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
Copy file name to clipboardExpand all lines: articles/aks/use-kms-etcd-encryption.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ The following limitations apply when you integrate KMS etcd encryption with AKS:
35
35
* Using more than 2000 secrets in a cluster.
36
36
* Bring your own (BYO) Azure Key Vault from another tenant.
37
37
* Change associated Azure Key Vault model (public, private) if KMS is enabled. For [changing associated key vault mode][changing-associated-key-vault-mode], you need to disable and enable KMS again.
38
-
* Stop/satrt cluster which is enabled KMS with private key vault.
38
+
* Stop/start cluster which is enabled KMS with private key vault.
39
39
40
40
KMS supports [public key vault][Enable-KMS-with-public-key-vault] and [private key vault][Enable-KMS-with-private-key-vault] now.
41
41
@@ -111,7 +111,7 @@ Create an AKS cluster using the [az aks create][az-aks-create] command with the
111
111
az aks create --name myAKSCluster --resource-group MyResourceGroup --assign-identity $IDENTITY_RESOURCE_ID --enable-azure-keyvault-kms --azure-keyvault-kms-key-vault-network-access "Public" --azure-keyvault-kms-key-id $KEY_ID
112
112
```
113
113
114
-
### Update an exiting AKS cluster to enable KMS etcd encryption
114
+
### Update an existing AKS cluster to enable KMS etcd encryption
115
115
116
116
Use [az aks update][az-aks-update] with the `--enable-azure-keyvault-kms`, `--azure-keyvault-kms-key-vault-network-access` and `--azure-keyvault-kms-key-id` parameters to enable KMS etcd encryption on an existing cluster.
After changing the key ID (including key name and key version), you could use [az aks update][az-aks-update] with the `--enable-azure-keyvault-kms`, `--azure-keyvault-kms-key-vault-network-access` and `--azure-keyvault-kms-key-id` parameters to rotate the exitsing keys of KMS.
133
133
134
134
> [!WARNING]
135
-
> Remember to update all secrets after key rotation. Otheriwse, the secrets will be unaccessable if the old keys are not existing or working.
135
+
> Remember to update all secrets after key rotation. Otherwise, the secrets will be unaccessable if the old keys are not existing or working.
136
136
137
137
```azurecli-interactive
138
138
az aks update --name myAKSCluster --resource-group MyResourceGroup --enable-azure-keyvault-kms --azure-keyvault-kms-key-vault-network-access "Public" --azure-keyvault-kms-key-id $NEW_KEY_ID
@@ -215,7 +215,7 @@ Create an AKS cluster using the [az aks create][az-aks-create] command with the
215
215
az aks create --name myAKSCluster --resource-group MyResourceGroup --assign-identity $IDENTITY_RESOURCE_ID --enable-azure-keyvault-kms --azure-keyvault-kms-key-id $KEY_ID --azure-keyvault-kms-key-vault-network-access "Private" --azure-keyvault-kms-key-vault-resource-id $KEYVAULT_RESOURCE_ID
216
216
```
217
217
218
-
### Update an exiting AKS cluster to enable KMS etcd encryption with private key vault
218
+
### Update an existing AKS cluster to enable KMS etcd encryption with private key vault
219
219
220
220
Use [az aks update][az-aks-update] with the `--enable-azure-keyvault-kms`, `--azure-keyvault-kms-key-id`, `--azure-keyvault-kms-key-vault-network-access` and `--azure-keyvault-kms-key-vault-resource-id` parameters to enable KMS etcd encryption on an existing cluster with private key vault.
Copy file name to clipboardExpand all lines: articles/applied-ai-services/form-recognizer/concept-custom-neural.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: nitinme
7
7
ms.service: applied-ai-services
8
8
ms.subservice: forms-recognizer
9
9
ms.topic: conceptual
10
-
ms.date: 07/11/2022
10
+
ms.date: 08/02/2022
11
11
ms.author: lajanuar
12
12
ms.custom: references_regions
13
13
recommendations: false
@@ -61,7 +61,9 @@ Starting August 01, 2022, Form Recognizer custom neural model training will only
61
61
* Southeast Asia
62
62
63
63
> [!TIP]
64
-
> You can [copy a model](disaster-recovery.md) trained in one of the select regions listed above to **any other region** and use it accordingly.
64
+
> You can [copy a model](disaster-recovery.md#copy-api-overview) trained in one of the select regions listed above to **any other region** and use it accordingly.
65
+
>
66
+
> Use the [**REST API**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-06-30-preview/operations/CopyDocumentModelTo) or [**Form Recognizer Studio**](https://formrecognizer.appliedai.azure.com/studio/custommodel/projects) to copy a model to another region.
Copy file name to clipboardExpand all lines: articles/applied-ai-services/form-recognizer/disaster-recovery.md
+22-29Lines changed: 22 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: nitinme
7
7
ms.service: applied-ai-services
8
8
ms.subservice: forms-recognizer
9
9
ms.topic: how-to
10
-
ms.date: 03/15/2021
10
+
ms.date: 08/02/2022
11
11
ms.author: lajanuar
12
12
---
13
13
@@ -21,11 +21,10 @@ The Copy API enables this scenario by allowing you to copy custom models from on
21
21
22
22
If your app or business depends on the use of a Form Recognizer custom model, we recommend you copy your model to another Form Recognizer account in another region. If a regional outage occurs, you can then access your model in the region where it was copied.
23
23
24
-
## Prerequisites
25
-
26
-
1. Two Form Recognizer Azure resources in different Azure regions. If you don't have them, go to the Azure portal and <ahref="https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer"title="Create a new Form Recognizer resource"target="_blank">create a new Form Recognizer resource </a>.
27
-
1. The key, endpoint URL, and subscription ID of your Form Recognizer resource. You can find these values on the resource's **Overview** tab on the Azure portal.
24
+
## Prerequisites
28
25
26
+
1. Two Form Recognizer Azure resources in different Azure regions. If you don't have them, go to the Azure portal and [create a new Form Recognizer resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer).
27
+
1. The key, endpoint URL, and subscription ID for your Form Recognizer resource. You can find these values on the resource's **Overview** tab in the [Azure portal](https://ms.portal.azure.com/#home).
29
28
30
29
## Copy API overview
31
30
@@ -35,17 +34,19 @@ The process for copying a custom model consists of the following steps:
35
34
1. Next you send the copy request to the source resource—the resource that contains the model to be copied with the payload (copy authorization) returned from the previous call. You'll get back a URL that you can query to track the progress of the operation.
36
35
1. You'll use your source resource credentials to query the progress URL until the operation is a success. You can also query the new model ID in the target resource to get the status of the new model.
37
36
38
-
# [Form Recognizer v3.0 (Preview)](#tab/v30)
37
+
###[Form Recognizer REST API v3.0 (Preview)](#tab/v30)
39
38
40
39
## Generate Copy authorization request
41
40
42
41
The following HTTP request gets copy authorization from your target resource. You'll need to enter the endpoint and key of your target resource as headers.
43
42
44
-
```
43
+
```http
45
44
POST https://{TARGET_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/documentModels:authorizeCopy?api-version=2022-06-30-preview
@@ -70,7 +71,7 @@ You'll get a `200` response code with response body that contains the JSON paylo
70
71
71
72
The following HTTP request starts the copy operation on the source resource. You'll need to enter the endpoint and key of your source resource as the url and header. Notice that the request URL contains the model ID of the source model you want to copy.
72
73
73
-
```
74
+
```http
74
75
POST {{source-endpoint}}formrecognizer/documentModels/{model-to-be-copied}:copyTo?api-version=2022-06-30-preview
@@ -90,26 +91,25 @@ The body of your request is the response from the previous step.
90
91
91
92
You'll get a `202\Accepted` response with an Operation-Location header. This value is the URL that you'll use to track the progress of the operation. Copy it to a temporary location for the next step.
### [Form Recognizer REST API v2.1 (GA)](#tab/v21)
100
100
101
101
## Generate Copy authorization request
102
102
103
103
The following HTTP request gets copy authorization from your target resource. You'll need to enter the endpoint and key of your target resource as headers.
104
104
105
-
```
105
+
```http
106
106
POST https://{TARGET_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/v2.1/custom/models/copyAuthorization
You'll get a `201\Created` response with a `modelId` value in the body. This string is the ID of the newly created (blank) model. The `accessToken` is needed for the API to copy data to this resource, and the `expirationDateTimeTicks` value is the expiration of the token. Save all three of these values to a secure location.
The following HTTP request starts the Copy operation on the source resource. You'll need to enter the endpoint and key of your source resource as headers. Notice that the request URL contains the model ID of the source model you want to copy.
121
121
122
-
```
122
+
```http
123
123
POST https://{SOURCE_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/v2.1/custom/models/<your model ID>/copy HTTP/1.1
@@ -136,20 +136,16 @@ The body of your request needs to have the following format. You'll need to ente
136
136
137
137
You'll get a `202\Accepted` response with an Operation-Location header. This value is the URL that you'll use to track the progress of the operation. Copy it to a temporary location for the next step.
> The Copy API transparently supports the [AEK/CMK](https://msazure.visualstudio.com/Cognitive%20Services/_wiki/wikis/Cognitive%20Services.wiki/52146/Customer-Managed-Keys) feature. This doesn't require any special treatment, but note that if you're copying between an unencrypted resource to an encrypted resource, you need to include the request header `x-ms-forms-copy-degrade: true`. If this header is not included, the copy operation will fail and return a `DataProtectionTransformServiceError`.
Track your progress by querying the **Get Copy Model Result** API against the source resource endpoint.
172
168
173
-
```
169
+
```http
174
170
GET https://{SOURCE_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/v2.1/custom/models/eccc3f13-8289-4020-ba16-9f1d1374e96f/copyresults/02989ba8-1296-499f-aaf4-55cfff41b8f1 HTTP/1.1
Your response will vary depending on the status of the operation. Look for the `"status"` field in the JSON body. If you're automating this API call in a script, we recommend querying the operation once every second.
|"errors":[{"code":"DataProtectionTransformServiceError",<br>"message":"Data transfer request isn't allowed <br>as it downgrades to a less secure data protection scheme. Refer documentation or contact your service administrator <br>for details."}]| Occurs when copying between an `AEK` enabled resource to a non `AEK` enabled resource. To allow copying encrypted model to the target as unencrypted specify `x-ms-forms-copy-degrade: true` header with the copy request.|
197
191
|"errors":[{"code":"ResourceResolverError",<br>"message":"Couldn't fetch information for Cognitive resource with ID '...'. Ensure the resource is valid and exists in the specified region 'westus2'.."}]| Indicates that the Azure resource indicated by the `targetResourceId` isn't a valid Cognitive resource or doesn't exist. Verify and reissue the copy request to resolve this issue.|
198
192
199
-
200
193
### [Optional] Track the target model ID
201
194
202
195
You can also use the **Get Custom Model** API to track the status of the operation by querying the target model. Call this API using the target model ID that you copied down in the first step.
203
196
204
-
```
197
+
```http
205
198
GET https://{TARGET_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/v2.1/custom/models/33f4d42c-cd2f-4e74-b990-a1aeafab5a5d HTTP/1.1
0 commit comments