Skip to content

Commit 10d826e

Browse files
author
Manika Dhiman
committed
added review feedback
1 parent 97b08d8 commit 10d826e

File tree

1 file changed

+19
-3
lines changed

1 file changed

+19
-3
lines changed

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

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy Azure Local, version 23H2 using local identity with Azure Key Vaul
33
description: Learn how to use local identity with Azure Key Vault for Azure Local, version 23H2 deployment (preview).
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 11/14/2024
6+
ms.date: 11/15/2024
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
ms.service: azure-stack-hci
@@ -37,7 +37,7 @@ Using local identity with Key Vault on Azure Local offers several benefits, part
3737

3838
Before you start, make sure that you:
3939

40-
- Sign the [Local Identity with Azure Key Vault Preview signup form](https://forms.office.com/pages/responsepage.aspx?id=DQSIkWdsW0yxEjajBLZtrQAAAAAAAAAAAAN__v7SnuFUNjBYOTVZTjRaTUtVVFVWSU1EM1dWWFpSOC4u&route=shorturl) to participate in the limited public preview.
40+
- Sign the [Local Identity with Azure Key Vault Preview signup form](https://forms.office.com/pages/responsepage.aspx?id=DQSIkWdsW0yxEjajBLZtrQAAAAAAAAAAAAN__v7SnuFUNjBYOTVZTjRaTUtVVFVWSU1EM1dWWFpSOC4u&route=shorturl) to participate in the limited public preview. For more information about how we collect, use, and protect your personal data during your participation in the preview, review [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
4141

4242
- Satisfy the [prerequisites and complete deployment checklist](./deployment-prerequisites.md). Skip the AD-specific prerequisites.
4343

@@ -125,7 +125,19 @@ After deploying the system, confirm the deployment was AD-less and verify that s
125125
126126
After deploying the system, confirm the deployment was without AD (AD-less).
127127
128-
1. Confirm the node isn't joined to an AD domain. <!--steps-->
128+
1. Confirm the node isn't joined to an AD domain by running the following command. If the output shows `WORKGROUP`, the node isn't domain-joined.
129+
130+
```powershell
131+
Get-WmiObject Win32_ComputerSystem.Domain
132+
```
133+
134+
Here's a sample output:
135+
136+
```output
137+
[host]: PS C:\Users\LocalAdmin\Documents> (Get-WmiObject Win32_ComputerSystem).Domain
138+
WORKGROUP
139+
```
140+
129141
1. Verify a cluster is a Workgroup cluster functional without AD. Run the following command and check the value of the `ADAware` parameter:
130142
131143
```powershell
@@ -142,6 +154,10 @@ After deploying the system, confirm the deployment was without AD (AD-less).
142154
143155
### Verify secrets are getting backed up to Key Vault
144156
157+
BitLocker keys and recovery admin passwords are securely backed up to Azure and are rotated to ensure maximum security.
158+
159+
In scenarios where AD isn't available, you can utilize a dedicated recovery admin user to restore the system. The designated username for this purpose is `RecoveryAdmin`. The corresponding password can be securely retrieved from the Azure Key Vault, ensuring that you have the necessary credentials to perform system recovery operations effectively.
160+
145161
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.
146162
147163
:::image type="content" source="media/deployment-local-identity-with-key-vault/back-up-secrets.png" alt-text="Screenshot of the Secrets page." lightbox="media/deployment-local-identity-with-key-vault/back-up-secrets.png":::

0 commit comments

Comments
 (0)