Azure Key Vault API 2026-03-01-preview retirement — How can I identify the calling application?

Kevin Grenier 0 Reputation points
2026-11-04T20:42:07.6133333+00:00

I received an Azure Service Health advisory (SH8B-Q4G) indicating that my subscription has used Azure Key Vault management API version 2026-03-01-preview, which is scheduled for retirement on January 31, 2027.

I'm trying to identify exactly which application, service or integration made these API requests before changing anything in production.

Environment:

  • Azure subscription with Basic support

One Azure Key Vault and one Storage Account in the relevant resource group

Microsoft Power Automate scheduled flow using a custom API connector

Vercel-hosted proxy that authenticates with an external CRM

The Power Automate flow is running successfully

Investigation completed:

Azure Service Health shows zero impacted resources for the advisory.

Azure Advisor → Reliability shows no recommendation referencing the retiring API version.

Azure Key Vault Activity Log shows no management events in the approximately 60-day period examined.

The current Power Automate flow lists Excel Online, a custom API connector and Office 365 Outlook as its connections.

An older version of the integration used the Azure Key Vault GetSecret connector, but the system was redesigned to use credentials stored in the Vercel environment.

I understand that GetSecret is a data-plane operation, whereas the retiring API version concerns the Azure Key Vault management plane.

Questions:

How can I identify the client, service principal, user agent or application responsible for calling 2026-03-01-preview?

Can Azure Resource Graph, Azure Monitor, Activity Log or another free diagnostic method reveal the API version used in historical management requests?

Could Azure Portal, Power Automate or another Microsoft-managed service have generated these requests automatically?

Does the absence of impacted resources and an Advisor recommendation indicate that the preview API is no longer being used?

Is any corrective action required if the use was historical and no longer recurring?

Can Microsoft confirm whether the retirement date is January 15 or January 31, 2027? The published guidance and subscription advisory appear to differ.

I would prefer not to change or remove a working production integration without identifying the actual dependency.

Any guidance on a read-only verification procedure would be appreciated.Title: Azure Key Vault API 2026-03-01-preview retirement — How can I identify the calling application?

I received an Azure Service Health advisory (SH8B-Q4G) indicating that my subscription has used Azure Key Vault management API version 2026-03-01-preview, which is scheduled for retirement on January 31, 2027.

I'm trying to identify exactly which application, service or integration made these API requests before changing anything in production.

Environment:

Azure subscription with Basic support

One Azure Key Vault and one Storage Account in the relevant resource group

Microsoft Power Automate scheduled flow using a custom API connector

Vercel-hosted proxy that authenticates with an external CRM

The Power Automate flow is running successfully

Investigation completed:

Azure Service Health shows zero impacted resources for the advisory.

Azure Advisor → Reliability shows no recommendation referencing the retiring API version.

Azure Key Vault Activity Log shows no management events in the approximately 60-day period examined.

The current Power Automate flow lists Excel Online, a custom API connector and Office 365 Outlook as its connections.

An older version of the integration used the Azure Key Vault GetSecret connector, but the system was redesigned to use credentials stored in the Vercel environment.

I understand that GetSecret is a data-plane operation, whereas the retiring API version concerns the Azure Key Vault management plane.

Questions:

How can I identify the client, service principal, user agent or application responsible for calling 2026-03-01-preview?

Can Azure Resource Graph, Azure Monitor, Activity Log or another free diagnostic method reveal the API version used in historical management requests?

Could Azure Portal, Power Automate or another Microsoft-managed service have generated these requests automatically?

Does the absence of impacted resources and an Advisor recommendation indicate that the preview API is no longer being used?

Is any corrective action required if the use was historical and no longer recurring?

Can Microsoft confirm whether the retirement date is January 15 or January 31, 2027? The published guidance and subscription advisory appear to differ.

I would prefer not to change or remove a working production integration without identifying the actual dependency.

Any guidance on a read-only verification procedure would be appreciated.

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 No comments

3 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Kevin Grenier 0 Reputation points
    2026-11-09T19:12:03.31+00:00

    Thank you for the detailed clarification.

    I would like to establish whether the reported use of Key Vault API version 2026-03-01-preview originated from my application, a Microsoft-managed service, or historical activity that is no longer occurring.

    Could you please escalate the following questions to the appropriate Azure product team?

    What was the last observed request timestamp, and which Key Vault resource ID was involved?

    Can you identify the caller's application ID, user agent, and operation type?

    Was the request generated by a Microsoft-managed service, including the Azure Portal?

    Is this API version still being called, or was the advisory triggered by historical usage?

    Can you confirm whether the retirement deadline is January 15 or January 31, 2027, as the documentation and Service Health advisory SH8B-Q4G appear inconsistent?

    My Power Automate and Vercel integration is operational. I want to avoid unnecessary changes unless there is evidence of an affected dependency.

    Thank you for your assistance.

    Was this answer helpful?

    0 comments No comments

  3. Andriy Bilous 12,676 Reputation points MVP
    2026-11-06T05:07:01.62+00:00

    Hello Kevin Grenier

    You're correct not to modify a working integration without identifying the dependency first.

    The retirement affects Azure Key Vault management-plane requests (management.azure.com), not GetSecret operations. Your previous Power Automate Key Vault connector is therefore not evidence of this particular dependency.

    First, check whether diagnostic logging was already enabled:

    az monitor diagnostic-settings list \
      --resource "<key-vault-resource-id>"
    

    If logs were sent to Log Analytics, try:

    AZKVAuditLogs
    | where OperationVersion == "2026-03-01-preview"
        or RequestUri contains "api-version=2026-03-01-preview"
    | project TimeGenerated, OperationName,
              RequestUri, ClientInfo, Identity,
              CallerIpAddress, CorrelationId
    | order by TimeGenerated desc
    

    Key KeyVault audit logs can contain vault management operations, API versions, and caller identities. However, they are not a guaranteed complete history of ARM requests, and logging cannot recover events that were never collected.

    Azure Activity Log primarily records management write/delete/action operations, not ordinary GET requests.

    Therefore, if the deprecated API was used only to read Key Vault properties, you may see no Activity Log events.

    Additionally:

    • Activity Log retains 90 days by default.
    • Azure Resource Graph can identify affected resources or Advisor recommendations, but not historical HTTP callers.
    • Neither provides a guaranteed historical API-version audit trail.

    I would recommend to check:

    1. Power Automate: Inspect the custom connector's configured host and actions. Does it call management.azure.com or only your Vercel/CRM endpoint?
    2. Vercel: Search the deployed code and dependencies for Microsoft.KeyVault, management.azure.com, and 2026-03-01-preview.
    3. Azure Portal: Portal operations can generate management API calls using versions selected by Microsoft. These cannot be changed directly by your application.

    Zero impacted resources and no Advisor recommendation do not prove that usage has stopped.

    Service Health's impacted-resource reporting covers only a subset of scenarios. Advisor's recommendation for this preview API is based on recent usage within 30 days.

    Since you have Basic support, which does not include one-to-one technical support, I recommend requesting clarification from a Microsoft moderator or product team in this thread.

    Specifically, ask for:

    • The last observed request timestamp and affected Key Vault resource ID.
    • The caller's application ID, user agent, and operation type, if available.
    • Confirmation whether the caller was a Microsoft-managed service.
    • Confirmation of the retirement deadline: January 15, 2027 (Advisor documentation) versus January 31, 2027 (your Service Health advisory SH8B-Q4G).

    Until the date discrepancy is resolved, plan around January 15.

    If the requests were historical and the integration no longer uses this API, no changes to your working Power Automate/Vercel integration are required solely because the advisory remains visible. The outstanding task is to establish the caller and whether usage is recurring.

    Microsoft documentation:

    Was this answer helpful?

    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.