Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hello,
we are using external data sharing to have shortcuts cross-tenant. When you create a share, you enter one (and only one!) mail address. Apparently, this mail address must be associated with a Fabric account for the sharing to work. This arrangement seems highly counterproductive for us: First, we would need to create several shares for every team member to have access; second, the shares would then be tied to personal accounts instead of the security group that we have for exactly this kind of situation.
Is there a better way? This current mode of external sharing seems to be not very well designed.
Solved! Go to Solution.
Hello @NotebookEnjoyer you don't get your data to the other tenant, however, with this approach you invite users of other tenant into yours using B2B guest and give them the appropriate access to your data i.e Lakehouse or Warehouse.
Hello @NotebookEnjoyer
For Fabric External Data Sharing (OneLake shortcuts):
This is a known limitation today. External data shares are user‑bound, not group‑bound.
Workaround: Entra B2B guest + Fabric permissions
Change the Fabric tenant settings -
How would I get the data to the other tenant with the workaround approach?
Do you want Shared access to the same data or Independent copy of the data in Tenant B?
These are very different architectures.
I don't want an independent copy; I want the kind of access in tenant B that a shortcut would provide: read it as if it's just another table in the lakehouse.
Hi,
Why not using Azure AD B2B with Security Groups?
Instead of sharing directly to individual emails:
- Invite the external users into your tenant via Azure AD B2B.
- Add those users to a security group.
- Grant Fabric workspace or item access to that security group.
This way you manage access centrally and no need to create multiple shares per person.
This is the most scalable pattern.
Best
Onur
😊 If this post helped you, feel free to give it some Kudos! 👍
✅ And if it answered your question, please mark it as the accepted solution.
How would I get the data to the other tenant with this approach?
Hello @NotebookEnjoyer you don't get your data to the other tenant, however, with this approach you invite users of other tenant into yours using B2B guest and give them the appropriate access to your data i.e Lakehouse or Warehouse.
Hi @NotebookEnjoyer
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.
Hi @NotebookEnjoyer
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 27 | |
| 13 | |
| 9 | |
| 8 | |
| 5 |