Forum Discussion

Mpmp1's avatar
Mpmp1
New Member
17 days ago
Solved

Copyjob issue

I had a consultant who has create a fabric model for us however since Monday morning the copyjob has failed. 
The consultant has now resigned but his account was only disabled today (weds). However we have made sure everything was taking off his account and put onto a service account. Since Monday it keeps saying Multi authentication has failed. 
But we don’t have Multi authentication on the service account 

 

also one of my report keeps crashing (even before this error above) and it keeps saying capacity issue with over 10000 lines

  • Hi Mpmp1​ ,

    "Unable to acquire user token" means the copy job is still trying to run as the consultant. Moving the connections to the service account isn't enough on its own, because the job itself runs under its owner. Failures starting on Monday, before the account was disabled, usually mean his sign-in was blocked earlier, for example by a password reset, revoked sessions or an MFA prompt he can no longer answer.

    To fix it:

    1. Sign in as the service account (or yourself), open the copy job's Settings > About, and select Take over.
    2. Edit both the source and destination connections and re-enter the credentials.
    3. Make a small change, such as renaming or editing the description, and save. This also updates the "last modified by" user.
    4. Check the schedule. If it still shows the consultant, recreate it.
    5. Do the same for any related pipelines, notebooks or dataflows he created.

    On MFA: even if MFA isn't enabled on the service account itself, a Conditional Access policy can still require it. Check Entra ID > Sign-in logs for the service account to see which policy is blocking it. Longer term, a service principal or workspace identity for connections avoids this problem.

    The report crash is a separate issue. It's most likely a visual that returns too many rows and hits the capacity's memory limit. Filter or aggregate that visual so it returns fewer rows, and check the Fabric Capacity Metrics app for throttling.

    Reference: Take ownership of Fabric items

    Sources:

    Please mark this post as solution if it helps you. Appreciate Kudos.

7 Replies

    • Mpmp1's avatar
      Mpmp1
      New Member

      The error I get is - Job failed to start 

      something wrong when trying to start the job. 
      job failed to start. Unable to acquire user token. Error code - Azure Active Directory client users error exception 

      • tayloramy's avatar
        tayloramy
        Icon for Super User rankSuper User

        Hi Mpmp1​,

        Have you tried re-authenticating the source and target connections, and taking over ownership of the copyjob item itself? After you take over ownership, update the connections, and then make a trivial change like changing the name or description, and save the copy job. 

  • v-achippa's avatar
    v-achippa
    Icon for Community Support rankCommunity Support

    Hi Mpmp1​,

    Thank you for confirming. Glad to hear that updating the schedule to use the service account resolved the issue. Thank you for being part of Microsoft Fabric Community.

    Thanks and regards,
    Anjan Kumar Chippa

  • Hi Mpmp1​ ,

    "Unable to acquire user token" means the copy job is still trying to run as the consultant. Moving the connections to the service account isn't enough on its own, because the job itself runs under its owner. Failures starting on Monday, before the account was disabled, usually mean his sign-in was blocked earlier, for example by a password reset, revoked sessions or an MFA prompt he can no longer answer.

    To fix it:

    1. Sign in as the service account (or yourself), open the copy job's Settings > About, and select Take over.
    2. Edit both the source and destination connections and re-enter the credentials.
    3. Make a small change, such as renaming or editing the description, and save. This also updates the "last modified by" user.
    4. Check the schedule. If it still shows the consultant, recreate it.
    5. Do the same for any related pipelines, notebooks or dataflows he created.

    On MFA: even if MFA isn't enabled on the service account itself, a Conditional Access policy can still require it. Check Entra ID > Sign-in logs for the service account to see which policy is blocking it. Longer term, a service principal or workspace identity for connections avoids this problem.

    The report crash is a separate issue. It's most likely a visual that returns too many rows and hits the capacity's memory limit. Filter or aggregate that visual so it returns fewer rows, and check the Fabric Capacity Metrics app for throttling.

    Reference: Take ownership of Fabric items

    Sources:

    Please mark this post as solution if it helps you. Appreciate Kudos.

  • v-achippa's avatar
    v-achippa
    Icon for Community Support rankCommunity Support

    Hi Mpmp1​,

    Thank you tayloramy​ and FarhanJeelani​ for the prompt response.

    As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the users for the issue worked? or let us know if you need any further assistance.

    Thanks and regards,
    Anjan Kumar Chippa

  • Thank you so muchtayloramy​ andFarhanJeelani​  i didn’t release we have to also update the scheduled to use the service account too. As the scheduled was created by the user who left it just didn’t like it. Thank you