Forum Discussion
Error with externally shared semantic models and "Analysis Services Database" connector
Many companies within our holding company structure work with externally shared semantic models deployed in the MS Power BI capacity (F64) of our parent company (which is not their own MS tenant). Those external users access the semantic models as guest users with read and build rights. Since we previously used an Azure Analysis Service Cube instead of a semantic model for external use, many users continue to use the "Analysis Service Database" connection type in Power BI Desktop to connect to the semantic models. Therein, the Power-BI Connection String of the workspace is specified, i.e. “powerbi://api.powerbi.com/v1.0/{tenant-id}/{WorkspaceName}". Not only has that approach enabled an easy migration from AAS to Semantic Models (with external sharing), but also there’s the advantage that external users can connect live to the data.
This has worked very well until last week. Ever since then, there have been errors when choosing the “Analysis Service Database” Connector as an external tenant. We also tested what happens when an internal user tries the same connection: Same error (see below screenshot). When an internal user changes the connection string to “powerbi://api.powerbi.com/v1.0/myorg/{WorkspaceName}", it works like a charm.
With the help of Claude, we figured out that the problem are Cached Credentials / Token Conflicts. Clearing all cached accounts (i.e. delete global connection settings) has thus solved the issue. This is only a temporary fix, however, as users now have to repeatedly clear and reestablish all connections, as the error occurs every time a PBI Desktop file is opened.
Does anyone know, why this suddenly does not work anymore and how to permanently solve the issue?
I just wanted to give an update on this issue: It has meanwhile been listed as known issue on the fabric website:
The Microsoft Support has released an updated build of PBI Desktop, which should resolve the issue when installed. We'll further test if that's the case, but I'll close this topic for now.
4 Replies
Hello,
I’m not completely sure, but this really looks like a recent change in how external access + tokens are handled rather than something wrong on your side, especially since internal users still work fine with the same patternthe cached credentials / token conflict explanation makes sense, I’ve seen similar behavior when Microsoft updates auth flows, one thing you could try is switching users to a different connection method (like direct Power BI dataset connector instead of the AS endpoint) just to see if it avoids the issue
otherwise it might be worth testing with a fresh Windows profile or clean Power BI install to confirm it’s not local caching only, but if it keeps happening consistently then it’s likely a platform-side regression and you may need to wait for a fix or raise a ticket
Best regards,
DanieleHi DanieleUgoCopp ,
thanks for your reply!
We have tested the fresh Windows profile and PBI installation, unfortunately that did not resolve the issue.
The connection method PBI dataset connector does work, but can only be connected as DirectQuery - we'd like to continue using Live-Connection-Mode.
I'll wait if someone has another idea, if not, we'll probably raise a ticket.
BR,
Kathrin
Hi KaySunset,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to DanieleUgoCopp for his inputs on this thread.
This behaviour looks like a recent change in how Power BI Desktop handles authentication tokens for cross-tenant connections rather than a local configuration issue. When using the Analysis Services connector with an explicit tenant ID in the connection string, Power BI is likely caching conflicting tokens, which leads to the timeout error. Clearing global permissions works temporarily because it resets those tokens, but the same conflict gets recreated when the file is reopened.
A more stable workaround is to switch the connection string to powerbi://api.powerbi.com/v1.0/myorg/{WorkspaceName} and make sure users are signed into the correct tenant context with only one active account in Power BI Desktop (also clear any old global permissions once). This helps avoid token conflicts while still allowing you to continue using Live connection mode.
Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.
I just wanted to give an update on this issue: It has meanwhile been listed as known issue on the fabric website:
The Microsoft Support has released an updated build of PBI Desktop, which should resolve the issue when installed. We'll further test if that's the case, but I'll close this topic for now.
