--- cuppy_hub: azure cuppy_path: changelog/2026-10-20-resource-manager-family.md cuppy_section: docs cuppy_doc: ARMZ-GWRV cuppy_doc_uuid: 155fd274-4e97-441d-b608-46e994d56865 cuppy_permalink: https://cuppy.io/azure/d/ARMZ-GWRV cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/azure/docs/changelog/2026-10-20-resource-manager-family cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: d8b3d2392f1651ee042685f9118b8406c7508a7d46a72d8f077f67cf02a1886e # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- # Azure hub — Resource Manager and IaC family (2026-10-20) ## What's in it 13 documents including this note, bringing the hub to 35: - **Error catalogues:** - `reference/arm/errors.md`: providers, subscriptions, quota, SKU, region, throttling, names, locks. - `reference/arm/deployment-errors.md`: templates, dependencies, concurrency, limits. - `reference/bicep/compile-errors.md` - `reference/azd/errors.md` - **References:** - Resource IDs, providers and API versions - Throttling and long-running operations - Locks and tags - Deployment stacks - **Guides:** deploying Bicep at the right scope; finding the real error in a failed deployment. - **Patterns:** Bicep that redeploys cleanly; Terraform `azurerm` as the alternative. ## 2026 changes captured - **`@azure/arm-resources` 8.0.0 (2026-07-17) no longer contains deployments.** They moved to `@azure/arm-resourcesdeployments` (`DeploymentsClient`; 2.0.0 on 2026-09-09). Long-running methods now return an awaitable poller, and `begin…AndWait` is deprecated. - **Terraform `azurerm` v5 no longer registers resource providers by default** (`resource_provider_registrations = none`), and `subscription_id` is required for plan and apply. The latest release is 5.10.0 (2026-10-15). - **Bicep 0.48.1 has no types for some newest stable API versions** (storage 2026-09-01, network 2026-03-01), which means no property checking. Examples use the newest version that has types. - **Azure CLI 2.75+ and 2.76+** add what-if short-circuit diagnostics and `--validation-level`. Deployment stack what-if is a separate command, `az stack-whatif`. - **Complete mode is being deprecated** in favour of deployment stacks. ## How it was verified - Sources were read from `azure-docs@dd032389`, `azure-dev-docs@dfe84c7e`, `azure-rest-api-specs@c783b658` and `hashicorp/terraform-provider-azurerm@3d141e8d`. - Bicep compiler messages were captured from Bicep CLI 0.48.1 by building deliberately broken files; they differ in wording from Microsoft's diagnostics page. - Every Bicep block compiles, and every `.bicepparam` file builds. - Each API version in the examples was tested for Bicep type availability. - All 180 `az` commands across the hub were checked against Azure CLI 2.91.0 help, with 0 issues. - All TypeScript blocks type-check under `tsc --strict` against the installed packages. ## Known gaps - Quotas through the `quota` CLI extension aren't covered (it isn't in the core CLI); quota reading is covered with core commands (`az vm list-usage`, `az vm list-skus`) until the cost and limits family. - ARM templates in JSON are covered through Bicep only; the error catalogues apply to both. --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 107 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/azure/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.