Operation on the event subscription failed as Azure Function destination type supports EventGridSchema only

Aliaksei Krylou3 1 Reputation point
2022-08-23T12:40:22.053+00:00

Hi Everyone,

We've created an Event Grid Topic that uses CloudEventSchemaV1_0 as an inputSchema. Then we've been able to create an Event Grid Subscription with 'AzureFunction' endpointType and 'CloudEventSchemaV1_0' as eventDeliverySchema via Azure CLI below:

az eventgrid event-subscription create --name test-subscription \--source-resource-id {event grid topic id}
--endpoint '{function app id}/functions/{function name}' \--endpoint-type azurefunction
--enable-advanced-filtering-on-arrays true

Then when we've tried to update it using the following Azure CLI command:
az eventgrid event-subscription update --name test-subscription \--source-resource-id {event grid topic id}
--endpoint '{function app id}/functions/{function name}' \--endpoint-type azurefunction
--enable-advanced-filtering-on-arrays true `
--max-delivery-attempts 30

We're getting the following error:
(InvalidRequest) Operation on the event subscription test-subscription failed as Azure Function destination type supports EventGridSchema only.
Code: InvalidRequest
Message: Operation on the event subscription test-subscription failed as Azure Function destination type supports EventGridSchema only.

The same behavior is when we're running the same Bicep template two times, getting the same error.

Can you please advise why it's complaining about schema as we're not trying to change it? Also please let us know if this is a known issue and if there is any workaround.

Thanks in advance.

Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
322 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. JananiRamesh-MSFT 22,121 Reputation points
    2022-09-11T11:28:43.477+00:00

    Hi @Aliaksei Krylou3 , Apologies for the delay in response this was an ongoing issue and fix is deployed to few regions "Canada central" "West central US". Our deployment to rest of the regions is going per SDP principles. We hope to have the fix available in all regions by next week.

    please try and again and let me know incase if you face any further issues.

    We really appreciate your patience on this topic.

    Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.