Forum Discussion

MithunYadav07's avatar
MithunYadav07
New Member
7 days ago

Microsoft Fabric Pipeline Authentication Error – AADSTS50173

Hi everyone,

I'm encountering an authentication issue while running a pipeline in Microsoft Fabric. The pipeline is failing with the following error:

Error Message:

ArtifactConnection_InaccessibleDatasource AADSTS50173: The provided grant has expired due to it being revoked. A fresh auth token is needed.

Has anyone encountered this issue before? Could you please help me understand the root cause and suggest how to resolve it?

I would also appreciate any recommendations for preventing this issue from recurring in production pipelines.

 

data engineering

3 Replies

  • tayloramy's avatar
    tayloramy
    Icon for Super User rankSuper User
    7 days ago

    Hi MithunYadav07​,

    There's lots of reasons a token can expire, including a password reset, organizational policy in entra, or just the token expiring naturally. 

    To resolve it, you will need to re-auth the connection. 

    To prevent this, don't use user accounts for connections. Use a service principal/workspace identity where supported, and if you must use a user account, have a service account created that is exempt from password change and expiration policies. 

  • v-csrikanth's avatar
    v-csrikanth
    Icon for Community Support rankCommunity Support
    2 days ago

    Hi MithunYadav07​ 

    We would like to inquire whether have you got the chance to check the solutions provided by other users in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

  • ShivekMaharaj's avatar
    ShivekMaharaj
    Icon for Community Champion rankCommunity Champion
    6 days ago

    Hi MithunYadav07​,

    tayloramy​'s answer is the right starting point.

    AADSTS50173 specifically means the Microsoft Entra refresh token behind the connection is no longer valid, so the immediate fix is to reauthenticate the affected Fabric connection.

    Microsoft documents this error as occurring when the refresh token has been revoked or expired, for example after a password change/reset or an administrator revokes the token.

    For production pipelines, I would also check whether the connector supports Fabric workspace identity. Where supported, that is usually preferable to a personal user connection because Fabric manages the identity and there is no user password or refresh token lifecycle to maintain.

    A service principal is another option, but authentication support is connector-specific, so I would verify the exact source/destination connector before redesigning the connection.

    So the pattern I would use is:

    Workspace identity where supported
→ service principal where appropriate and supported
→ dedicated user/service account only where workload identities are not available

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.