scheduled refresh corrupts user credentials and makes it stop refresh

[kadirkkkk]

In my situation there are two tenants, Tenant A and Tenant B

In tenant A there is X user. X user is also a guest user in Tenant B. X user has fabric admin role in Tenant B. 

In tenant B there is a dataflow (gen 1) and a semantic model connected to this dataflow

In semantic model i use the X user credentials to connect dataflow. Of course i connect X user as "Sing in to an organisation" option and enter the Tenant B address.

When i click REFRESH in semantic model, everything works fine. But when i schedule a refresh that refresh gives error as below; 

<ccon>Expression.Error: The key didn't match any rows in the table.. Microsoft.Data.Mashup.ErrorCode = 10061. Key = [workspaceId = "xxxxxxxxxx"]. Table = #table({"workspaceId", "workspaceName", "workspaceType"}, {}). </ccon>;<ccon>The key didn't match any rows in the table.</ccon>. The exception was raised by the IDbCommand interface. Table: DataTableName.

Once the error occurs manual refresh stop working either. 

When i enter the credentials again manuel refresh starts working again. 

Looks like a bug. What do you suggest?

[v-sgandrathi · Accepted solution]

Hi @kadirkkkk,

Thank you for providing detailed information about the issue you're encountering.

Based on the scenario you've described, the root cause of the scheduled refresh failure seems to be related to using a guest user account from Tenant A to access resources in Tenant B. While manual refresh works when initiated through the Power BI interface using the guest session, scheduled refresh operations run in the background and are unable to consistently authenticate guest users across tenants.

This behavior can lead to a token mismatch or loss of access context, resulting in the error: “The key didn't match any rows in the table.”

Once this occurs, it can also invalidate or corrupt the stored credentials, which is why manual refresh stops functioning until the credentials are re-entered.

To ensure stable and consistent refresh behavior, we recommend the following:

Use a native user account created directly within Tenant B, rather than a guest user account.

Assign the appropriate permissions (such as Fabric Admin) to this native account.

Reconfigure the semantic model to use this account for dataflow connections.

Using a native user account ensures that the Power BI service can reliably handle authentication for scheduled refreshes, avoiding the limitations associated with guest accounts in cross-tenant scenarios.

Glad I could assist! If this answer helped resolve your issue, please mark it as Accept as Solution and give us Kudos to guide others facing the same concern.

Thank you being a part of the Microsoft Fabric Community.

[v-sgandrathi]

Hi  @kadirkkkk,

We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.

If my answer resolved your query, please mark it as "Accept Answer" and give Kudos if it was helpful.

If you need any further assistance, feel free to reach out.

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[kadirkkkk]

Yes, what you suggest as using native user account solved refresh issue. But that cost me an extra Power BI pro license 😞

[SaiTejaTalasila]

Hi @kadirkkkk ,

@GilbertQ is correct. Can you share more details?

Data source, authentication you are using etc,..

Thanks,

Sai Teja 

[GilbertQ]

Hi @kadirkkkk 

I would strongly recommend making sure you always use user accounts within the tenant that you want the refresh to happen using guest accounts in another tenant creates endless headaches and a lot of complexity that is very hard to troubleshoot and get working successfully.