Skip to content

Commit c62e254

Browse files
committed
fixed bullets issue
1 parent f9c257c commit c62e254

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

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

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -34,61 +34,61 @@ ms.date: 04/06/2023
3434

3535
## Detailed steps
3636

37-
1. ### User Assigned Managed Identity:
37+
### 1. User Assigned Managed Identity:
3838

3939
1. Search for Managed Identities in the global search bar.
4040

41-
![Searching for Managed Identities in Azure portal.](media/how-to-customer-managed-keys/user-assigned-managed-identity.png)
41+
![Searching for Managed Identities in Azure portal.](media/how-to-customer-managed-keys/user-assigned-managed-identity.png)
4242

4343

4444
1. Create a new User assigned managed Identity in the same region as your Azure Cosmos DB for PostgreSQL cluster.
4545

46-
![Screenshot of User assigned managed Identity page in Azure portal.](media/how-to-customer-managed-keys/user-assigned-managed-identity-provisioning.png)
46+
![Screenshot of User assigned managed Identity page in Azure portal.](media/how-to-customer-managed-keys/user-assigned-managed-identity-provisioning.png)
4747

4848

4949
Learn more about [User Assigned Managed Identity.](../../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity).
5050

51-
1. ### Key Vault:
51+
### 2. Key Vault:
5252

5353
Using customer-managed keys with Azure Cosmos DB for PostgreSQL requires you to set two properties on the Azure Key Vault instance that you plan to use to host your encryption keys: Soft Delete and Purge Protection.
5454

5555
1. If you create a new Azure Key Vault instance, enable these properties during creation:
5656

57-
![Screenshot of Key Vault's properties.](media/how-to-customer-managed-keys/key-vault-soft-delete.png)
58-
57+
![Screenshot of Key Vault's properties.](media/how-to-customer-managed-keys/key-vault-soft-delete.png)
58+
5959
1. If you're using an existing Azure Key Vault instance, you can verify that these properties are enabled by looking at the Properties section on the Azure portal. If any of these properties aren’t enabled, see the "Enabling soft delete" and "Enabling Purge Protection" sections in one of the following articles.
6060

61-
* How to use [soft-delete with PowerShell.](../../key-vault/general/key-vault-recovery.md)
62-
* How to use [soft-delete with Azure CLI.](../../key-vault/general/key-vault-recovery.md)
61+
* How to use [soft-delete with PowerShell.](../../key-vault/ general/key-vault-recovery.md)
62+
* How to use [soft-delete with Azure CLI.](../../key-vault/general/key-vault-recovery.md)
6363

6464
1. The key Vault must be set with 90 days for 'Days to retain deleted vaults'. If the existing key Vault has been configured with a lower number, you'll need to create a new key vault as it can't be modified after creation.
6565

6666
> [!IMPORTANT]
6767
> Your Azure Key Vault instance must be allow public access from all the networks.
6868
69-
1. ### Add an Access Policy to the Key Vault:
69+
### 3. Add an Access Policy to the Key Vault:
7070

7171
1. From the Azure portal, go to the Azure Key Vault instance that you plan to use to host your encryption keys. Select Access configuration from the left menu and then select Go to access policies.
7272

73-
![Screenshot of Key Vault's access configuration.](media/how-to-customer-managed-keys/access-policy.png)
73+
![Screenshot of Key Vault's access configuration.](media/how-to-customer-managed-keys/access-policy.png)
7474

7575
1. Select + Create.
7676

7777
1. In the Permissions Tab under the Key permissions drop-down menu, select Get, Unwrap Key, and Wrap Key permissions.
7878

79-
![Screenshot of Key Vault's permissions settings.](media/how-to-customer-managed-keys/access-policy-permissions.png)
79+
![Screenshot of Key Vault's permissions settings.](media/how-to-customer-managed-keys/access-policy-permissions.png)
8080

8181
1. In the Principal Tab, select the User Assigned Managed Identity you had created in prerequisite step.
8282

8383
1. Navigate to Review + create select Create.
8484

85-
1. ### Create / Import Key:
85+
### 4. Create / Import Key:
8686

8787
1. From the Azure portal, go to the Azure Key Vault instance that you plan to use to host your encryption keys.
8888

8989
1. Select Keys from the left menu and then select +Generate/Import.
9090

91-
![Screenshot of Key generation page.](media/how-to-customer-managed-keys/create-key.png)
91+
![Screenshot of Key generation page.](media/how-to-customer-managed-keys/create-key.png)
9292

9393
1. The customer-managed key to be used for encrypting the DEK can only be asymmetric RSA Key type. All RSA Key sizes 2048, 3072 and 4096 are supported.
9494

@@ -100,7 +100,7 @@ ms.date: 04/06/2023
100100

101101
1. If you're manually rotating the key, the old key version shouldn't be deleted for at least 24 hours.
102102

103-
1. ### Enable CMK encryption during the provisioning for a new cluster
103+
### 5. Enable CMK encryption during the provisioning for a new cluster
104104

105105
# [Portal](#tab/portal)
106106

0 commit comments

Comments
 (0)