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

60 Days of Data Days! Live and on-demand sessions, challenges, study groups and more! And it's all FREE!. Join now. 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
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

60 days of Data Days Carousel

Data Days 2026

Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.

Top Solution Authors