Forum Discussion
Shared Semantic Model - Connectivity Issue from different tenants
- 7 months ago
Power BI Desktop cannot:
carry over Databricks credentials,
rebind DirectQuery connections across tenants,
or safely republish that dataset binding.
So Desktop opens the report, but when they publish, the semantic model connection is dropped → “data disconnected”. This is expected behavior.
So you have a few limited options here which none of them would be a perfect solution as there is no any in your case.
Option 1: They publish reports, not datasets
You own and publish the semantic model (DirectQuery to Databricks).
Customers get Build permission on the semantic model.
Customers create reports:
in Power BI Service (web authoring), or
in Desktop using Live connection, then publish reports only.
They do not publish datasets.
This is the standard multi-tenant pattern.
Option 2: Customer-owned semantic models
If customers must publish datasets:
Each customer must have:
their own Databricks connection,
their own semantic model in their tenant,
their own credentials.
You cannot safely share a DirectQuery dataset across tenants and let others republish it.
- 7 months ago
Hi Scheneyder , Thank you for reaching out to the Microsoft Community Forum.
There is no remaining configuration or permission change that will make this work. If customers must publish from Desktop, they must own their Databricks connection and semantic model. If they cannot, then Desktop authoring is off the table and authoring must stay in the Service. Currently, Power BI does not support a middle ground for this scenario.
Hi Scheneyder , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
- Scheneyder7 months agoHelper I
Im still having trouble, I was trying to do live connection but when customer download the file with live connection thats the message they got:
We Encountered an error while trying to connect.
Details: "Looks like we're enable to access the semantic model.
Please contact the owner of the semantic model."