Skip to content

Commit 665c050

Browse files
Update fail-over.md
Changed the guide to using two containers for each resource in the same region instead of using one container.
1 parent 42eaec7 commit 665c050

File tree

1 file changed

+4
-4
lines changed
  • articles/cognitive-services/language-service/custom-named-entity-recognition

1 file changed

+4
-4
lines changed

articles/cognitive-services/language-service/custom-named-entity-recognition/fail-over.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In this article, you will learn to how to use the export and import APIs to repl
2525

2626
## Prerequisites
2727

28-
* Two Azure Language resources in different Azure regions. [Create your resources](./how-to/create-project.md#create-a-language-resource) and connect them to an Azure storage account. It's recommended that you connect both of your Language resources to the same storage account, though this might introduce slightly higher latency when importing your project, and training a model.
28+
* Two Azure Language resources in different Azure regions. [Create your resources](./how-to/create-project.md#create-a-language-resource) and connect them to an Azure storage account. It's recommended that you connect each of the resources of your Language resources to a different storage account in the respective region the resource was created in. You can follow the the [quickstart](./quickstart?pivots=rest-api#create-a-new-azure-language-resource-and-azure-storage-account) to create an additional Language resource and storage account.
2929

3030
## Get your resource keys endpoint
3131

@@ -34,8 +34,8 @@ Use the following steps to get the keys and endpoint of your primary and seconda
3434
[!INCLUDE [Get keys and endpoint Azure Portal](./includes/get-keys-endpoint-azure.md)]
3535

3636
> [!TIP]
37-
> Keep a note of keys and endpoints for both primary and secondary resources. Use these values to replace the following placeholders:
38-
`{PRIMARY-ENDPOINT}`, `{PRIMARY-RESOURCE-KEY}`, `{SECONDARY-ENDPOINT}` and `{SECONDARY-RESOURCE-KEY}`.
37+
> Keep a note of keys and endpoints for both primary and secondary resources as well as the primary and secondary container names. Use these values to replace the following placeholders:
38+
`{PRIMARY-ENDPOINT}`, `{PRIMARY-RESOURCE-KEY}`, `{PRIMARY-CONTAINER-NAME}`, `{SECONDARY-ENDPOINT}`, `{SECONDARY-RESOURCE-KEY}`, and `{SECONDARY-CONTAINER-NAME}`.
3939
> Also take note of your project name, your model name and your deployment name. Use these values to replace the following placeholders: `{PROJECT-NAME}`, `{MODEL-NAME}` and `{DEPLOYMENT-NAME}`.
4040
4141
## Export your primary project assets
@@ -63,7 +63,7 @@ Now go ahead and import the exported project assets in your new project in the s
6363

6464
### Submit import job
6565

66-
Replace the placeholders in the following request with your `{SECONDARY-ENDPOINT}` and `{SECONDARY-RESOURCE-KEY}` that you obtained in the first step.
66+
Replace the placeholders in the following request with your `{SECONDARY-ENDPOINT}`, `{SECONDARY-RESOURCE-KEY}`, and `{SECONDARY-CONTAINER-NAME}` that you obtained in the first step.
6767

6868
[!INCLUDE [Import project using the REST API](./includes/rest-api/import-project.md)]
6969

0 commit comments

Comments
 (0)