Pipeline failed with: BadRequest Error fetching pipeline default identity userToken .. etc etc

[smeetsh]

Hi All,

Last week MS Fabric decided to give a me Monday morning hurdle to jump (Aren't those the best 😂)

One of the 1st things I check every morning is the monitor in fabric, to see if our pipleines worked as intended. To my dismay i saw all  of our pipelines started failing at midnight our time (New Zealand). The error was:

"BadRequest Error fetching pipeline default identity userToken, response content: {
"code": "LSROBOTokenFailure",
"message": "AADSTS700003: Device object was not found in the tenant '6742845e-46ae-4628-bd3c-d15a1c3bbda6' directory. Trace ID: dd85a86e-d1f1-473e-9fe2-6ed45a782e00 Correlation ID: 349f2d7b-68ed-4507-9728-0fb4e0981b83 Timestamp: 2025-06-30 04:30:07Z The returned error contains a claims challenge. For additional info on how to handle claims related to multifactor authentication, Conditional Access, and incremental consent, see https://aka.ms/msal-conditional-access-claims. If you are using the On-Behalf-Of flow, see https://aka.ms/msal-conditional-access-claims-obo for details.",
"target": "PipelineDefaultIdentity-e9412e12-96d5-4738-8cf1-89a1e037ac84",
"details": null,
"error": null
}. FetchUserTokenForPipelineAsync"

After some frantic searching the solution was very simple, just make a change, like add a dot to a description of a activity, or the description of the pipeline, and just simply save the pipeline. This refreshes the token and brought every thing back online.

Does anyone have any idea what could have caused this autentication token to suddenly disappear?

The problem is resolved , but I would hope to find out what caused it

(and at least it is now documented here for others to fine)
Cheers

Hans 

[Rufyda]

Hi
Glad that your query got resolved. Please continue using Fabric Community for any help regarding your queries.

[smeetsh]

@v-karpurapud  Thank you for the response, we had indeed made changes to conditional access. So I am thinking that was the cause of it.

[v-karpurapud · Accepted solution]

Hi @smeetsh 

Thank you for contacting the Microsoft Fabric Community Forum.
 
The pipeline failure, identified by the error message indicating a  BadRequest and LSROBOTokenFailure, was due to an authentication token issue with the pipeline’s default managed identity in Microsoft Fabric. The Azure Active Directory (AAD) error “AADSTS700003: Device object was not found in the tenant” shows that the identity object was no longer recognized by AAD. This can happen if the token has expired, become stale, or was invalidated by service updates, metadata changes, or Conditional Access policy updates. Backend changes in Microsoft Fabric can also impact token validation. In this instance, making a small change to the pipeline, such as updating its description, refreshed the pipeline metadata and prompted Fabric to request a new valid token from AAD, resolving the issue. To avoid similar issues, regularly check managed identities in Azure AD, review Conditional Access policy changes, and keep up with platform updates that may affect authentication in Microsoft Fabric.

 

Regards,

Karpurapu D,

Microsoft Fabric Community Support Team.