Deploy custom language projects to multiple regions
Note
This article applies to the following custom features in Azure AI Language:
Custom language service features enable you to deploy your project to more than one region. This capability makes it much easier to access your project globally while you manage only one instance of your project in one place.
Before you deploy a project, you can assign deployment resources in other regions. Each deployment resource is a different Language resource from the one that you use to author your project. You deploy to those resources and then target your prediction requests to that resource in their respective regions and your queries are served directly from that region.
When you create a deployment, you can select which of your assigned deployment resources and their corresponding regions you want to deploy to. The model you deploy is then replicated to each region and accessible with its own endpoint dependent on the deployment resource's custom subdomain.
Validations and requirements
Assigning deployment resources requires Microsoft Entra authentication. Microsoft Entra ID is used to confirm that you have access to the resources that you want to assign to your project for multiregion deployment. In Language Studio, you can automatically enable Microsoft Entra authentication by assigning yourself the Azure Cognitive Services Language Owner role to your original resource. To programmatically use Microsoft Entra authentication, learn more from the Azure AI services documentation.
Your project name and resource are used as its main identifiers. A Language resource can only have a specific project name in each resource. Any other projects with the same name can't be deployed to that resource.
You can only swap deployments that are available in the exact same regions. Otherwise, swapping fails.
If you remove an assigned resource from your project, all of the project deployments to that resource are deleted.
Note
Orchestration workflow only:
You can't assign deployment resources to orchestration workflow projects with custom question answering or LUIS connections. Subsequently, you can't add custom question answering or LUIS connections to projects that have assigned resources.
For multiregion deployment to work as expected, the connected CLU projects must also be deployed to the same regional resources to which you deployed the orchestration workflow project. Otherwise, the orchestration workflow project attempts to route a request to a deployment in its region that doesn't exist.
Some regions are only available for deployment and not for authoring projects.
Related content
Learn how to deploy models for: