Forum Discussion
Post PatronDataverse Direct Link to Fabric
Dears,
We would like to decommission our Dataverse synapse link and start working with : Dataverse Direct Link to Fabric
I was reading and seems to me that we cannot have more than one link per dataverse environment .
For example, seems we cannot create one link from our production dataverse application tables (called agora) to link it to fabric workspace in Prod and then, create another link of the same tables in the same dataverse environment to connect it to our Dev Fabric worskpace.
Is this correct? We can only have one link?
I ask this because it means (in case this technical restriction exists) that we will not be able to connect Dataverse environment to Fabric Dev WS, Fabric UAT WS and Fabric Prod WS as we do for other apps according to our change management process
Instead, probably, we will need to create only one Fabric WS (connected to Dataverse production) and then, maybe, use onelake shortcuts to connect our Fabric Dev WS , Fabric Dev WS UAT and Fabric Dev WS Prod in their respective RAW zones
Can you please clarify if there is this technical constraint?
Thanks,
Pedro
Thank you for reaching out to the Microsoft Fabric Forum Community.
suparnababu8 svenchio Thanks for the inputs. The information shared by users has been very helpful, as have their suggestions. I’d like to add a small point as well.
It’s not mandatory to create a separate dedicated ingestion workspace. Given the one-link limitation in Microsoft Dataverse, you can simply:
Connect Dataverse Prod -> RAW Prod workspace
Use Microsoft OneLake shortcuts to RAW UAT and RAW Dev
Later, when Dataverse UAT/Dev exist, link each to its matching RAW workspace
Create a Dataverse shortcut - Microsoft Fabric | Microsoft LearnIf there are any deviations from your expectation please let us know we are happy to address.
Thanks.
8 Replies
- suparnababu8
Super User
Yes, your approch is correct. Dataverse environment can have only once active link, either synapse link or Direct link to Fabric at a time. It means that you can not create muliple direct links from the same Dataverse environement to different workspaces.
Finally, I would recoomend you, to support your DEV, UAT and PD seperation, you can use One Lake shortcuts mechnaisam to replicate the data into multiple wortkspaces.
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! - svenchio
Hey fabricpribeiro not sure the reson behind it, but I think is a smart choice 👉 "to decommission our Dataverse synapse link and start [...] Dataverse Direct Link to Fabric" 😉
What you read is correct and I can confirm by trying that you 👉 "... cannot have more than one link per dataverse environment ." had the same question and confirmed by experimentaiton, I was so confused betwwen Synpase vs Fabric link that I tried, and no, you can't ... it is a one-to-one relation.
So, yes, recommended architecture as of today with Fabric Link is
#1. Dataverse Prod (Direct Link – ONE TIME) ↓
#2. Fabric Workspace: Dataverse-Source (RAW) ↓
#3. OneLake Shortcuts ↓
#4.Dev Fabric Workspace
#4.UAT Fabric Workspace
#4.Prod Fabric WorkspaceSo, there it goes, i think you were on the right track all along 😁 and you can now move forward with a bit more confidence 😅 nonethelss, I would suggest you to handle this with some caution, I know there's some private preview of Dataverse Mirror in Fabric 🤫 ... so, perhaps in the no so distant future there's an evolution on this topic and it would me advise to keep your stakeholder understand this is a very dynamic environment and fabric is evaolving fast and constantly, so, you don't have to deal with "but we just move from synapse to fabric link, and now this?" 😋 (just a friendly piece of advise)
All the best mate, hope you find this informatino useful, if so, give us a kudos! And mark as a solution if appropiate. Cheers.
fabricpribeiroThank you very much for the anwser. I think my question now is:
I have :
1 - RAW workspace in Production
1 - RAW workspace in UAT
1 - RAW workspace in Development
I guess , because we are doing the link from dataverse Prod, we can connect it to our RAW workspace PROD and then create links from the other workspaces. This way,in the future, if other data verse environments get available, for example dataverse UAT, we can connect our UAT with their UAT.
Or would you create a completely separade WS for this? and then the shortcuts from the 3?
I am trying to avoid having completed separated because I cerated the RAW zone in each environment already to support separation between landing and bronze
Thanks in advance for a comment
Best regards,
Pedro
- svenchio
Welcome fabricpribeiro , given the current one-link-per-Dataverse-environment constraint, the cleanest and most future‑proof approach is to create one dedicated Fabric workspace with only the Dataverse ingestion (RAW) and connect the Dataverse Prod environment only to that workspace.
From there, use OneLake shortcuts to expose the RAW data into your Dev, UAT, and Prod Fabric workspaces, this avoids coupling Dataverse Prod directly to multiple environment-RAW zones and keeps your existing RAW layering intact.
Hope this note helps... all the best and good luck with your infra. re-factor! If nothing else, remember to close and accept a solution and kudos if you find this info. useful .
- fabricpribeiro
Sorry, just to be clear, you defend something like:
Dedicated Fabric RAW connect to Dataverse in a separated workspace
Then,
Fabric Prod RAW WS, Fabric TEST RAW WS and Fabric DEV RAW WS , each one with shortcuts to that dedicated workspace in bold.
Is that it?
Thanks,
Pedro
Thank you for reaching out to the Microsoft Fabric Forum Community.
suparnababu8 svenchio Thanks for the inputs. The information shared by users has been very helpful, as have their suggestions. I’d like to add a small point as well.
It’s not mandatory to create a separate dedicated ingestion workspace. Given the one-link limitation in Microsoft Dataverse, you can simply:
Connect Dataverse Prod -> RAW Prod workspace
Use Microsoft OneLake shortcuts to RAW UAT and RAW Dev
Later, when Dataverse UAT/Dev exist, link each to its matching RAW workspace
Create a Dataverse shortcut - Microsoft Fabric | Microsoft LearnIf there are any deviations from your expectation please let us know we are happy to address.
Thanks.
Thank you for reaching out to the Microsoft Fabric Forum Community.
I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.
