Forum Discussion
Dataverse Fabric Link – No Workspaces Visible with Manually Created Workspace (F2 Capacity)
Hi all,
We have a Dataverse environment in West Europe, and a Microsoft Fabric capacity (F2) also in West Europe.
I previously tested the Fabric Link feature using a trial Fabric capacity in North Europe, and everything worked fine. Now I’ve removed the trial and created a manual workspace in my own Fabric capacity (F2, West Europe), but I’m running into issues:
- When I try to link Dataverse to Fabric via the “Analyze” option in Power Apps, no workspaces are visible.
- I am unable to create a new workspace from the Dataverse interface.
- The user has admin rights on both the workspace and the capacity.
I also tested this with a capacity in North Europe, but the result is the same.
It seems like something is blocking the visibility or linking of manually created workspaces. Some sources suggest that a higher SKU like F64 might be required, but I couldn’t find any official documentation confirming this. According to Microsoft’s documentation, F2 should be supported.
Questions:
- Are there specific requirements or limitations when linking Dataverse to a manually created Fabric workspace?
- Is there a minimum SKU required for workspace visibility or linking?
- Could tenant settings or permissions be preventing this?
Any help or insights would be greatly appreciated!
Thanks,
Erwin
Update: It's working now!
I’ve resolved the issue — turns out that admin permissions on the Fabric capacity (not just the workspace) are required. Once those were in place, I was able to create and select Fabric workspaces in both North Europe and West Europe, using my Dataverse environment in Europe.
Thanks to everyone who contributed to earlier posts — they helped point me in the right direction!
7 Replies
- suparnababu8
Super User
Can you please check if your newly created workspace is assigned to your F2 Capacity. Check your workspace settings and ake sure you can select you wroksapce should be assigend to fabric capacity / premium cpapcity.
And F2 is enough for Fabric link, no need to go for higher SKU.
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User! Hello suparnababu8
Yess my workspace is visible by the user (role=admin) and the Fabric Capacity is assigned to the workspace:
Tomorrow I will try again 🙂
Kind regards,
Erwin
Hi everyone,
This is a follow-up to my earlier post regarding Fabric F2 capacity workspaces not appearing in the "Link to Fabric" wizard in Dataverse — and unfortunately, the issue still persists.
To recap:
- I have two workspaces assigned to Fabric F2 capacity, one in West Europe and one in North Europe.
- I’m an admin on both workspaces.
- When I use "Link to Fabric" in Dataverse, neither of these workspaces shows up.
- Instead, a new workspace is automatically created on the trial capacity in North Europe, even though I disabled the trial for this user yesterday.
What I’ve already verified:
- Region alignment between Dataverse and Fabric capacity.
- Permissions: System Admin in Dataverse, Admin in Power BI, and Contributor on the capacity.
- Tenant settings: “Users can create Fabric items” is enabled.
- Capacity assignment: Workspaces are correctly linked to the F2 capacity.
Despite all this, the wizard still defaults to the trial capacity and ignores the existing F2 workspaces. I’m wondering if there’s some kind of caching issue, or if the trial capacity is somehow still being prioritized.
Has anyone experienced something similar or found a workaround?
Thanks again for any help or insights!
Best regards,
ErwinIn powerapps\dataverse:
I think this means dataverse is in west-europe. when ik create a workspace here a trail workspace has been created in north-europe. I can change this workspace to my own Fabric capicity (F2) in north-europe. But I want to add the dataverse lakehouse to an existing workspace.
v-echaithraCommunity Support
Hi EngineerErwin ,
Thank you for providing the update.When using the Dataverse Fabric link through the “Analyze” button in Power Apps, it is essential that the Dataverse environment, the Fabric capacity, and the target workspace are all located in the same region.
In your case, since your Dataverse environment is in West Europe and your Fabric F2 capacity is in North Europe, the link wizard is unable to display any workspaces associated with the North Europe. As a result, it automatically defaults to creating a trial workspace in West Europe, which aligns with the region of your Dataverse environment.
This behavior is by design, as Microsoft Fabric requires that the Lakehouse created through the Dataverse Fabric link reside in the same region as the originating Dataverse environment.
To resolve this, the most effective and supported approach is to provision a new Fabric capacity (F2 or higher) in the same region as your Dataverse environment West Europe.Once the new capacity is in place:
Assign your existing or new workspaces to this West Europe Fabric capacity.
The Dataverse > Fabric link wizard will then correctly display these workspaces for linking.
This ensures regional alignment and enables seamless integration between Dataverse and Microsoft Fabric.
I did this already. dataverse (west-europe) - Workspace with Fabric capacity (west-europe). Still not seeing this. Strange thing is that a workspace (created from dataverse) ends in een trail capacity in north-europe. So I tried also with aan workspace in north-Europe. still no luck.
The trail expired for this user. and now I get this error again
I need a premium-license of Power BI (message in Dutch). I tried with a fabric capicity in north and west Europe again. No luck in the first step.. Only with a trail license I get it to work.
Update: It's working now!
I’ve resolved the issue — turns out that admin permissions on the Fabric capacity (not just the workspace) are required. Once those were in place, I was able to create and select Fabric workspaces in both North Europe and West Europe, using my Dataverse environment in Europe.
Thanks to everyone who contributed to earlier posts — they helped point me in the right direction!
