Skip to content

Commit b5c44bf

Browse files
author
Manika Dhiman
committed
tweaks
1 parent dc73831 commit b5c44bf

File tree

2 files changed

+5
-7
lines changed

2 files changed

+5
-7
lines changed

azure-local/TOC.yml

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -207,10 +207,8 @@ items:
207207
href: deploy/deployment-azure-arc-gateway-configure-via-script.md
208208
- name: Configure without a proxy
209209
href: deploy/deployment-azure-arc-gateway-use-without-proxy.md
210-
- name: Deploy with local identiy
211-
items:
212-
- name: Prepare local identity with Key Vault
213-
href: deploy/deployment-local-identity-with-key-vault.md
210+
- name: Deploy using local identiy with Key Vault
211+
href: deploy/deployment-local-identity-with-key-vault.md
214212
- name: Deploy SDN
215213
items:
216214
- name: Using Express scripts

azure-local/deploy/deployment-local-identity-with-key-vault.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Follow these steps to configure DNS for Azure Local:
9999
100100
## Deploy Azure Local via the portal using local identity with Key Vault
101101
102-
During the system deployment via the Azure portal, you have the option to select a local identity provider integrated with Key Vault. This means that instead of relying on AD for authentication, you can use a local identity with Key Vault to manage and store secrets securely.
102+
During deployment via the Azure portal, you have the option to select a local identity provider integrated with Key Vault. This allows you to use a local identity with Key Vault to securely manage and store secrets instead of relying on AD for authentication.
103103
104104
The general deployment steps are the same as those outlined in [Deploy an Azure Local, version 23H2 system using the Azure portal](./deploy-via-portal.md). However, when using local identity with Key Vault, you need to perform specific steps on the **Networking** and **Management** tabs.
105105
@@ -119,7 +119,7 @@ The general deployment steps are the same as those outlined in [Deploy an Azure
119119
120120
## Post-deployment steps
121121
122-
After deploying the system, confirm the deployment was without AD (AD-less) and verify secrets are getting backed up to Key Vault.
122+
After deploying the system, confirm the deployment was AD-less and verify that secrets are being backed up to Key Vault.
123123
124124
### Confirm the system was deployed without Active Directory
125125
@@ -144,7 +144,7 @@ After deploying the system, confirm the deployment was without AD (AD-less).
144144
145145
This ensures that all critical information is stored safely and can be easily retrieved when needed, providing an additional layer of security and reliability for our infrastructure.
146146
147-
:::image type="content" source="media/deployment-local-identity-with-key-vault/back-up-secrets.png" alt-text="Screenshot of Create a Key Vault page." border="false" lightbox="media/deployment-local-identity-with-key-vault/back-up-secrets.png":::
147+
:::image type="content" source="media/deployment-local-identity-with-key-vault/back-up-secrets.png" alt-text="Screenshot of the Secrets page." border="false" lightbox="media/deployment-local-identity-with-key-vault/back-up-secrets.png":::
148148
149149
## Update Key Vault on Azure Local
150150

0 commit comments

Comments
 (0)