Skip to content

[AI-Suggested] Content update request from Product Release signal: azure-cli azure-cli-2.90.0 #21

Open
Open
[AI-Suggested] Content update request from Product Release signal: azure-cli azure-cli-2.90.0#21
Labels
akashdubey/mgrazure-cli/svcazure/svcchange-detection-agentproduct-release/sigtype

Description

@learn-build-service-ppe
learn-build-service-ppe
bot
opened on Sep 1, 2026

Background

A recent product update has been released that may impact our documentation. This could include new features, changes to existing functionality, or other product enhancements.
Your Action Required: Please review the suggestions below and update the relevant documentation to ensure accuracy and completeness.

Signal Details:

Source Signal Summary

Details
  • az cosmosdb restore now supports a new --disable-local-auth three-state flag to disable key-based authentication on the restored Azure Cosmos DB account (requires documenting the new parameter/behavior in the az cosmosdb restore command reference). (PR #33303)
  • az cosmosdb fleet, az cosmosdb fleetspace, and az cosmosdb fleetspace account command groups are no longer marked is_preview=True (update any Azure CLI docs/help that label these Cosmos DB fleet/fleetspace commands as preview). (PR #33303)
  • az cosmosdb mongodb role definition create/update and az cosmosdb mongodb user definition create/update now convert the --body JSON for Privileges/Roles into the required SDK model shape (documented body schema using PascalCase keys like Privileges[].Resource.{Db,Collection}, Privileges[].Actions, and Roles[].{Db,Role} should now be accepted reliably instead of failing with newer Cosmos DB API versions). (PR #33303)
  • Behavior-only: Azure Cosmos DB network rule output transformations now consistently return the historical ignoreMissingVnetServiceEndpoint casing and omit the additionalProperties artifact when present (update any az cosmosdb ... network rule examples that show the old casing or include additionalProperties in JSON output). (PR #33303)
  • Azure CLI’s Cosmos DB management-plane support is updated via azure-mgmt-cosmosdb==10.0.0 to align with API version 2026-03-15 (if docs mention supported Cosmos DB ARM API versions/features gated by this API version, they may need refreshing). (PR #33303)
  • Azure CLI az network public-ip create and az network public-ip update now support a new --ddos-custom-policy parameter to associate a DDoS custom policy with a Public IP; the value can be a policy name or full resource ID (names are auto-expanded to a Microsoft.Network/ddosCustomPolicies resource ID in the current subscription/resource group), and update now clears ddosCustomPolicy when unset; users should note the service limitation that DDoS custom policies can only be attached to instance-level Public IPs (NIC/VM) or Load Balancer frontend IP configurations—attempts to attach to a standalone Public IP are rejected by the service. (PR #33812, PR #33869, PR #33978)
  • Azure CLI az storage blob upload now treats an explicitly empty --data '' / --data "" value as valid input (uploads an empty blob) by validating --data based on presence (None vs provided) rather than truthiness; the existing mutual-exclusion and required-input rules for --file and --data remain unchanged. (PR #33803, PR #33869)
  • Azure CLI (AKS) adds Cluster Autoscaler (CAS) support for VirtualMachines (VMS) agent pools via a new command group az aks nodepool auto-scale with add / update / delete subcommands to manage virtualMachinesProfile.scale.autoscale profiles (using --node-vm-size, --min-count, --max-count, and --current-node-vm-size), and updates existing autoscaler workflows so that az aks nodepool add can create VMS pools directly in autoscale mode with --enable-cluster-autoscaler, az aks nodepool update --enable-cluster-autoscaler converts all VMS manual scale profiles to autoscale profiles using the provided min/max, az aks nodepool update --disable-cluster-autoscaler converts autoscale profiles back to manual (defaulting manual count from autoscale minCount), and --update-cluster-autoscaler is now explicitly rejected for VMS pools with guidance to use az aks nodepool auto-scale update instead (VMSS behavior unchanged). (PR #33801, PR #33869, PR #33978)
  • Azure CLI az aks create --sku automatic now treats Automatic SKU clusters as not supporting SSH key configuration: the CLI no longer reads or auto-generates an SSH key / Linux profile by default for Automatic SKU, and it now fails early with a clear error if users explicitly set --ssh-key-value (non-default) or --generate-ssh-keys while using --sku automatic (so docs/examples for Automatic SKU should omit SSH-key flags and note they’re unsupported; users no longer need --no-ssh-key just to avoid SSH key handling). (PR #33820, PR #33869)
  • Azure CLI az aks create --sku automatic and AKS Azure Monitor metrics enablement flows now explicitly wait for ARM long-running operations (begin_create_or_update[_by_id]) to complete by calling .result() on the returned LRO poller; this changes the documented behavior/expectation from “command may return after request acceptance” to “command returns after Azure Monitor metrics artifacts (DCE/DCR/DCRA/Azure Monitor Workspace/Grafana link) finish provisioning,” which can increase command runtime but avoids returning before dependent resources are ready, and will surface failures synchronously. (PR #33734, PR #33869)
  • Azure CLI az aks nodepool rollback warning behavior updated to distinguish upgrade-channel settings: if upgradeChannel (Kubernetes auto-upgrade) is enabled, it still warns that rollback will not succeed until auto-upgrade is disabled; if only nodeOSUpgradeChannel is enabled, it now warns that the orchestrator (Kubernetes version) rollback will proceed but the node image rollback will not succeed (and no warning is emitted when both are disabled). (PR #33854)
  • Azure CLI az aks create and az aks update add new boolean flags --enable-upstream-kubescheduler-user-configuration (create/update) and --disable-upstream-kubescheduler-user-configuration (update only) to control AKS “user-defined scheduler configuration for kube-scheduler upstream”; these flags set the managed cluster property .schedulerProfile.upstream.schedulerConfigMode to ManagedByCRD when enabled and to Default when disabled, and az aks update now errors if both flags are provided together (mutually exclusive). (PR #33934)
  • Azure CLI az aks update (and az aks create) Azure Container Storage (ACStor) behavior: improved detection of existing ACStor extension configurationSettings by treating boolean values case-insensitively ("true"/"false" as well as "True"/"False") and supporting native JSON booleans (true/false), preventing --enable-azure-container-storage from missing active cluster configuration and incorrectly falling back to legacy defaults. (PR #33938)
  • Azure CLI az ssh vm (SSH certificate flow) now works in Azure Cloud Shell when signed in with a user account, because the CLI authentication guard in Profile.get_msal_token() no longer blocks Cloud Shell sessions; managed identity (az login --identity) remains unsupported and still raises AuthenticationError: VM SSH currently doesn't support managed identity. (PR #33860)
  • Azure CLI Cognitive Services management commands now pin azure-mgmt-cognitiveservices to exactly 15.0.0b4 (instead of a ~=15.0.0b4 range) to preserve support for Compute operations in Private Preview; documentation that mentions availability/behavior of Cognitive Services Compute operations via the Azure CLI should align with this preview dependency constraint and potential limitations. (PR #33870)
  • Service Bus management-plane changes (targeting API 2026-01-01) and behavior updates: az servicebus namespace create/update add --ip-address-type {DualStack,IPv4}, add --platform-capabilities (including confidential-compute mode={Enabled,Disabled}), extend --minimum-tls-version to include 1.3, enforce namespace --name length validation (min 6 / max 50), and remove the cluster-arm-id field from GeoDR replica location input; az servicebus namespace private-endpoint-connection delete no longer prompts for confirmation; and Service Bus help text/examples were regenerated/updated (including az servicebus summary now “Manage Service Bus.”). (PR #31970, PR #33869)
  • Azure CLI Service Bus “list” style commands now support server-driven pagination via newly added pagination_limit and pagination_token parameters (AAZ paging) on commands including az servicebus namespace list, az servicebus namespace authorization-rule list, az servicebus namespace network-rule-set list, az servicebus namespace private-endpoint-connection list, az servicebus georecovery-alias list / az servicebus georecovery-alias authorization-rule list, az servicebus migration list, az servicebus queue list / az servicebus queue authorization-rule list, az servicebus topic list / az servicebus topic authorization-rule list, az servicebus topic subscription list, and az servicebus topic subscription rule list (and az servicebus namespace private-link-resource show, which returns a collection). (PR #31970)
  • Azure CLI Service Bus messaging-entity commands add support for user metadata: --user-metadata is now available on az servicebus queue create/update, az servicebus topic create/update, and az servicebus topic subscription create/update; additionally, az servicebus queue update adds new updatable flags --enable-partitioning, --enable-duplicate-detection/--duplicate-detection, and --enable-session. (PR #31970, PR #33869)
  • Azure CLI az servicebus georecovery-alias create no longer requires --partner-namespace (parameter changed from required to optional). (PR #31970, PR #33869)
  • Application Gateway WAF policy managed rules update validation/behavior: az network application-gateway waf-policy managed-rule rule-set update now allows --group-name to be specified without --rule, creating an empty rule-group override that disables all rules in the specified group; specifying --rule without --group-name remains invalid and now errors with --group-name must be provided when --rule is specified. (PR #33871, PR #33869)
  • Azure Event Hubs management updates (AAZ latest) and validation changes: many az eventhubs commands move to ARM API version 2026-01-01 and add/extend parameters, including az eventhubs namespace create/update --ip-address-type (DualStack/IPv4), --minimum-tls-version now including 1.3, identity shorthand flags --mi-system-assigned/--mi-user-assigned, and --platform-capabilities (including nested confidential-compute mode=Enabled|Disabled); az eventhubs namespace schema-registry create/update expands --schema-type choices to include Json and ProtoBuf; az eventhubs cluster create/update add --confidential-compute-mode (alias --mode) and --zone-redundant, and az eventhubs cluster list adds --pagination-limit/--pagination-token; geo-data-replication location parsing for az eventhubs namespace normalizes role-type values to Primary/Secondary case-insensitively, treats missing cluster-arm-id as unset (no longer sends empty string/null), and preserves existing maxReplicationLagDurationInSeconds when adding locations; breaking validation enforces new name length rules across az eventhubs namespace *, az eventhubs eventhub *, and related subcommands (namespace/event hub names now require 6–50 chars where previously 4–48 could pass CLI-side validation). (PR #33830, PR #33869)
  • Azure CLI packaging now builds and publishes official Azure Linux–based artifacts for Azure Linux 4.0 (Beta) in addition to Azure Linux 3.0 (container images and RPMs generated side-by-side, using mcr.microsoft.com/azurelinux-beta/base/core:4.0 for AZL4 and mcr.microsoft.com/azurelinux/base/core:3.0 for AZL3), and extension management (e.g., az extension add) now supports installing psycopg2 system dependencies on Azure Linux 4 by detecting AZL4 and using tdnf install (installing gcc, libpq-devel, python3-devel, binutils, glibc-devel, kernel-headers with a warning and sudo when not root); if tdnf is missing or dependency installation fails, the CLI raises a user-facing error. (PR #33850)
  • Azure CLI Debian/Ubuntu packaging pipeline now includes Ubuntu 26.04 (codename Resolute) in the build matrix, which may require updating Azure CLI installation documentation (APT/deb packages) that lists supported Ubuntu versions/codenames. (PR #33791)
  • Azure CLI standalone distribution via the Azure-managed Homebrew Cask (brew tap Azure/homebrew-azure-cli / brew install --cask azure-cli) is extended to include Linux ARM64 and Linux x86_64 alongside macOS, with the Cask now selecting archives using the azure-cli-<version>-<os>-<arch>.tar.gz pattern and corresponding per-platform SHA256 values; installation still relies on Homebrew Python (e.g., python@3.14) (no bundled Python), and the Cask template removes Homebrew’s deprecated verified: field. (PR #33927)
  • Azure CLI updated to 2.90.0 (including azure-cli-core), which may require updating any installation/release documentation that pins or references the previous Azure CLI version (2.89.1) and its bundled help/command indexes. (PR #33978)
  • Azure CLI (Compute az vmss) adds preview support for Virtual Machine Scale Set lifecycle hooks and their events via two new command groups: az vmss lifecycle-hook (add, update, remove, show, list) and az vmss lifecycle-hook-event (list, show, update, approve, reject); includes new/updated command parameters and rules such as --type (supported hook types include UpgradeAutoOSScheduling and UpgradeAutoOSRollingBatchStarting), hook configuration with --wait-duration (ISO 8601 duration) and --default-action (Approve/Reject), remove requiring exactly one of --type or --all, and event actions using --name/-n, optional --instance-ids (uniform instance IDs or flex VM names; omitted applies to all target resources), update requiring at least one of --action-state (Approved/Rejected) or --wait-until (UTC ISO 8601 timestamp) with --instance-ids requiring --action-state; az vmss lifecycle-hook-event update/approve/reject resolves --instance-ids to target resource IDs by querying the event (and VMSS instances when needed) and now polls the underlying PATCH as an LRO to handle the service returning HTTP 202. (PR #33758, PR #33978)
  • Open Capacity Reservation support across Compute commands: az capacity reservation group create/update now support --reservation-type {Block,Open,Targeted} (document that the reservation type is immutable after creation, even though the flag is present on update); az vm create/update and az vmss create/update add --disable-capacity-reservation-assignment (alias --no-cap-reservation) to explicitly opt out of capacity reservation association (VMSS: mutually exclusive with --capacity-reservation-group, applies only to parent VMSS on update (blocked with --instance-id), and when true clears any existing capacityReservationGroup from the update payload); outputs and API versions update to Microsoft.Compute 2026-04-01 for several AAZ-backed az capacity reservation*, az vm*, and az vmss* commands, surfacing additional JSON fields (e.g., systemData, capacity reservation scheduleProfile / reservationStateInfo, utilizationInfo.usedReservedCountBySubscription, VM/VMSS capacity reservation fields like disableCapacityReservationAssignment / capacityReservationType, and VMSS enum priority=SpotPlus plus other new nested properties/args such as hardware-profile processor-mode, storage-profile disk-api-version, sku-profile automatic-sku-migration-policy, and interconnect block/group profiles). (PR #33901, PR #33929, PR #33978)
  • Breaking: Azure CLI az vm deallocate is no longer registered in the az vm command group (the command is removed from the Azure CLI command table), so scripts/docs referencing az vm deallocate need an alternative. (PR #33869)
  • Azure CLI az vm boot-diagnostics get-boot-log no longer crashes when the VM’s boot diagnostics are stored in a custom (non-managed) Storage Account, restoring the command’s ability to retrieve the boot log in that scenario. (PR #33872)
  • Azure CLI az network private-endpoint-connection (approve/reject/show/list/delete) and az network private-link-resource list now accept Microsoft.HardwareSecurityModules/paymentHsmClusters as a valid --resource-provider choice (using API version 2025-12-01-preview), enabling these commands to manage Private Endpoint Connections / Private Link Resources for Payment HSM clusters. (PR #33889)
  • Azure CLI az sql server deleted-server list now makes --location optional: when --location <region> is provided it continues to list deleted SQL servers scoped to that region, but when omitted it lists deleted SQL servers across the subscription (all locations) using the subscription-level list API; the command help and examples are updated to reflect the new subscription-wide usage. (PR #33918)
  • Azure CLI az sql mi link (Managed Instance link / distributed availability group) now supports multi-database links via the 2025-08-01-preview API: az sql mi link create adds --link-mode {SingleDatabase,MultiDatabase}, az sql mi link update adds --databases (list of objects with database-name, only updatable when the link is in MultiDatabase mode), and az sql mi link create/update/show/list/failover now return the linkMode property in command output. (PR #33874, PR #33978)
  • Azure CLI az sql server update: Updated handling of --soft-delete-retention-days to follow the standard update/PUT pattern—when the flag is omitted the command now preserves the existing soft-delete retention value instead of forcing retention_days=None into the PUT payload (when provided, it still sets the value). (PR #33933)
  • Azure CLI az bicep snapshot (Validate mode) now preserves and surfaces Bicep CLI stdout when the underlying Bicep process exits non-zero (e.g., validation detects resource changes): the raised CLI error message appends any reported “detected changes” output after the parsed stderr diagnostics, instead of discarding stdout. (PR #33925)
  • Azure CLI az bicep publish help text examples correct the syntax for overwriting an existing tag by moving --force out of the quoted --target value: --target "br:{registry}/{module_path}:{tag}" --force (previously showed --target "… --force"). (PR #33517)
  • Azure CLI az deployment * what-if output now appends a new “NOTICE!” line in the existing noise disclaimer pointing users to “Deployment Stacks What-If” (https://aka.ms/stackswhatifGA) as the recommended way to get what-if results “without noise”. (PR #33943)
  • Azure CLI az acr network-rule list / az acr network-rule add / az acr network-rule remove now correctly reads/writes virtual network rules using virtualNetworkSubnetResourceId, fixes virtualNetworkResourceId previously being returned as null, returns both virtualNetworkResourceId (legacy/back-compat) and virtualNetworkSubnetResourceId (correct field), and az acr network-rule remove now actually removes the matching virtual network rule (it previously could be a silent no-op). (PR #33685, PR #33978)
  • Azure CLI az keyvault control-plane command groups now target ARM API version 2026-02-01 via azure-mgmt-keyvault upgrade to 14.0.1 (retirement of <2026-02-01 on 2027-02-27), and az keyvault mhsm recover now sends ManagedHsm.properties using wire-format camelCase keys (tenantId, createMode), fixing BadRequest failures caused by azure-mgmt-keyvault 14.x “hybrid model” serialization. (PR #33895)
  • Azure CLI az containerapp job update --no-wait no longer crashes with TypeError: argument of type 'NoneType' is not iterable; the command now correctly short-circuits the post-update provisioning-state check when --no-wait is used, aligning behavior with az containerapp update and restoring the documented expectation that --no-wait returns immediately without error. (PR #33807)
  • Azure CLI az consumption usage list (with --include-meter-details) and az consumption pricesheet show --include-meter-details now correctly preserve meterDetails.totalIncludedQuantity from the service response (instead of incorrectly copying meterDetails.pretaxStandardRate). (PR #33908)
  • Azure CLI az storage commands now use Track 2, client-factory-backed argument completers for --container-name, --blob-name, --directory-name, --file-name, and stored access policy --policy-name completion (completion is skipped unless required parent arguments like container_name/share_name are present), and az storage file generate-sas help text for --policy-name was corrected to refer to the file share’s ACL (instead of a container’s ACL). (PR #33793)
  • Azure CLI az storage fs file download now streams downloads to the destination file using the Storage SDK readinto(stream) instead of buffering via readall(), fixing download failures when the service response includes Content-Encoding: deflate. (PR #33730)
  • Azure CLI App Service adds/updates several Linux-focused features:
  • New preview az webapp exec for Linux web apps only, enabling container interaction via --mode shell (default) and --mode execute, with constraints/flags including --shell absolute path override (shell mode), --command vs --shell-command (<shell> -c <command>; default /bin/bash; --shell only valid with --shell-command), --working-directory/--cwd (absolute path), --instance/-i (shell mode single instance; execute mode supports comma-separated IDs or all validated against az webapp list-instances), and --slot/-s; sessions may end after ~3 hours inactivity or if the instance is reimaged/updated; breaking: adds --target {app,kudu} (default app) for shell mode to choose container, --target kudu is rejected in execute mode.
  • az webapp troubleshoot collect network-capture (preview) to run a bounded tcpdump on a single Linux App Service worker instance and return authenticated Kudu links (raw .pcap download URL and analysis report URL), with --duration (default 60, range 1-300), --instance/-i (required for non-interactive use; otherwise prompts), --slot/-s, and --collect-only (omit analysis link), and limitations (Linux web apps on dedicated App Service plans only; one instance per invocation; “no packets” messaging; concurrent-capture/feature-unavailable errors from Kudu).
  • az webapp deploy adds --tag to set a friendly name for a deployment; if provided for a non-Linux web app it is ignored with a warning (--tag is only supported for Linux web apps and will be ignored.).
  • az webapp create adds a new --enriched-errors three-state flag (Linux only) that, when enabled, shows context-enriched diagnostics (classified error codes/stages, suggested fixes, and a Copilot prompt) for both client-side Linux runtime validation failures and ARM provisioning failures (including raw error text truncated to ~500 chars).
  • Node.js 26 runtime identifier is standardized to NODE|26 (drops -lts/LTS suffix) for Windows+Linux App Service plans; az webapp list-runtimes output shows NODE|26 (deduplicating prior Current/LTS rows), az webapp create accepts NODE|26-lts / NODE|26LTS as aliases resolving to NODE|26 (Node >= 26), Linux sets linuxFxVersion=NODE|26 while Windows remains ~26, and GitHub Actions runtime detection/display reports NODE|26 with version 26.x.
  • az webapp config set --generic-configurations now correctly persists camelCase site configuration properties (for both key=value and JSON input), preserving camelCase keys and coercing 'true'/'false' strings to booleans, fixing prior silent ignore of valid properties like webJobsEnabled. (PR #33640, PR #33954, PR #33949, PR #33940, PR #33936, PR #33864, PR #33826, PR #33978)
  • Azure CLI App Service plan and SKU surface updates: az appservice plan create/update, az appservice list-locations --sku, and az webapp up --sku now support Isolated v4 SKUs (I1V4–I6V4, I1MV4–I5MV4) mapped to ARM tier IsolatedV4, validated as requiring an App Service Environment (ASE) (and az webapp up --app-service-environment help now states it supports Isolated v2 or Isolated v4), and zone redundancy validation now explicitly permits IsolatedV4 while enforcing ASE/SKU compatibility rules; additionally, az appservice plan create help/examples were corrected so Windows examples explicitly include --is-linux false to avoid accidentally creating Linux plans. (PR #33892, PR #33828)
  • Breaking: Azure CLI az redis import now requires confirmation before running because the operation deletes all existing cache data and makes the cache inaccessible during import; interactive runs prompt, and non-interactive/scripts must pass the new --yes/-y flag to skip the prompt (help text/examples updated accordingly). (PR #33905, PR #33978)
  • Azure CLI az aro adds a new az aro identity command group for the managed identity workflow (az aro identity get-required and az aro identity create-required), and az aro create --enable-managed-identity/--enable-mi can auto-generate required identities/assignments when identity args aren’t provided (with updated mutually-exclusive flag validation and requiring --version when enabling managed identity without providing identities); az aro create help now documents a default worker VM size in --worker-vm-size help text ([Default: Standard_D4s_v5]). (PR #33912, PR #33978)
  • Azure CLI az postgres flexible-server replica promote planned switchover promotions no longer fail with MissingRequiredParameter because the PATCH now includes properties.sourceServerResourceId populated from the existing replica’s source_server_resource_id. (PR #33777)
  • Azure CLI az postgres flexible-server maintenance-event list no longer auto-registers or passes an unsupported --ids parameter, fixing a previously unavoidable TypeError and allowing the command to run with --resource-group and --server-name as documented. (PR #33847)
  • Azure CLI az postgres flexible-server create: when --sku-name is not provided, the command now selects the default SKU based on the service-reported default_sku_name for the chosen --tier (instead of sorting available SKUs and picking the first). (PR #33897)
  • Azure CLI az postgresql db create now correctly applies the --charset and --collation flags when creating a database (fixes a regression in CLI >= 2.84.0 where these options were ignored); both flags still must be provided together. (PR #33951)
  • MySQL Flexible Server behavior/help fixes: az mysql flexible-server ad-admin create now builds payloads using the AzureADAdministrator SDK model (fixing user-assigned identity scenarios after SDK upgrade); az mysql flexible-server firewall-rule create now uses the FirewallRule SDK model to send the expected { "properties": { "startIpAddress": ..., "endIpAddress": ... } } wire shape (fixing InternalServerError regressions); az mysql flexible-server geo-restore no longer copies the source server’s storage_redundancy into the target payload (target region selects a supported redundancy automatically); and az mysql flexible-server list-skus --output table now correctly renders single-item capability results and tightens error handling. (PR #33838, PR #33865, PR #33814, PR #33747)
  • Azure CLI core request handling (used by az rest via send_raw_request and by AAZ-generated commands’ client-side pagination via AAZPaginationTokenArgFormat) now normalizes URLs before origin validation and before sending requests, and will reject non-normalized/ambiguous URLs (e.g., protocol-relative or double-slash paths like https://management.azure.com//attacker.example/leak, control-character/backslash tricks, or inputs whose requests-prepared URL changes origin), which can surface as InvalidArgumentValueError and may stop pagination when a nextLink is not a normalized trusted cloud endpoint (is_trusted_cloud_endpoint/is_same_origin). (PR #33960)
  • Azure CLI bundled-build/security dependency changes: bundled requirements bump cryptography from 46.0.7 to 48.0.1 (remediating GHSA-537c-gmf6-5ccf “Vulnerable OpenSSL included in cryptography wheels”) and pyOpenSSL from 26.0.0 to 26.2.0; packaging also pins paramiko==5.0.0 in bundled requirements and relaxes setup.py to paramiko>=2.0.8,<6.0.0 (Paramiko 5 removes SHA-1 ssh-rsa signature support, which may break Azure CLI SSH/SFTP scenarios against legacy SHA-1-only servers). (PR #33944, PR #33946)
  • Help-text/grammar-only updates in CLI reference output: az mysql flexible-server import create long-summary grammar fix (“a Azure” → “an Azure”) and additional “a Azure …” → “an Azure …” corrections across az cosmosdb and az aks (ACS module, Azure Dev Spaces). (PR #33819, PR #33884)

Suggestions

Instructions for Copilot: Copilot should only fix suggestions with a checkmark and do not make any updates for unchecked suggestions.

Note

Suggestions are generated by AI and they should be reviewed by human before assigning it to Copilot. Please uncheck the ones you don't want Copilot to work on. Then assign this issue to Agent (GitHub Copilot).

  • docs-ref-conceptual/Latest-version/release-notes-azure-cli.md:
    • [Improvements] In the “September 01, 2026 / Version 2.90.0” section, add an “Event Hubs” entry that documents the breaking change in CLI validation for Event Hubs resource names (namespace/event hub and related subcommands), specifically the enforced 6–50 character name length requirement (previously 4–48 could pass CLI validation), so users are not surprised by post-upgrade command/script failures. (PR #33830, PR #33869)
  • docs-ref-conceptual/Latest-version/install-azure-cli-macos-preview.md:
    • [Correction Required] In the Troubleshooting > Unable to find Python or installed packages section, update the guidance and example commands that instruct users to install/relink python@3.13 so they match the Python version actually used/required by the Azure CLI Homebrew Cask dependency chain (for example, python@3.14 per the change). Otherwise, a reasonable user following the troubleshooting steps can remain broken because they relink the wrong Homebrew Python formula. (PR #33927)
  • docs-ref-conceptual/Latest-version/choose-the-right-azure-command-line-tool.md:
    • [Correction Required] In the “Azure CLI vs Azure PowerShell: Side-by-side Command Comparison” section, under “Manage Azure Virtual Machines”, update the “Stop & Deallocate VM” row to remove the invalid az vm deallocate --name myVM --resource-group <ResourceGroupName> command and replace it with the currently supported Azure CLI command/workflow for deallocating a VM. (PR #33869)
  • docs-ref-conceptual/Latest-version/release-notes-azure-cli.md:
    • [Improvements] In the App Service section entry az webapp create: update the release note text to reflect that --enriched-errors is Linux-only, so users don’t assume it applies to Windows webapp creation and encounter argument/validation failures.
    • [Improvements] In the App Service section entry az webapp create: update the description to reflect that --enriched-errors is a three-state flag (explicit enable/disable vs omitted/default), to avoid users forming an incorrect understanding of how to control the behavior.
    • [Improvements] In the App Service section entry az webapp create: refine the description of what the flag does to match the new behavior (context-enriched diagnostics including classified stages/codes, suggested fixes, Copilot prompt; applies to both client-side Linux runtime validation failures and ARM provisioning failures), so users aren’t misled about the scope of diagnostics surfaced.

📚 To learn more about agentic content maintenance workflow, visit Agentic workflow for Learn content maintenance. Sign in using Learn Profile to access the content on this link.

💬 Share your feedback on the Learn Content Maintenance Agentic Workflow here.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    akashdubey/mgrazure-cli/svcazure/svcchange-detection-agentproduct-release/sigtype

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions