scheduled refresh corrupts user credentials and makes it stop refresh

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.