Skip to content

Commit 5e79ecc

Browse files
authored
Merge pull request #107182 from outinyman/patch-35
How to use CMK in single data residency regions
2 parents 4cb0095 + 546e58a commit 5e79ecc

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/healthcare-apis/azure-api-for-fhir/customer-managed-key.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,10 @@ You can also enter the key URI here:
4747
> Ensure all permissions for Azure Key Vault are set appropriately. For more information, see [Add an access policy to your Azure Key Vault instance](../../cosmos-db/how-to-setup-cmk.md#add-access-policy).
4848
Additionally, ensure that the soft delete is enabled in the properties of the Key Vault. Not completing these steps will result in a deployment error. For more information, see [Verify if soft delete is enabled on a key vault and enable soft delete](../../key-vault/general/key-vault-recovery.md?tabs=azure-portal#verify-if-soft-delete-is-enabled-on-a-key-vault-and-enable-soft-delete).
4949

50+
> [!NOTE]
51+
> Using customer-managed keys in Brazil South and East Asia regions requires an Enterprise Application ID generated by Microsoft. You can request Enterprise Application ID by creating a one-time support ticket through the Azure portal. After receiving the Application ID, follow [the instructions to register the application](/azure/cosmos-db/how-to-setup-cross-tenant-customer-managed-keys?tabs=azure-portal#the-customer-grants-the-service-providers-app-access-to-the-key-in-the-key-vault).
52+
53+
5054
For existing FHIR accounts, you can view the key encryption choice (**Service-managed key** or **Customer-managed key**) in the **Database** blade as shown below. The configuration option can't be modified once it's selected. However, you can modify and update your key.
5155

5256
:::image type="content" source="media/bring-your-own-key/bring-your-own-key-database.png" alt-text="Database":::

0 commit comments

Comments
 (0)