Synapse Analytics Event Trigger Activation Error

Chavi Gupta 31

Storage event trigger activation fails with following error:
Forbidden. Role based access check failed for resource <storage-account>

Please help.

Accepted answer

KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2020-08-19T01:41:35.13+00:00

Hi @Chavi Gupta ,

Welcome to Microsoft Q&A forum and sorry you are experiencing this.

After verifying with internal team, it is confirmed that this is a known issue with event based triggers in Synapse workspace. The product team is aware of this issue and working on fixing it. Unfortunately I don't have an ETA at the moment but will keep this thread updated once I receive further information from internal sources.

One possible workaround/alternate until the issue is fixed is to use a schedule trigger.

Hope the above info helps. Please do let us know if you have further query.

Thank you for your patience.

----------

Thank you
Please do consider to click on "Accept Answer" and "Upvote" on the post that helps you, as it can be beneficial to other community members.
Please sign in to rate this answer.
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2020-08-20T17:17:26.753+00:00

Hi @Chavi Gupta ,

Following up to see if the above information was helpful. If you have any further query, please let us know.

Thank you
Sign in to comment

4 additional answers

FMSFT 16 Reputation points Microsoft Employee

2021-01-29T01:15:15.89+00:00
Please sign in to rate this answer.

3 people found this answer helpful.
juanf.perezr 1 Reputation point

2021-05-07T13:26:40.247+00:00

did it work for anyone?

Bennett, Alexander 1 Reputation point

2021-06-08T15:24:28.833+00:00

This response successfully created the event subscription, and the subscription is correctly identifying the storage events. However, the associated event-based trigger in Synapse is still not firing.

Daniel Brum 121 Reputation points

2021-08-26T20:26:11.493+00:00

Took me several hours, but I somehow got it to work, hehe.

Raffaele Brivio 101 Reputation points

2021-10-27T09:10:38.153+00:00

This is the right answer. Thanks.

Matt Protopapas 1 Reputation point

2022-01-07T19:24:05.473+00:00

yes, the Data Factory resource provided was not registered in my subscription, although I had a Synapse workspace. After registering it, the error stopped appearing when publishing the (activated) trigger.
Sign in to comment
Chavi Gupta 31 Reputation points

2020-08-20T23:31:10.793+00:00

Since I needed event based triggers I moved my pipeline to data factory instead. It is working fine there.
Please sign in to rate this answer.
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2020-09-14T18:26:52.083+00:00

Hi @Chavi Gupta ,

Just heard back from internal team about the mitigation/workaround for this issue. Following is temporary mitigation until a permanent fix is applied, please follow below steps to activate event trigger in Synapse workspace.

Append the feature flag(given below) to the Synapse Studio URL. This will enable the blocked feature. &feature.openSubscribeAndProgressAPIs=true

Refresh the page

Disable the trigger and publish the change.

Enable the trigger and publish the change.

Please let us know how it goes.

Thank you

PARAS PAREKH 1 Reputation point Microsoft Employee

2020-09-15T00:08:59.677+00:00

Still doesn't work. Getting the error below.

System.NullReferenceException : Object reference not set to an instance of an object. at Microsoft.Analytics.Common.PartnerApi.DataFactoryResourceProviderClientBase.CreateActionRequest(HttpMethod requestMethod, String subscriptionId, String resourceGroup, String workspaceName, Nullable1 resourceType, String resourceName, String resourcePathPrefix, String action, IEnumerable1 queryParameters, Tuple`2 requestBody) in S:\src\common\Microsoft.Analytics.Common\PartnerApi\DataFactoryResourceProviderClientBase.cs:line 118 at Microsoft.Analytics.Common.PartnerApi.UserAuthBasedDataFactoryResourceProviderClient.<Microsoft-Analytics-Common-PartnerApi-IUserAuthBasedDataFactoryResourceProviderClient-StartTrigger>d__4.MoveNext() in S:\src\common\Microsoft.Analytics.Common\PartnerApi\UserAuthBasedDataFactoryResourceProviderClient.cs:line 127

!Lise Parker (Sword Group) 76 Reputation points

2020-09-29T21:40:21.827+00:00

Hi
I am having the same issue so I added the &feature.openSubscribeAndProgressAPIs=true but I still get the same error when publishing:

Failed to subscribe to storage events for event trigger:...
Trigger activation failed for ....

Both have the same details: Forbidden. Role based access check failed for resource /subscriptions/e.../resourceGroups/.../providers/Microsoft.Storage/storageAccounts/...

Data Factory is working fine but I have everything in Synapse. Any other suggestions please?

KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2020-10-01T19:57:12.367+00:00

Hi @!Lise Parker (Sword Group) , anonymous user,

Sorry for your experience with this issue. I tried this again and noticed an issue and reached out to Product team. I have received a confirmation that there was another issue identified related to event triggers in Synapse. Because of which we are seeing this error message. Product team is actively working on fixing this. At the moment I do not have an ETA but will keep this thread posted as soon as I have the next update.

Until the fix is applied, it is recommended to use schedule trigger or ADF (GA'd product) based on the requirement.

Also please note that Azure Synapse workspace is still in Public preview, and Synapse product team is acknowledging these feedbacks and actively prioritizing them accordingly to provide the best experience.

We appreciate your patience and sincere apologies for the inconvenience caused because of this issue.
Sign in to comment
Alessandro 87 Reputation points

2022-05-19T07:05:15.17+00:00

Register resource providers Data Factory and Event Grid (Subscription -> Resource providers -> Microsoft.DataFactory / Microsoft.EventGrid) worked for me.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Mritunjay Daiya 20 Reputation points

2023-09-05T12:06:17.4833333+00:00

If you are still facing the same issue you can use the Azure CLI to resolve this issue and run the command given below:

az role assignment create --assignee <object-id> --role Contributor --scope /subscriptions/<subscription-id>

Now, you are good to go.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment