Share via

Important update: Access to instance size flexibility ratios is changing on 9 May 2026

Priya Jayaraman 326 Reputation points
2026-04-09T08:54:15.6466667+00:00

Important update: Access to instance size flexibility ratios is changing on 9 May 2026

|| | -------- | COMMUNICATION:

You're receiving this notification because you’re associated with one or more Azure subscriptions using Azure Virtual Machine Reserved Instances.

After 9 May 2026, the instance size flexibility ratio file will no longer be updated in our documentation. To access the latest instance size flexibility ratios, you’ll have to use the Azure Catalogs API. Read this documentation page for details on using the API.

You may continue using the current instance size flexibility file until 30 August 2026. However, if your organization relies on this file for internal billing processes or cost management tools, we recommend transitioning to the new API as soon as possible.

Help and support

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and need technical help, please submit a support request.

COMMUNICATION:

You're receiving this notification because you’re associated with one or more Azure subscriptions using Azure Virtual Machine Reserved Instances.

After 9 May 2026, the instance size flexibility ratio file will no longer be updated in our documentation. To access the latest instance size flexibility ratios, you’ll have to use the Azure Catalogs API. Read this documentation page for details on using the API.

You may continue using the current instance size flexibility file until 30 August 2026. However, if your organization relies on this file for internal billing processes or cost management tools, we recommend transitioning to the new API as soon as possible.

Help and support

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and need technical help, please submit a support request.

Azure Cost Management
Azure Cost Management

A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.


1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-04-09T08:54:42.6366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The communication means that the static CSV file with instance size flexibility (ISF) ratios in the documentation will stop being updated after 9 May 2026, and will be fully deprecated for use after 30 August 2026. The ISF feature itself is not being removed; only the way to obtain the ratios is changing.

    Key impacts and required actions:

    1. What is changing
    • The current ISF ratio CSV file referenced from the “Virtual machine size flexibility with Reserved VM Instances” documentation will no longer receive updates after 9 May 2026.
    • After 30 August 2026, relying on that CSV for accurate ratios is not recommended; it may be outdated relative to new or changed SKUs.
    • Going forward, the authoritative source for ISF ratios will be the Azure Reservations Catalogs API (Azure Catalogs API).
    1. How to get ISF ratios going forward
    • Use the Azure Reservations Catalogs API to retrieve ISF data programmatically.
    • The API returns, per SKU, the ISF metadata in skuProperties:
      • InstanceSizeFlexibilityGroup (or ReservationsAutofitGroup in some responses) – the flexibility group name (for example, “Av2 Series”, “General Purpose Gen5”).
      • InstanceSizeFlexibilityRatio (or ReservationsAutofitRatio) – the ratio value used for ISF calculations.
    • The “Instance size flexibility (ISF)” documentation describes how to:
      • Call the Catalogs API for the relevant reservedResourceType (for example, Virtual Machines).
      • Parse the response and construct a CSV with columns:
        • InstanceSizeFlexibilityGroup
        • ArmSkuName
        • Ratio
    1. Recommended next steps for cost management/billing tools
    • If any internal billing, showback/chargeback, or cost optimization tooling currently reads the public CSV file directly or uses a copy of it:
      1. Implement a scheduled job (for example, PowerShell or another client) that calls the Azure Reservations Catalogs API.
      2. Parse skuProperties to extract the ISF group and ratio for each ArmSkuName.
      3. Generate and store an internal CSV or table in the same structure currently used by your tools (InstanceSizeFlexibilityGroup, ArmSkuName, Ratio).
      4. Update downstream tools to read from this new internal source instead of the public documentation CSV.
    • Follow the guidance in the ISF documentation about:
      • Pagination via nextLink.
      • Region-specific data (ratios can vary by region, so generate per-region files if needed).
      • Regular updates, because ratios may change as new VM sizes are introduced.
    1. Relation to reservations and VM retirements
    • ISF continues to apply to Azure Virtual Machine Reserved Instances as before: reservation benefits can be shared across sizes within the same flexibility group using the ratio values.
    • For VM sizes that are retiring (for example, certain families listed in the “Azure Virtual Machine size retirements in 2026” article), ISF ratios for replacement SKUs can be obtained via the same Catalogs API, which helps plan reservation coverage when migrating to suggested replacement sizes.
    1. Support
    • For complex scenarios (for example, large internal billing systems or cross-region reservation optimization), open an Azure support request as suggested in the communication, or use Microsoft Q&A for community guidance.

    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.