Skip to content

Commit b84a498

Browse files
committed
Learn Editor: Update how-to-setup-customer-managed-keys.md
1 parent 68de008 commit b84a498

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
@@ -336,6 +336,7 @@ az cosmosdb show \
336336
--query "keyVaultKeyUri"
337337
```
338338

339+
339340
---
340341

341342
## Using a managed identity in the Azure Key Vault access policy
@@ -461,9 +462,6 @@ Currently, only user-assigned managed identity is supported for creating continu
461462

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

464-
> [!NOTE]
465-
> System-assigned identity and continuous backup mode is currently under Public Preview and may change in the future.
466-
467465
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)
468466

469467
### [Azure CLI](#tab/azure-cli)
@@ -536,10 +534,6 @@ A user-assigned identity is required in the restore request because the source a
536534

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

539-
> [!NOTE]
540-
> This feature is currently under Public Preview and requires Cosmos DB CLI Extension version 0.20.0 or higher.
541-
542-
543537
1. Create a new user-assigned identity (or use an existing one) for the restore process.
544538

545539
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.
@@ -577,7 +571,6 @@ Use the Azure CLI to restore a continuous account that is already configured usi
577571
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.
578572
579573
580-
581574
### [PowerShell / Azure Resource Manager template / Azure portal](#tab/azure-powershell+arm-template+azure-portal)
582575
583576
Not available
@@ -741,3 +734,4 @@ Steps to assign a new managed-identity:
741734
## Next steps
742735
743736
- Learn more about [data encryption in Azure Cosmos DB](database-encryption-at-rest.md).
737+

0 commit comments

Comments
 (0)