topic Re: Failed to Create Rule When Adding Azure Blob Storage Event Trigger in Microsoft Fabric Pipeline in Pipelines

Failed to Create Rule When Adding Azure Blob Storage Event Trigger in Microsoft Fabric Pipeline

reireirejinjin — Fri, 08 Aug 2025 07:48:22 GMT

Hello,
Referring to the article AI Ready Apps: From RAG to Chat – Interacting with SQL Database in Microsoft Fabric using GraphQL and MCP | Microsoft Fabric Blog | Microsoft Fabric on the Microsoft Fabric Blog,

I tried to add an Azure Blob Storage event from Add Trigger in a Microsoft Fabric pipeline.

However, I get the following error and cannot complete the rule creation:

“Failed to create rule. Please check your network connection, refresh the page, and try again.”

Do you know how to resolve this?

Environment information

・Fabric capacity region: Japan West (Trial)

・Azure Blob Storage region: Japan West

・Azure subscription and resource group region: US East

・Account permissions: Contributor, EventGrid EventSubscription Contributor, and EventGrid Contributor at the subscription level; ・Storage Blob Data Owner and Contributor for the Blob Storage

・No specific network restrictions

Things I have tried

・Deleted existing event subscription from Blob and recreated it (I thought it might be due to duplication, but it didn’t help)

・Enabled “Share data externally” and “Receive data from external sources” in the Fabric tenant settings

After that, when I tried to open the eventstream created by the pipeline, I got the following error:
Failed to create or update event subscription, workspaceId：～

I can see that an event subscription has been created on the Azure blob side.

Re: Failed to Create Rule When Adding Azure Blob Storage Event Trigger in Microsoft Fabric Pipeline

Vinodh247 — Sun, 10 Aug 2025 05:19:30 GMT

From my experience, your biggest blocker is likely region alignment between Fabric capacity, storage account, and resource group. Event Grid validation webhooks tend to fail when they cross regions unnecessarily, and Fabric trial capacity makes this more sensitive.

Here is what I suspect and recommend:

Region Mismatch

Your Fabric capacity is in Japan West
Your Azure Blob Storage is also in Japan West
But your Azure subscription and resource group is in US East

Even though the storage account is in Japan West, having the subscription’s resource group in another region can cause cross-region Event Grid handshake problems, especially for services like Fabric pipelines that require low-latency Event Grid webhook confirmation.

Recommendation:
Create a resource group in Japan West and move or recreate your storage account there. Event Grid works best when Fabric capacity, resource group, and storage account are in the same region.

Fabric Trial Capacity Limitations

Fabric Trial capacity sometimes restricts:

Certain cross-region Event Grid triggers.
Persistent event subscription handshakes (esp. when “secure webhook” verification is needed).

If possible, try on an F64 or higher paid capacity in the same region as the storage account to confirm if it is a trial limitation.

Event Grid Permissions

You already have:

EventGrid Contributor
EventGrid EventSubscription Contributor
Storage Blob Data Owner

However, Fabric’s Event Grid integration also requires that:

The Fabric service principal has Microsoft.EventGrid/eventSubscriptions/* permissions on the storage account.
The subscription-level EventGrid Contributor role is applied directly, not just inherited via groups.

Check Azure > IAM on the Storage Account and make sure these roles are explicitly assigned.

Network / Firewall

Even though you said “no specific network restrictions”, double-check that:

The storage account firewall allows “Allow Azure services on the trusted services list to access this storage account”.
Fabric’s public IPs for Japan West are allowed if you have any custom firewall settings.

Manual Workaround

If the rule creation from Fabric keeps failing:

Manually create the Event Grid subscription in Azure Portal, with destination pointing to a Webhook endpoint you control.
Then connect that endpoint to Fabric’s Eventstream via custom source. This avoids the auto-creation path that Fabric uses, which is where the failure is happening.

Re: Failed to Create Rule When Adding Azure Blob Storage Event Trigger in Microsoft Fabric Pipeline

v-dineshya — Mon, 11 Aug 2025 11:14:24 GMT

Hi @reireirejinjin ,

Thank you for reaching out to the Microsoft Community Forum.

Hi @Vinodh247 , Thank you for your prompt response.

Hi @reireirejinjin , Could you please try the proposed solution shared by @Vinodh247 . Please do let us know if you have any further queries.

Regards,

Dinesh

Re: Failed to Create Rule When Adding Azure Blob Storage Event Trigger in Microsoft Fabric Pipeline

reireirejinjin — Thu, 14 Aug 2025 00:55:27 GMT

Hi @Vinodh247 ,

Thank you for your detailed answer — it was really helpful.

In short, it worked when I created a Fabric capacity (East US, F2) inside a resource group located in East US, instead of using the trial capacity.

On the other hand, when I created a resource group in West Japan, set up a storage account there, and used the trial capacity (West Japan), the error still occurred. I’m not certain about the exact cause, but there may be some limitations with the trial capacity.

Either way, your help made a big difference. Thank you so much!