Azure Key Vault API 2026-03-01-preview retirement notice – Impacted subscription but no impacted resources

Sofia Bergqvist 20 Reputation points
2026-11-05T09:55:39.9433333+00:00

My team received the Azure Key Vault API 2026-03-01-preview retirement notice, and the message states that we received it because one or more of the Azure subscriptions we are associated with use an Azure Key Vault API 2026-03-01-preview.

However, when checking the details in the Service Health/Health advisories we found that we have one impacted subscription, but no impacted resources in that subscription.

We can see that impacted resources for retirements may take up to 2 weeks to appear after the event is published, but from what we can gather this event was published 2 months ago.

So our questions are: Why have we received this notice? Could it have been triggered by one-time requests to the Azure Key Vault API 2026-03-01-preview?

Azure Key Vault
Azure Key Vault

An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.

0 comments
Answer accepted by question author
Jose Benjamin Solis Nolasco 12,941 Reputation points Volunteer Moderator
2026-11-05T12:25:39.74+00:00

Welcome to Microsoft Q&A

Hello @Sofia Bergqvist I hope you are doing welll,

Yes, it is possible that you received the retirement notification even though no impacted resources are currently listed in Service Health.

The retirement notices are typically generated based on Microsoft's telemetry indicating that a subscription has used the affected API version. However, the presence of an impacted subscription does not always mean that there is a currently identifiable resource associated with that usage.

A few possibilities include:

  • The API version was used by a script, automation, SDK, test deployment, or one-time operation.
  • The affected resource has since been deleted or recreated.
  • Microsoft detected usage at the subscription level, but corresponding impacted-resource details are unavailable or incomplete.
  • There may be a delay or discrepancy between subscription-level telemetry and the impacted resources view.
  1. Review any custom automation, scripts, ARM/Bicep templates, Terraform code, or SDK-based applications that interact with Azure Key Vault.
  2. Search source repositories for:

2026-03-01-preview

  1. Review deployment pipelines that may have referenced preview API versions.
  2. Check Azure Activity Logs for Key Vault create/update operations that occurred during the timeframe in which the preview API was available.

Have you ever used preview ARM/Bicep templates, Terraform provider previews, SDK preview packages, or direct REST API calls against Azure Key Vault in that subscription? Even a one-time deployment could potentially explain why the subscription was flagged.

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.