--image-version is incorrect parameter

[mbiver]

The command az sig image-version create uses the --image-version parameter with a managed image’s resource ID, which is incorrect. The --image-version flag is meant for specifying an existing image version (in a gallery) as the source, whereas a managed image source requires the --managed-image parameter.

Also, the az sig image-version create will fail if there is not already an image definition present. You may want to add a step to make sure and create the image definition using az sig image-definition create

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 3612e0f:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/migration/migration-managed-image-to-compute-gallery.md	✅Succeeded

For more details, please refer to the build report.

[ktoliver]

@AjKundnani

Can you review the proposed changes?

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

[github-actions]

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.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

[Copilot]

Pull request overview

This PR fixes a bug in the Azure CLI command example for migrating managed images to Azure Compute Gallery. The command was using an incorrect parameter (--image-version) that is meant for specifying an existing gallery image version as a source, when it should have been using --managed-image for a managed image resource ID source.

Key Changes:

• Corrected the az sig image-version create command parameter from --image-version to --managed-image for managed image migration