Skip to content

Commit e1da0ce

Browse files
Merge pull request #247660 from MikeRayMSFT/20230808-245930
20230808 245930
2 parents ac279f5 + 0a03e1a commit e1da0ce

File tree

1 file changed

+2
-8
lines changed

1 file changed

+2
-8
lines changed

articles/cosmos-db/how-to-setup-customer-managed-keys.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -347,6 +347,7 @@ az cosmosdb show \
347347
--query "keyVaultKeyUri"
348348
```
349349

350+
350351
---
351352

352353
## Using a managed identity in the Azure Key Vault access policy
@@ -472,9 +473,6 @@ Currently, only user-assigned managed identity is supported for creating continu
472473

473474
Once the account has been created, you can update the identity to system-assigned managed identity.
474475

475-
> [!NOTE]
476-
> System-assigned identity and continuous backup mode is currently under Public Preview and may change in the future.
477-
478476
Alternatively, user can also create a system identity with periodic backup mode first, then migrate the account to Continuous backup mode using these instructions [Migrate an Azure Cosmos DB account from periodic to continuous backup mode](./migrate-continuous-backup.md)
479477

480478
### [Azure CLI](#tab/azure-cli)
@@ -547,10 +545,6 @@ A user-assigned identity is required in the restore request because the source a
547545

548546
Use the Azure CLI to restore a continuous account that is already configured using a system-assigned or user-assigned managed identity.
549547

550-
> [!NOTE]
551-
> This feature is currently under Public Preview and requires Cosmos DB CLI Extension version 0.20.0 or higher.
552-
553-
554548
1. Create a new user-assigned identity (or use an existing one) for the restore process.
555549

556550
1. Create the new access policy in your Azure Key Vault account as described previously, use the Object ID of the managed identity from step 1.
@@ -585,7 +579,6 @@ Use the Azure CLI to restore a continuous account that is already configured usi
585579
1. Once the restore has completed, the target (restored) account will have the user-assigned identity. If desired, user can update the account to use System-Assigned managed identity.
586580
587581
588-
589582
### [PowerShell / Azure Resource Manager template / Azure portal](#tab/azure-powershell+arm-template+azure-portal)
590583
591584
Not available
@@ -749,3 +742,4 @@ Steps to assign a new managed-identity:
749742
## Next steps
750743
751744
- Learn more about [data encryption in Azure Cosmos DB](database-encryption-at-rest.md).
745+

0 commit comments

Comments
 (0)