Problem with setting up link to Fabric in Dataverse

Hi Johan_DS​,
Thanks for sharing the details. According to Microsoft documentation, Link to Fabric requires the Dataverse System Administrator role, Power BI workspace administrator permissions, and a qualifying Fabric capacity in the same Azure geography as the Dataverse environment. Please verify the F2 capacity's region and confirm that the target workspace is assigned to it. Also, check the documented Fabric workspace network security requirements.
Troubleshooting common issues with link to Fabric with Microsoft Dataverse - Power Apps | Microsoft Learn
Configure your environment and link to Microsoft Fabric - Power Apps | Microsoft Learn
Frequently asked questions about Microsoft Fabric Link for Dataverse - Power Apps | Microsoft Learn

Thank you.

Hi Johan_DS​,

Have you had a chance to review the solution shared by jubinsoni​ fpvmorais1​ ShivekMaharaj​? If the issue persists, feel free to reply so we can help further.

Thank you.

Hi Johan_DS,

One detail in your screenshots stands out: the two screens disagree about where the environment is.

Link to Fabric wizard   -> AzureRegion.Westeurope
Synapse Link screen     -> North Europe (geography: Europe)
Client capacity (F2)    -> North Europe

By the documented rule (same geography), North Europe and West Europe should both pass. But the failing step is the wizard's own "Access check for Power BI and Fabric capacity", and that check is driven by the region the Fabric wizard resolves, which here is West Europe. Other users have reported the check only passing once the capacity was in that exact region, which would also explain why your own tenant behaves differently.

On your license question: Microsoft's Link to Fabric troubleshooting guidance says you need a Power BI Premium or Fabric capacity, and that Premium Per User is not sufficient. The check is about capacity access, not a personal Pro license, which matches your colleague setting it up without one.

Before asking the client to buy anything, I would rule out the permission side:

F2 is running, not paused, in the Azure portal
-> you are capacity admin or have contributor
   permissions on the F2 (Admin portal > Capacity settings)
-> the target workspace is assigned to the F2
-> you are Admin on that workspace
-> retry in a fresh browser session after any change

If all of that is in place and it still fails, the cheapest way to prove the region theory is a short-lived test, since F2 is billed per second and can be paused:

create a temporary F2 in West Europe
-> assign a test workspace to it
-> run Link to Fabric again
-> pause or delete the F2 once you have the answer

If that works, you have a clear basis for the recommendation: either keep the link on a West Europe capacity, or ask Microsoft support why the wizard resolves the environment to West Europe while Power Platform reports North Europe.

So my overall approach would be:

rule out capacity state and permissions
-> test with a capacity in the region the wizard reports
-> decide on capacity placement from that result

That way you can give the client a tested answer instead of a guess.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi Johan_DS​,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.