Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric certified for FREE! Don't miss your chance! Learn more

Reply
TePe
Helper IV
Helper IV

Defining Event Grid as a source - Namespace doesn't appear

Hi,

I want to define Event Grid as a source for my Eventstream to consume MQTT events (the MQTT connector doesn't work for me). However, after selecting my subscription the Event Grid Namespace list is empty. I recreated the Event Grid Namespace, I checked the settings in the Fabric Tenant Admin, I enabled MQTT and Routing, I'm not sure what I missed. Any idea?

Thanks,

 

Thomas

1 ACCEPTED SOLUTION
TePe
Helper IV
Helper IV

Solved... It's missing in the documentation that some permissions are also required:

RBAC: you need Reader (or higher) on the subscription/RG + a Workspace‑level assignment for the Namespace service principal

There are two permission tracks involved:

  • Enumeration path (your identity): Fabric uses your Azure ARM permissions to list Namespaces. Make sure your Entra/Azure role on the subscription and resource group containing the Namespace is Reader or above. Without this, the list will be empty even though the resource exists. Azure’s troubleshooting docs point to RBAC/visibility permissions as typical blockers. [learn.microsoft.com]

  • Ingestion path (service principal of the Namespace): Per Fabric docs, in the Fabric workspace you must Add the Event Grid Namespace’s service principal and grant Contributor (this is not about listing, but it’s required to successfully add/ingest afterward). Steps are in the Learn article under “Prerequisites.” [learn.microsoft.com]

In Fabric: Workspace → Manage access → Add people or groups → enter the Event Grid Namespace name → select the matching service principal → assign Contributor. [learn.microsoft.com]

THANKS to CoPilot 🙂

View solution in original post

1 REPLY 1
TePe
Helper IV
Helper IV

Solved... It's missing in the documentation that some permissions are also required:

RBAC: you need Reader (or higher) on the subscription/RG + a Workspace‑level assignment for the Namespace service principal

There are two permission tracks involved:

  • Enumeration path (your identity): Fabric uses your Azure ARM permissions to list Namespaces. Make sure your Entra/Azure role on the subscription and resource group containing the Namespace is Reader or above. Without this, the list will be empty even though the resource exists. Azure’s troubleshooting docs point to RBAC/visibility permissions as typical blockers. [learn.microsoft.com]

  • Ingestion path (service principal of the Namespace): Per Fabric docs, in the Fabric workspace you must Add the Event Grid Namespace’s service principal and grant Contributor (this is not about listing, but it’s required to successfully add/ingest afterward). Steps are in the Learn article under “Prerequisites.” [learn.microsoft.com]

In Fabric: Workspace → Manage access → Add people or groups → enter the Event Grid Namespace name → select the matching service principal → assign Contributor. [learn.microsoft.com]

THANKS to CoPilot 🙂

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

February Fabric Update Carousel

Fabric Monthly Update - February 2026

Check out the February 2026 Fabric update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors