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

Garima Saxena 0 Reputation points • Microsoft Employee

We have multiple api versions for microsoft advisor in preview but on portal i am only seeing one that is latest 2026-03-01-preview. Why older versions are not showing up on portal

Link : [https://learn.microsoft.com/en-us/rest/api/advisor/operation-groups?view=rest-advisor-2026-03-01-preview]

In earlier version we have certain resource types for which we have removed support in 2026-03-01-preview version. So wiki pages for those RTs are removed from 2026-03-01-preview version, hence there is no way to get definition for those apis which are still supported in older versions. Why only latest preview version is showing up on portal ?

  1. Suchitra Suregaunkar 14,595 Reputation points • Microsoft External Staff • Moderator

    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.

  2. Suchitra Suregaunkar 14,595 Reputation points • Microsoft External Staff • Moderator

    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.

  3. Garima Saxena 0 Reputation points • Microsoft Employee

    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]👁 User's image

Sign in to comment

1 answer

  1. AI answer

    The REST API documentation for Microsoft.Advisor is organized so that only the selected API version is shown at a time. The list of deployment API versions and their resource types is maintained separately under the Azure Resource Manager (ARM) template documentation.

    For Microsoft.Advisor, the available deployment API versions per resource type are listed in the ARM templates reference. For example:

    • Microsoft.Advisor/advisorScore has versions including 2022-10-01, 2023-01-01, 2023-09-01-preview, 2024-11-18-preview, 2025-01-01, 2025-05-01-preview, and 2026-02-01-preview.
    • Microsoft.Advisor/assessments has preview versions 2023-09-01-preview, 2024-11-18-preview, 2025-05-01-preview, and 2026-02-01-preview.
    • Microsoft.Advisor/configurations has versions from 2020-01-01 up through 2026-02-01-preview.
    • Microsoft.Advisor/metadata has preview versions 2025-05-01-preview and 2026-02-01-preview.

    The change log for Microsoft.Advisor shows when new resource types or versions were introduced or updated, but it does not expose every REST documentation view selector in the same way as the ARM template reference. Older API versions remain listed and usable for deployment via ARM/Bicep, but the REST documentation UI may only expose the latest preview view for a given REST collection.

    To obtain definitions for resource types that are no longer present in the latest preview documentation, use the ARM template reference pages for the specific resource type and API version, or the corresponding change-log entries, which enumerate the supported versions and link to their schemas.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer