Forum Discussion

ShaunLeMouton's avatar
ShaunLeMouton
Icon for Helper I rankHelper I
6 months ago
Solved

FABRIC and DataVerse : Create de Fabric Link

Hi,   I would like to create a link between my dataverse table on my environement to a Fabric WorkSpace. I have checked my rigth in Fabric (i 'm full administrator , i can create workspace, Onelak...
General Comment
  • ShaunLeMouton's avatar
    ShaunLeMouton
    5 months ago

    Hi

     

    The MicroSoft Support just sent me a response to my ticket. (after a long moment)

    They said in the ticket :

    they have successfully removed the CDS2 folder manually. You may now kindly proceed with retrying the Fabric link creation at your convenience.

     

    I Suppose that old meta date was not deleted then i dropped the link the first time to recreate it.

     

    if it can help some one.

     

Zanqueta's avatar
Zanqueta
Icon for Super User rankSuper User
6 months ago

Hi  ShaunLeMouton

Based on similar cases and Microsoft’s current implementation of the Dataverse–Fabric link, the issue is typically not related to user permissions but instead to one of the following:
 
1. Workspace Creation Policies or Governance Restrictions

Even if your user has administrative rights, the tenant‑level Fabric governance settings or Power Platform environment policies may block automatic creation of:

new Fabric workspaces

associated OneLake lakehouses

This can occur when:

  • Fabric capacity is restricted to specific security groups

  • Workspace creation is limited by tenant policy

Power Platform environment does not allow Fabric integration

These restrictions often generate the behaviour you are describing: a long delay followed by a generic error identifier.

 

2. Capacity Availability or Region Misalignment
 
A Dataverse–Fabric link requires:
  • a Fabric-enabled workspace

a lakehouse created in the same region as the Dataverse environment

If your Dataverse environment resides in a region where Fabric is not enabled, the link creation fails at step 2.
This is a common cause of errors that produce only an opaque activity ID.
 
3. Missing Fabric Resource Providers
 
In some tenants, especially new ones, the Microsoft Fabric resource providers in Azure are not fully registered.
If the Fabric workspace cannot be provisioned programmatically, the Dataverse wizard fails before the lakehouse is created.
 
4. Known Product Limitation / Service Issue
 
There have been several documented cases where creating a lakehouse automatically from the Dataverse wizard fails due to a transient backend issue.
Submitting the error ID to Microsoft Support is the correct step.
 
Your support ticket with the error ID is the correct escalation path.
In the meantime, check this resolved ticket in order to get more context
 
 
ShaunLeMouton's avatar
ShaunLeMouton
Icon for Helper I rankHelper I
6 months ago

Hi,

 

I tried to  link Dataverses Tables on other environment (PREPROD / PROD) , to Fabric.

It's work fine ... but not with my DEv dataverse environnment ..