-
Notifications
You must be signed in to change notification settings - Fork 420
Revisions to deploy with local identity article #3918
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@ManikaDhiman : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
PRMerger Results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the documentation for deploying Azure Local, version 23H2 using local identity with Azure Key Vault. The revisions include expanded explanations, updated procedures, and new troubleshooting content.
Key changes:
- Enhanced overview and benefits sections with clearer explanations of Local Identity deployment
- Added new sections for Key Vault extension alerts, tool compatibility, and FAQ
- Updated deployment procedures with more detailed steps and clarifications
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
## Overview | ||
|
||
Previously known as AD-less deployment, the method of using local identity with Key Vault allows Azure Local to securely manage and store secrets, such as BitLocker keys, node passwords, and other sensitive information, without relying on Active Directory (AD). By integrating with Key Vault and using certificate-based authentication, you can enhance your security posture and ensure the continuity of operations. | ||
In addition to Active Directory (AD) based deployment, Azure Local supports deployment through Local Identity with Azure Key Vault, previosuly known as AD-less deployment. |
Copilot
AI
Oct 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected spelling of 'previosuly' to 'previously'.
In addition to Active Directory (AD) based deployment, Azure Local supports deployment through Local Identity with Azure Key Vault, previosuly known as AD-less deployment. | |
In addition to Active Directory (AD) based deployment, Azure Local supports deployment through Local Identity with Azure Key Vault, previously known as AD-less deployment. |
Copilot uses AI. Check for mistakes.
Azure Local uses the Key Vault extension to securely store and manage secrets. To ensure reliability and security, the system continuously monitors the health of the Key Vault integration. If any issues are detected, alerts are automatically generated and surfaced through Azure Monitor for visibility and response. | ||
Alerts are sent through the Azure Alerts gateway and can be viewed in the Azure portal under **Monitor** > **Alerts**. You can configure action groups to receive notifications via email, SMS, or webhook. For more information, see [What are Azure Monitor alerts?](/azure/azure-monitor/alerts/alerts-overview) |
Copilot
AI
Oct 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing closing period at the end of the sentence.
Alerts are sent through the Azure Alerts gateway and can be viewed in the Azure portal under **Monitor** > **Alerts**. You can configure action groups to receive notifications via email, SMS, or webhook. For more information, see [What are Azure Monitor alerts?](/azure/azure-monitor/alerts/alerts-overview) | |
Alerts are sent through the Azure Alerts gateway and can be viewed in the Azure portal under **Monitor** > **Alerts**. You can configure action groups to receive notifications via email, SMS, or webhook. For more information, see [What are Azure Monitor alerts?](/azure/azure-monitor/alerts/alerts-overview). |
Copilot uses AI. Check for mistakes.
This extension requires specific configurations that are only applied by the Azure Local Resource Provider (*Microsoft.AzureStackHCI Resource Provider*). To restore the extension, trigger a synchronization from the cluster by running the following command: | ||
<!--Add command here--> |
Copilot
AI
Oct 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command placeholder needs to be replaced with the actual command for triggering synchronization from the cluster. This is critical information for users troubleshooting the deleted extension scenario.
<!--Add command here--> | |
```powershell | |
Invoke-AzStackHciClusterSync | |
``` |
Copilot uses AI. Check for mistakes.
If the extension wasn't installed during deployment, you can manually install it on Arc-enabled servers by following these steps: | ||
1. Create a new Azure Key Vault if you don’t already have one. For instructions, see [Quickstart: Create a key vault using the Azure portal](/key-vault/general/quick-create-portal). |
Copilot
AI
Oct 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link path appears to be missing the Azure documentation domain. It should be /azure/key-vault/general/quick-create-portal
to match the standard Azure documentation URL format used elsewhere in the document.
1. Create a new Azure Key Vault if you don’t already have one. For instructions, see [Quickstart: Create a key vault using the Azure portal](/key-vault/general/quick-create-portal). | |
1. Create a new Azure Key Vault if you don’t already have one. For instructions, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). |
Copilot uses AI. Check for mistakes.
@alkohli Can you review the proposed changes? Note the following blocker needs to be resolved before this PR is eventually merged: azure-local/deploy/media/deployment-local-identity-with-key-vault/key-vault-secret-extension-install-6.png
If you approve the new content in this PR, the commits must be moved to the private repository for automated checks and publishing. After you move the commits, close this PR ( Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Learn Build status updates of commit 46ddb57: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Learn Build status updates of commit fe244af: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Learn Build status updates of commit 32f5a75: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Learn Build status updates of commit 2238c82: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
No description provided.