-
Notifications
You must be signed in to change notification settings - Fork 200
Update image-builder-overview.md #209
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
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" |
|
||
```azurecli-interactive | ||
az feature register --namespace Microsoft.VirtualMachineImages --name FairfaxPublicPreview | ||
``` |
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.
_> 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview command to register the provider Microsoft.VirtualMachineImages in AzureGov.