VM SKU retirement visibility in Service Health vs Advisor

Dhruv Jain 0 Reputation points Microsoft Employee
2026-08-20T22:11:26.4733333+00:00

I was looking into automated alerting for Azure VM SKU retirements (e.g., D/Ds/Dv2/Dsv2 series retiring May 2028). I see these retirements in Azure Advisor but they do NOT appear in Service Health

  1. Are VM SKU retirements expected to appear in Service Health retirement events? If so, when?
  2. Is Advisor the canonical source for VM SKU retirement impacted resources?
Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,330 Reputation points
    2026-09-05T11:45:01.52+00:00

    I think vm‑sku retirements may not show in Service Health, and Advisor is where Azure lists the impacted VMs. and u can see everything by running one Azure Resource Graph query across ur subs.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-08-20T22:11:41.7466667+00:00

    Yes. Service retirements are expected to be surfaced through Azure Service Health as the lifecycle-awareness signal, and Azure Advisor as the resource-level action signal.

    For VM SKU retirements specifically:

    1. Service Health is for awareness, not the primary impacted-resource source.
      Service Health provides notification that a retirement is announced and includes a tracking ID for correlation. It is the recommended signal for early awareness, timeline tracking, and portfolio-level governance.
    2. Advisor is the canonical source for impacted resources and remediation workflow.
      Advisor is the recommended action path when the goal is to identify impacted resources, track remediation, and drive migration work. Advisor retirement recommendations are resource-scoped and actionable.
    3. If a retirement is visible in Advisor but not in Service Health, use Advisor for execution.
      The guidance explicitly separates the two roles: Service Health tells what is changing; Advisor tells what to do. For impacted-resource details, Advisor recommendations, the Service Retirement workbook, and related APIs are the supported channels.
    4. Service Health visibility is not guaranteed to be a complete substitute for Advisor.
      The guidance notes that tenant-level Service Health alerts do not include all subscription-level events, retirement notifications are not inherently consolidated, and full visibility can require both tenant-level and subscription-level rules.
    5. For automation, the recommended pattern is:
      • Use Service Health if the requirement is announcement awareness and tracking ID capture.
      • Use Advisor if the requirement is impacted-resource inventory and remediation tracking.
      • If starting from a Service Health retirement signal, use the tracking ID with Azure Resource Graph to identify impacted resources, then track remediation in Advisor.

    So for the two questions directly:

    • Are VM SKU retirements expected in Service Health?
      Retirement announcements are expected to use Service Health as the awareness signal, but the available guidance does not provide a VM-SKU-specific timing guarantee for when a given SKU retirement will appear there.
    • Is Advisor the canonical source for VM SKU retirement impacted resources?
      Yes. Advisor is the recommended and actionable source for resource-level retirement recommendations and impacted-resource details.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.