Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chrismrutledge
Copy link

You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview command to register the provider Microsoft.VirtualMachineImages in AzureGov.

You no longer have to run the separate Microsoft.VirtualMachineImages/FairfaxPublicPreview command to register the provider Microsoft.VirtualMachineImages in AzureGov.
Copy link
Contributor

@chrismrutledge : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 7214d0e:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/image-builder-overview.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Apr 22, 2025

@sumit-kalra

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 (#please-close) and move the commits to the private repository. If you need help moving the commits, contact the publicprs alias.

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Apr 22, 2025

```azurecli-interactive
az feature register --namespace Microsoft.VirtualMachineImages --name FairfaxPublicPreview
```

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.

Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment