Power Platform Community Forum Thread Details

Hi all,

Hoping someone else has experienced the same and is able to help out. We've started looking at migrating away from the old webhooks that are being deprecated and in to the Workflows replacement. One of the things we set up back at the start of October was using Azure Key Vault events alerting to alert about events as below:

This was set up and working fine, the events sent a JSON payload that got parsed in the Workflow after being posted to the Teams webhook and then successfully posted in specific Teams Channels:

This was all working great until some time recently when we went back and found that this functionality just no longer works and the Key Vault events metrics show all delivery attempts as failures. Once we'd enabled diagnostic logging for the delivery failures all that it really gives is that it was a bad request:

{ "time": "2024-11-22T09:52:15.9868768Z", 
"resourceId": "/SUBSCRIPTIONS/PLACEHOLD_SUB_ID/RESOURCEGROUPS/PLACERHOLDER_NAME/PROVIDERS/MICROSOFT.EVENTGRID/SYSTEMTOPICS/TEST-EVENTGRID-TOPIC", 
"eventSubscriptionName": "PLACEHOLDER_NAME", 
"category": "DeliveryFailures", 
"operationName": "Deliver", 
"message": 
  "outcome=BadRequest, 
  latencyInMs=170, id=PLACEHOLDER_ID, 
  outputEventSystemId=PLACEHOLDER_ID, 
  state=Filtered, 
  deliveryTime=11/22/2024 9:52:15 AM, 
  deliveryCount=0, 
  probationCount=0, 
  deliverySchema=EventGridEvent, 
  trackedSystemTopicState=CreatedExplicitlyByUser, 
  eventSubscriptionDeliverySchema=EventGridEvent, 
  outputEventFields=InputEvent| EventSubscriptionId| DeliveryTime| State| Id| LastHttpStatusCode| DeliverySchema| LastDeliveryAttemptTime| SystemId| UseMappedResourceArmIdForBilling| TrackedSystemTopicState, 
  outputEventFieldCount=, 
  dedicatedQueueDeliveryQueueId=, 
  requestExpiration=1/1/0001 12:00:00 AM, 
  delivered=False id=PLACEHOLDER_ID, 
  inputEventSystemId=PLACEHOLDER_ID 
  publishTime=11/22/2024 9:52:15 AM, 
  eventTime=11/22/2024 9:52:15 AM, 
  eventType=Microsoft.KeyVault.SecretNewVersionCreated, 
  deliveryTime=11/22/2024 9:52:15 AM, 
  filteringState=FilteredWithRpc, 
  inputSchema=EventGridEvent, 
  publisher=MICROSOFT-KEYVAULT-VAULTS.UKSOUTH-1.EVENTGRID.AZURE.NET, 
  size=662, 
  subject=PLACEHOLDER_NAME, 
  inputEventFields=Id| PublishTime| SerializedBody| EventType| Topic| Subject| FilteringHashCode| SystemId| Publisher| FilteringTopic| TopicCategory| DataVersion| MetadataVersion| InputSchema| EventTime| FilteringPolicy, 
  inputEventFieldCount=16, 
  type=HttpPost, 
  subType=LogicApps, 
  supportsBatching=False, 
  aadIntegration=False, 
  managedIdentityType=None, 
  urlPath=PLACEHOLDER_URL, 
  deliveryResponse=BadRequest, 
  errorCode=BadRequest, 
  HttpRequestMessage: httpVersion=1.1, 
  HttpResponseMessage: HttpVersion=1.1, 
  StatusCode=BadRequest(BadRequest), 
  StatusDescription=Bad Request, 
  IsRedirected=False, 
  RedirectUrl=, "}

I can point the Key Vault at another non-Microsoft webhook and it will successfully post the payload with no issue. I can also take the payload and post it to the above webhook myself and it will work fine, which leads mean to think it's either something in the way Azure posts these events has changed and the new Teams Workflow webhook doesn't like it, or the Teams Workflow webhook has changed in what it's expecting and the Azure events don't have what's required.

If anyone else has experienced and overcome this issue it would be great to know what you did, as this is driving me round the bend. I'm not even sure if this is the right place to post about this problem!

Thanks all.

Categories:

Business Process Flows

New Teams Workflow Based Webhooks Notification Issues

Helpful resources

News and Announcements

Quick Links

November 2024 Newsletter…

Community Update Oct 28…

Tuesday Tip #7 Community Profile Tips…

more Community News

Leaderboard

Featured topics

Product updates