An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.
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:
- Power Automate: Inspect the custom connector's configured host and actions. Does it call
management.azure.comor only your Vercel/CRM endpoint? - Vercel: Search the deployed code and dependencies for
Microsoft.KeyVault,management.azure.com, and2026-03-01-preview. - 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: