You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/deploy/deployment-local-identity-with-key-vault.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy Azure Local, version 23H2 using local identity with Azure Key Vaul
3
3
description: Learn how to use local identity with Azure Key Vault for Azure Local, version 23H2 deployment (preview).
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 11/14/2024
6
+
ms.date: 11/15/2024
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
ms.service: azure-stack-hci
@@ -37,7 +37,7 @@ Using local identity with Key Vault on Azure Local offers several benefits, part
37
37
38
38
Before you start, make sure that you:
39
39
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).
41
41
42
42
- Satisfy the [prerequisites and complete deployment checklist](./deployment-prerequisites.md). Skip the AD-specific prerequisites.
43
43
@@ -125,7 +125,19 @@ After deploying the system, confirm the deployment was AD-less and verify that s
125
125
126
126
After deploying the system, confirm the deployment was without AD (AD-less).
127
127
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.
1. Verify a cluster is a Workgroup cluster functional without AD. Run the following command and check the value of the `ADAware` parameter:
130
142
131
143
```powershell
@@ -142,6 +154,10 @@ After deploying the system, confirm the deployment was without AD (AD-less).
142
154
143
155
### Verify secrets are getting backed up to Key Vault
144
156
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
+
145
161
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.
146
162
147
163
:::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