Fix Dataverse Link to Fabric Errors: Premium License, Unauthorized Access, Region Mismatch

In this video, I share three issues we ran into when setting up a Microsoft Dataverse link to Fabric, and what actually fixed them. Some of the error messages were misleading and did not point directly to the real problem, so this walkthrough may save you some troubleshooting time. What I cover Validate Configuration error Error message: “Access to Power BI and Fabric capacity” “You need a Power BI premium license to continue” In our case, the fix was not in Power BI or Fabric. The account used to create the link needed System Administrator access to the Dataverse environment. Tables created, but data not accessible Error message: “Unauthorized. Access to target location denied” The tables were created in Fabric, but the data was not accessible. In our setup, the Fabric account was different from the Dataverse admin account. We used a service principal in Fabric, so that account needed read access to the Dataverse tables. Region mismatch Our Fabric capacity was in West Europe, but Dataverse was in the UK. For the Dataverse to Fabric link, they needed to be in the same region. We created a small F2 capacity in the UK specifically for this link. Checklist Before setting up Dataverse link to Fabric, check: • Does the account creating the link have the right Dataverse environment role? • Does the Fabric account or service principal have access to the Dataverse tables? • Are Dataverse and Fabric capacity in the same region? • Are you using the same account everywhere, or different accounts for Dataverse and Fabric? Key takeaway Not every Fabric error is actually a Fabric problem. Sometimes the fix is in Dataverse roles, table permissions, service principal access, or capacity region. #MicrosoftFabric #Dataverse #PowerBI #DataEngineering