why is not trigger URL available for Sora-2?

Hello 3l3c,

Welcome to Microsoft Q&A,

There isn’t a separate “trigger URL” for Sora-2. For Sora-2 you call the Azure OpenAI v1 endpoint of your resource (the same base URL you see under Keys + Endpoint), and the SDK/REST route handles the “trigger” (create video job) and “status/download” calls. In some panes Azure AI Foundry shows a “Target/Trigger URL”, but for OpenAI models, especially Standard Global Sora-2 deployments—that field can be blank; this is expected and not a misconfiguration.

https://free.blessedness.top/en-us/azure/ai-foundry/openai/concepts/video-generation?tabs=python-entra

https://free.blessedness.top/en-us/azure/ai-foundry/openai/api-version-lifecycle?tabs=python

Please Upvote and accept the answer if it helps!!

Hello 3l3c,

Welcome to Microsoft Q&A and thank you for reaching out.

The Sora-2 model currently doesn’t expose a trigger URL because it’s not yet supported for direct REST API invocation or endpoint-based triggering like other Azure OpenAI models. At this stage, access to Sora-2 is limited to usage within the Azure AI Studio interface (for testing and evaluation) and may not yet be integrated into programmatic workflows. You haven’t missed any configuration this behavior is expected for the current release. Microsoft is gradually expanding support for trigger URLs and API-based integration for Sora models, which will be made available once the service moves closer to general availability.

In addition to the details Divyesh Govaerdhanan already shared, you may also want to verify the following points:

Ensure that your deployment type is set to Standard Global and not a Private Preview configuration. Some regions (like Sweden Central) may have partial rollout status for Sora-2, and trigger-related features might still be in phased enablement.

You can learn more about the limited access criteria here.

Even though the trigger URL isn’t explicitly listed, you can still interact with Sora-2 via the standard Azure OpenAI v1 endpoint by invoking the /videos API path programmatically. The endpoint structure typically follows this pattern:

https://{your-resource-name}.openai.azure.com/openai/deployments/{deployment-name}/videos?api-version=2024-09-01-preview

This route handles both job creation and status retrieval, replacing the need for a separate trigger URL.

Since Sora-2 is currently in a public preview phase, some portal views (like “Target/Trigger URL”) may show as blank by design. These fields will become active once the model transitions toward GA (General Availability) with full REST API integration.

Confirm that your account or subscription has video generation preview access granted. In some cases, access is region- and tenant-specific, especially for new model families like Sora.

Check the Azure Service Health page to see if there are any ongoing incidents that might affect the availability of your resources.

Please Keep an eye on the Azure AI Foundry release notes, Sora 2 API guidelines and API version lifecycle documentation, as Microsoft may announce new API enhancements or region-wide endpoint support in upcoming updates.

I Hope this helps. Do let me know if you have any further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!