Azure Vaulted Backup on ADLS - backup jobs failing

Chris Rice 20 Reputation points
2026-08-18T14:34:43.8966667+00:00

ADLS Azure Vaulted Backup jobs failing due to error code: UserErrorMaxConcurrentOperationLimitReached due to a backup job stuck 'in progress'.

The stuck job has been in this state for nearly 4 days - I'm unable to delete the job in Azure portal as the option is greyed out.

I've stopped the backup and restarted in an attempt to clear the job but this hasn't worked.

Can anyone help with this situation, please?

Azure Backup
Azure Backup

An Azure backup service that provides built-in management at scale.

Answer accepted by question author
Ravi Varma Mudduluru 12,545 Reputation points Microsoft External Staff Moderator
2026-09-03T08:07:52.0433333+00:00

Hello @Chris Rice

Thank you for reaching out to Microsoft Q&A.

The backend team cancelled the stuck operation from the backend. After the cancellation, the resource status was updated to Succeeded.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Was this answer helpful?

2 people found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jose Benjamin Solis Nolasco 12,026 Reputation points Volunteer Moderator
    2026-08-18T14:44:15.37+00:00

    Welcome to Microsoft Q&A!

    Hello @Chris Rice I hope you are doing well,

    The error UserErrorMaxConcurrentOperationLimitReached means Azure Backup believes another backup operation is still active, so a new backup cannot start. Microsoft documents that this can occur when an existing backup is still running, particularly during a long-running initial backup. (learn.microsoft.com)

    However, since your job has remained In Progress for nearly four days and stopping/restarting the backup has not cleared it, this may indicate that the original operation is stuck rather than simply taking longer than expected.

    I recommend:

    1. Go to Backup vault → Backup jobs and confirm the old job remains In Progress.
    2. Check the protected ADLS account for a very large number of blobs/versions, as these can significantly increase the duration of an initial backup.
    3. If appropriate, review your Storage Account lifecycle management policy and consider cleaning up unnecessary old blob versions to reduce future backup processing time. (learn.microsoft.com)
    4. Avoid repeatedly starting additional on-demand backups while the existing operation is still reported as running.

    For ADLS vaulted backup, Microsoft also documents that backup operations depend on snapshots and replication, and an initial backup can take at least 30–40 minutes under normal conditions. (learn.microsoft.com) However, since your job has remained In Progress for nearly four days and stopping/restarting the backup has not cleared it, this may indicate that the original operation is stuck rather than simply taking longer than expected. I will scale this thread internally so MS can take a look at the backend too.

    References:

    If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.