You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.**Resource Region**. Choose **Global** unless your business or application requires a specific region. If you're planning on using a [system-assigned managed identity](create-use-managed-identities.md) for authentication, choose a **geographic** region like **West US**.
47
47
48
-
1.**Name**. Enter the name you have chosen for your resource. The name you choose must be unique within Azure.
48
+
1.**Name**. Enter the name you chose for your resource. The name you choose must be unique within Azure.
49
49
50
50
> [!NOTE]
51
51
> Document Translation requires a custom domain endpoint. The value that you enter in the Name field will be the custom domain name parameter for your endpoint.
@@ -56,13 +56,13 @@ To get started, you need:
56
56
57
57
1. Review the service terms and select **Create** to deploy your resource.
58
58
59
-
1. After your resource has successfully deployed, select **Go to resource**.
59
+
1. After your resource successfully deploys, select **Go to resource**.
60
60
61
61
### Retrieve your key and custom domain endpoint
62
62
63
63
*Requests to the Translator service require a read-only key and custom endpoint to authenticate access. The custom domain endpoint is a URL formatted with your resource name, hostname, and Translator subdirectories and is available in the Azure portal.
64
64
65
-
1. If you've created a new resource, after it deploys, select **Go to resource**. If you have an existing Document Translation resource, navigate directly to your resource page.
65
+
1. If you created a new resource, after it deploys, select **Go to resource**. If you have an existing Document Translation resource, navigate directly to your resource page.
66
66
67
67
1. In the left rail, under *Resource Management*, select **Keys and Endpoint**.
68
68
@@ -76,7 +76,7 @@ To get started, you need:
76
76
77
77
Requests to the Translator service require a read-only key for authenticating access.
78
78
79
-
1. If you've created a new resource, after it deploys, select **Go to resource**. If you have an existing Document Translation resource, navigate directly to your resource page.
79
+
1. If you created a new resource, after it deploys, select **Go to resource**. If you have an existing Document Translation resource, navigate directly to your resource page.
80
80
1. In the left rail, under *Resource Management*, select **Keys and Endpoint**.
81
81
1. Copy and paste your key in a convenient location, such as *Microsoft Notepad*.
82
82
1. You paste it into the code sample to authenticate your request to the Document Translation service.
@@ -97,9 +97,9 @@ You need to [**create containers**](../../../../storage/blobs/storage-quickstar
97
97
98
98
The `sourceUrl` , `targetUrl` , and optional `glossaryUrl` must include a Shared Access Signature (SAS) token, appended as a query string. The token can be assigned to your container or specific blobs. *See*[**Create SAS tokens for Document Translation process**](create-sas-tokens.md).
99
99
100
-
* Your **source** container or blob must have designated**read** and **list** access.
101
-
* Your **target** container or blob must have designated**write** and **list** access.
102
-
* Your **glossary** blob must have designated**read** and **list** access.
100
+
* Your **source** container or blob must designate**read** and **list** access.
101
+
* Your **target** container or blob must designate**write** and **list** access.
102
+
* Your **glossary** blob must designate**read** and **list** access.
103
103
104
104
> [!TIP]
105
105
>
@@ -142,11 +142,11 @@ The following headers are included with each Document Translation API request:
@@ -158,8 +158,8 @@ The following headers are included with each Document Translation API request:
158
158
### Translate a specific document in a container
159
159
160
160
* Specify `"storageType": "File"`
161
-
* If you aren't using a [**system-assigned managed identity**](create-use-managed-identities.md) for authentication, make sure you've created source URL & SAS token for the specific blob/document (not for the container)
162
-
* Ensure you've specified the target filename as part of the target URL – though the SAS token is still for the container.
161
+
* If you aren't using a [**system-assigned managed identity**](create-use-managed-identities.md) for authentication, make sure you created source URL & SAS tokens for the specific blob/document (not for the container)
162
+
* Ensure you specified the target filename as part of the target URL – though the SAS token is still for the container.
163
163
* This sample request returns a single document translated into two target languages
164
164
165
165
```json
@@ -168,15 +168,15 @@ The following headers are included with each Document Translation API request:
Cancelcurrentlyprocessingorqueuedjob. Onlydocumentsforwhichtranslationhasn't started are canceled.
1100
+
Cancelcurrentlyprocessingorqueuedjob. Onlydocumentsforwhichtranslationisn't started are canceled.
1101
1101
1102
1102
### [C#](#tab/csharp)
1103
1103
@@ -1280,8 +1280,8 @@ func main() {
1280
1280
|200|OK|Therequestwassuccessful. |
1281
1281
|400|BadRequest|Arequiredparameterismissing, empty, or null. Or, the value passed to either a required or optional parameter is invalid. A common issue is a header that is too long. |
1282
1282
| 401 | Unauthorized | The request isn't authorized. Check to make sure your key or token is valid and in the correct region. When managing your subscription on the Azureportal, makesureyou'reusingthe **Translator** single-serviceresource_not_the **AzureAIservices** multi-serviceresource.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments