AAS based PBI failed in refresh & token expiration.

[weizou]

Hi ,

We have a PBI report originally sourcing from Kusto import mode, later rebuilt with AAS live connection.

It has been running successfuly in AAS connection for ~2 months.

Today, it failed loading as following, something related to token expiration (which should not be applicable for live connection).
The report works again after we republish the pbix without change.

Any idea why this happened, and how to monitor/prevent?
Thanks!

Underlying error message: AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-02-24T18:22:17.1619532Z and was inactive for 90.00:00:00. Trace ID: 45134bd8-462b-47c8-a67d-9cba9e671600 Correlation ID: 32735da4-4e51-4e4a-b58b-f7a2ebf43f24 Timestamp: 2025-07-11 16:01:49Z

Activity ID: 1dfdde67-752b-4f25-bd4f-9c7008d187ce

Correlation ID: d1c125cb-d077-8eba-f57d-d4b5220961a4

Request ID: 3a8cf93e-bacd-2015-16dd-3a59bd383c04

Time: Fri Jul 11 2025 09:01:49 GMT-0700 (Pacific Daylight Time)

Service version: 13.0.26321.25

Client version: 2507.2.24997-train

Cluster URI: https://df-msit-scus-redirect.analysis.windows.net/

[weizou]

@FBergamaschi ,

Thanks for help.

One more followup knowledge question.  Is it correct understanding that :
Even report is inactive, it should still work properly for any users. Because semantic model is based on AAS, and refresh on AAS side. User should not receive any token refresh issue (which is applicable for Kusto datasource only).

[weizou]

Thank you !

Republish did solve the issue.

Could I understand it as : the token issue should NOT come back on AAS based semantic model ?

FBergamaschi, could you please share a little more here? what "record" does this refer to?
" if nobody opens and interacts with the report it might be they record is as inactive"

Thanks
Wei

& priyankata.

[FBergamaschi · Accepted solution]

What I mean is that after some days without anybody opening it, a report is classified as inactive

If this helped, please consider giving kudos and mark as a solution

@me in replies or I'll lose your thread

consider voting this Power BI idea

Francesco Bergamaschi

MBA, M.Eng, M.Econ, Professor of BI

[v-priyankata]

Hi @weizou 

Thank you for reaching out to the Microsoft Fabric Forum Community. @FBergamaschi Thanks for the inputs.

Everything he mentioned was correct, the issue was caused by the token expiring after 90 days of inactivity even live connections can run into this if the token isn’t refreshed in time.

Please republish, it will fix it because it triggers a fresh token, which restores the connection. 

If you are still experiencing this issue after trying the above steps, please reach out here for further assistance.
Thanks.

[FBergamaschi]

Are yo usure the report was open by someone in the meantime? if nobody opens and interacts with the report it might be they record is as inactive