Documentation for Microsoft.Advisor shows only latest preview api version 2026-03-01-preview and not the ol ones

Hello Garima Saxena The REST API reference documentation on Microsoft Learn is designed to surface only the latest stable and latest preview API version in the version selector dropdown. This is the expected behavior across all Azure REST API reference pages, it's not specific to Microsoft.Advisor. So when 2026-03-01-preview became the latest preview, the older preview versions (such as 2025-05-01-preview, 2024-11-18-preview, 2023-09-01-preview, etc.) were removed from the dropdown.

This creates a gap when resource types are removed in the latest preview, because there's no easy way to view their API definitions through the portal's version selector.

How to access older API version definitions:

1. ARM Template Reference (all versions listed): The ARM template reference for Microsoft.Advisor lists every supported API version for each resource type. You can find the full list here: Microsoft.Advisor – All Versions (ARM Template Reference) For example:
   • Microsoft.Advisor/recommendations has versions from 2017-03-31 through 2026-02-01-preview
   • Microsoft.Advisor/configurations has versions from 2020-01-01 through 2026-02-01-preview
   Each version links to its respective schema and property definitions.
2. Azure REST API Specs on GitHub (full OpenAPI/Swagger specs): The complete OpenAPI specifications for all older preview versions are maintained in the official Azure REST API specs GitHub repository: Microsoft.Advisor – Preview API Specs (GitHub) Available preview versions include:
   • 2016-07-12-preview
   • 2020-07-01-preview
   • 2022-02-01-preview
   • 2023-09-01-preview
   • 2024-11-18-preview
   • 2025-05-01-preview
   You can open the openapi.json file under each version folder to get the full API definition, including resource types that were removed in later previews. [github.com]
3. Azure Service Versioning Policy: For reference on how Azure handles API versioning and version lifecycle, you can review the official versioning policy here: Versioning Policy for Azure Services, SDKs, and CLI Tools

If you feel older preview versions should remain accessible in the REST API docs version selector especially when resource types are dropped, I'd recommend submitting feedback by filing an issue on the https://github.com/Azure/azure-rest-api-specs/issues.

Hope this helps! Please let me know if you need any further assistance.

Thanks,

Suchitra.

Hello Garima Saxena

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,

Suchitra.

Hey @Suchitra Suregaunkar

I just checked the link shared by you [https://learn.microsoft.com/en-us/azure/templates/microsoft.advisor/allversions]. Microsoft.Advisor/triageRexommendations and Microsoft.Advisor/triageResources correctly do not include 2026-03-01-preview version as we have removed support for these two RTs in 2026-03-01-preview version but Microsoft.Advisor/resiliencyReviews do support 2026-03-01-preview version but its not there in the list. I am not sure why Could you help understand this as well?

This document clearly shows resiliency reviews with 2026-03-01-preview version [https://learn.microsoft.com/en-us/rest/api/advisor/resiliency-reviews?view=rest-advisor-2026-03-01-preview]

Hello Garima Saxena

The two pages are generated from different source pipelines, which is why you're seeing this mismatch:

1. REST API Reference Page (/rest/api/advisor/...)

This page is generated directly from the OpenAPI / Swagger specifications published in the azure-rest-api-specs GitHub repository. As soon as a new API version's spec is merged there, the REST API docs pick it up. That's why 2026-03-01-preview is already visible for resiliencyReviews.

2. ARM Template Reference Page (/azure/templates/microsoft.advisor/allversions)

This page is generated from the Azure Resource Manager JSON schemas hosted at https://schema.management.azure.com/. These schemas are auto-generated separately from the Swagger specs, and the new API version has to be added/registered to these schemas through a separate build/sync process.

So the version not appearing on the ARM template page typically means one of the following:

• (a) Sync/publishing lag — The schema generation pipeline hasn't yet processed 2026-03-01-preview for resiliencyReviews. This is the most common cause and usually resolves itself within a few release cycles. Third-party trackers like AzAdvertizer also reflect this — as of their last sync, only versions up to 2026-02-01-preview are listed for this RT.
• (b) No deployable (PUT) operations in this version — The ARM template reference only lists API versions that include resource-definition (deployable) operations. Looking at the 2026-03-01-preview spec for resiliencyReviews, it only exposes GET and LIST operations — there are no PUT/create-or-update operations. Since ARM templates (and Bicep) are about deploying resources, an API version that only contains read operations may be intentionally excluded from the /azure/templates/... reference, because there's nothing for a template author to deploy at that version.

In short — the discrepancy is expected behavior, not a documentation bug. The REST API page is the authoritative source for "what API operations exist in version X," and the ARM template page is the authoritative source for "what API versions can be used to deploy this resource type."

You can verify the operations supported in 2026-03-01-preview directly from the GitHub specs: Microsoft.Advisor – ResiliencyReview spec (azure-rest-api-specs) [github.com]

If you check the ResiliencyReview.tsp (and the corresponding routes.tsp) under the latest preview folder, you'll see exactly which operations are defined, confirming whether it's read-only or includes write/PUT operations.

Official reference on how the ARM template reference works:

For background on how ARM template documentation gets its data and version list: Azure resource reference – Bicep, ARM template & Terraform AzAPI reference.

Thanks,
Suchitra.