Forum Discussion
Problem with setting up link to Fabric in Dataverse
- 26 days ago
Hi
Regarding regions on Dataverse you can check them here:
These are what they call Macro regions:
https://learn.microsoft.com/en-us/power-platform/admin/macro-regions#macro-region-geography
To find out with more detail which region you need you can try either look at your Dataverse URL for the number and then check against this table:
https://learn.microsoft.com/en-us/power-platform/admin/new-datacenter-regions
There's also this other way I found in the forum seems kind of hacky but it should work as well:
Fabric Dataverse Link - You need Power BI premium license to continue | Microsoft Fabric CommunityRegarding the license of the account that sets up the link, I believe it needs to have at least a PRO license due to the requirement of being an Admin in the workspace.
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 EuropeBy 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 changeIf 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 answerIf 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 resultThat 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.