Forum Discussion
kusto cross cluster join not work on Service
Hi Anonymous,
Thank you Shahid12523 again for your points.
In Power BI Service, running a cross-cluster query requires the engine to resolve the schema of the remote cluster as well. For OAuth authentication to work in this scenario, several conditions need to be met:
cross-cluster queries must be enabled at the Kusto level to establish trust between the primary and secondary clusters, and your OAuth identity (user or service principal) must have permissions on both clusters, typically at least the Database Viewer role. Additionally, if you’re using a service principal or managed identity for refresh, it must also be granted access to the remote cluster.
The reason it works in Desktop but fails in Service is because Desktop uses your local session token, but Service requires explicit permissions and cross-cluster trust. Once your admin enables cross-cluster querying and grants your OAuth identity access on the second cluster, the refresh should succeed.
Thank you.
Community ChampionPower BI Desktop supports Kusto cross-cluster joins using your local credentials. But in Power BI Service, the refresh fails because the service can't resolve remote entities—likely due to missing permissions or trust between clusters. You’ll need to:
- Use a service principal or managed identity with access to both clusters
- Ensure cross-cluster queries are allowed and remote schema resolution is enabled
- Grant proper viewer permissions on the remote cluster