az sql mi update --resource-group rgName --name sqlMiName --admin-password fails with ERROR: (InvalidParameterValue)

[FlukeFan]

Describe the bug

When using v2.78.0 of the cli, the following command:

az sql mi update --resource-group rgName --name sqlMiName --admin-password new-password

fails with:

ERROR: (InvalidParameterValue) Invalid value given for parameter LogicalAvailabilityZone can NOT be specified because ZonePinning feature is NOT yet supported!. Specify a valid parameter value.

This works fine with v2.77.0.

Related command

az sql mi update --resource-group rgName --name sqlMiName --admin-password new-password

Errors

ERROR: (InvalidParameterValue) Invalid value given for parameter LogicalAvailabilityZone can NOT be specified because ZonePinning feature is NOT yet supported!. Specify a valid parameter value.

Issue script & Debug output

n/a

Expected behavior

I expect this to not error.

Environment Summary

azure-cli: 2.78.0

Additional context

No response

[yonzhan]

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

[VZ-Mike]

Since 19.10.2025, we have the same Error with the following command:
az sql mi update --subscription mySubscription --resource-group myGroup --name mssql-mi-int-chn-srv01 --storage 8000
The problem lokks like with the update command to a sql mi instance.
Our host is in Switzerland north.

[msliwkaFP]

I have same error when I try change public endpoint:
az sql mi update -n SQLManagedInstanceName -g SQLResourceGroupName --public-data-endpoint-enabled true

[VZ-Mike]

For the moment we was go back to azure-cli: 2.77.0 version. This one works fine.

[azclibot]

Thanks for the detailed report! This looks like a regression introduced in v2.78.0.

Bug summary: az sql mi update --admin-password now fails with (InvalidParameterValue) because the CLI is unexpectedly sending LogicalAvailabilityZone in the request payload even when it wasn't specified. In v2.77.0 this worked correctly.

Root cause to investigate: Between v2.77.0 and v2.78.0, a change to the az sql mi update command likely started including LogicalAvailabilityZone as a non-null default or began serializing it unconditionally, causing the error on subscriptions where ZonePinning is not supported.

Fix direction: The sql mi update command should only include LogicalAvailabilityZone in the request body when the user explicitly passes a value for it. The fix is in src/azure-cli/azure/cli/command_modules/sql/ — check the ManagedInstance update model and ensure logical_availability_zone is only set when explicitly provided by the caller.

---

Posted by agent-assist (autonomous bug-fix pipeline).