Skip to content

az vm update failed with 'Enabling zone movement' with unrelated action #33500

Closed
Closed
az vm update failed with 'Enabling zone movement' with unrelated action#33500
Assignees
yanzhudd
Labels
Auto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamBreaking ChangeComputeaz vm/vmss/image/disk/snapshotact-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Backlog

Description

@nbjohnson
Nicholas Johnson (nbjohnson)
opened on Jun 4, 2026

Describe the bug

When trying to run a az vm update --set tags command it failed with an unrelated 'zone movement' error

Related command

az vm update

Errors

Operation 'Enabling zone movement' is not supported on the resource 'VM as its not enabled for the region/ subscription.'

Issue script & Debug output

above error

Expected behavior

Expect az vm update commands to function and not fail related to an unspecified flag

Environment Summary

azure-cli 2.87.0

Additional context

This does not occur on the previous version 2.86, only on the latest 2.87. Wondering if some cli flag got set regarding zone movement so it tries to update on every update command, even those that don't specify it, and the region doesn't support that feature. This seems to break az vm update commands for me.

Activity

  1. Nicholas Johnson (nbjohnson)
    added
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    on Jun 4, 2026

  2. yonzhan commented on Jun 4, 2026

    @yonzhan
    Yong Zhang (yonzhan)
    on Jun 4, 2026
    Collaborator

    Thank you for opening this issue, we will look into it.

  3. microsoft-github-policy-service
    added
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    Computeaz vm/vmss/image/disk/snapshot
    on Jun 4, 2026
  4. microsoft-github-policy-service
    assigned
    Julie Zhu (yanzhudd)
    and
    Xing Zhou (zhoxing-ms)
    on Jun 4, 2026
  5. microsoft-github-policy-service
    added
    Auto-AssignAuto assign by bot
    Azure CLI TeamThe command of the issue is owned by Azure CLI team
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    act-observability-squad
    on Jun 4, 2026
  6. github-actions
    added
    Breaking Change
    on Jun 4, 2026
  7. Yong Zhang (yonzhan)
    removed
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    on Jun 4, 2026
  8. Yong Zhang (yonzhan)
    unassigned
    Xing Zhou (zhoxing-ms)
    on Jun 4, 2026
  9. Yong Zhang (yonzhan)
    added this to the Backlog milestone on Jun 4, 2026

  10. dspezia commented on Jun 12, 2026

    @dspezia
    Didier Spezia (dspezia)
    on Jun 12, 2026

    We got the same problem by running a command assigning a VM to a capacity reservation group.
    We run 2.87.

    az vm update -g "$AZURE_RG" -n "$VM_NAME" --capacity-reservation-group "$CRG_ID" -o none

(BadRequest) Operation 'Enabling zone movement' is not supported on the resource 'VM as its not enabled for the region/ subscription.'.
Code: BadRequest
Message: Operation 'Enabling zone movement' is not supported on the resource 'VM as its not enabled for the region/ subscription.'.

  11. MmAtBosch commented on Jun 12, 2026

    @MmAtBosch
    MM - Business (MmAtBosch)
    on Jun 12, 2026

    Same here when trying to swap an os disk on a vm

    ERROR: (BadRequest) Operation 'Enabling zone movement' is not supported on the resource 'VM as its not enabled for the region/ subscription.'.

  12. scarcher2 commented on Jun 12, 2026

    @scarcher2
    Scott Archer (scarcher2)
    on Jun 12, 2026

    We also experienced this issue when trying to update a tag.

  13. william051200 commented on Jun 15, 2026

    @william051200
    William (william051200)
    on Jun 15, 2026
    Member

    Hi Nicholas Johnson (@nbjohnson)

    Thanks for reporting this.

    We have identified the issue and have a fix in progress. It will be included in the next release, CLI version 2.88.

    In the meantime, please revert to version 2.86 as a workaround.

    cc Didier Spezia (@dspezia) MM - Business (@MmAtBosch) Scott Archer (@scarcher2)

  14. william051200 commented on Oct 21, 2026

    @william051200
    William (william051200)
    on Oct 21, 2026
    Member

    This regression is fixed in Azure CLI 2.88.0, released July 7, 2026, through #33441.

    Please upgrade to 2.88.0 or later using az upgrade and retry your command. Reverting to 2.86 is no longer necessary.

    Closing as resolved. If the same error persists after upgrading, please open a new issue with your CLI version, command, and sanitized --debug output.

  15. William (william051200)
    closed this as completedon Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Auto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamBreaking ChangeComputeaz vm/vmss/image/disk/snapshotact-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions