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.