Update image-builder-overview.md #209
Conversation
You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview command to register the provider Microsoft.VirtualMachineImages in AzureGov.
|
@chrismrutledge : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 7214d0e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? If you accept the changes, Note this content requires automated and human checks available only in the private repository. Please close this PR ( IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
|
||
| ```azurecli-interactive | ||
| az feature register --namespace Microsoft.VirtualMachineImages --name FairfaxPublicPreview | ||
| ``` |
There was a problem hiding this comment.
_> You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview
> command to register the provider Microsoft.VirtualMachineImages in AzureGov.
Hello. How was this ascertained? AFAIK, this AFEC flag is still needed.
There was a problem hiding this comment.
In a new Fairfax tenant, I registered Microsoft.VirtualMachineImages in the portal and deployed a custom image template. There was no requirement for the extra step specifically for FairfaxPublicPreview
There was a problem hiding this comment.
@sumit-kalra Can you respond to the comment above?
@MicrosoftDocs/public-repo-pr-review-team
There was a problem hiding this comment.
@chrismrutledge - The AFEC should still be needed. If it's not being required then it may be a code bug (and not a doc bug). We are investigating. Thanks for bringing this up.
There was a problem hiding this comment.
Also @chrismrutledge - would it be possible for you to share the subscription ID you used to validate that image templates could be created without registering to an AFEC?
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
github-actions
bot
removed
the
inactive
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
github-actions
bot
removed
the
inactive
|
@chrismrutledge Can you share the subscription you used to validate that image templates could be created without registering to an afec? |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
Nudging @chrismrutledge, thank you. |
github-actions
bot
removed
the
inactive
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
There was a problem hiding this comment.
Pull Request Overview
This PR removes outdated registration instructions for Azure VM Image Builder in Azure Government regions. The change reflects that users no longer need to run a separate feature registration command (Microsoft.VirtualMachineImages/FairfaxPublicPreview) to use the service in USGov Arizona and USGov Virginia.
Key Changes
- Removed 13 lines of documentation describing the Fairfax preview feature registration process
- Eliminated both PowerShell and Azure CLI command examples for the obsolete registration step
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
5 participants
You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview command to register the provider Microsoft.VirtualMachineImages in AzureGov.