Azure Blob vaulted backup stuck in ProtectionError/SubscriptionSuspended after subscription reactivation

Question

Azure Blob vaulted backup stuck in ProtectionError/SubscriptionSuspended after subscription reactivation

Clayton Parker 20

An Azure Blob vaulted backup instance remains stuck after its Azure subscription was briefly suspended and then reactivated.

Current backup-instance state:

provisioningState: SubscriptionSuspended
currentProtectionState: ProtectionError
protectionStatus: ProtectionError
errorCode: UserErrorStorageAccountInLockedState

The subscription is now Enabled. The storage account is healthy, and Microsoft.DataProtection is registered. The storage account has no ReadOnly resource lock; it only has an intentional CanNotDelete lock. It uses a private endpoint, but successful vaulted backups previously completed with this same networking configuration.

The last successful backup completed on August 10, 2026. Existing recovery points remain visible and must be preserved.

Troubleshooting already attempted:

Portal Fix protection error
/sync with Default
/sync with ForceResync
resumeBackups / Resume protection
Backup-instance PUT with DeepValidation
Ad hoc backup

Portal Fix protection error calls:

POST .../sync?api-version=2025-01-01

with:

{"objectType":"SyncBackupInstanceRequest","syncType":"Default"}

It returns HTTP 400:

UserErrorInvalidRequestParameter: Parameter ProtectionStatus in request is invalid

No Data Protection repair job is created. Resume and ad hoc operations are also rejected because the instance is already in ProtectionError.

Portal repair activity ID:

4546591f-e6a5-4a27-9e6a-25666c695037-Ibz

Original error activity ID:

f8351335-a7bf-4245-bf53-bac4f7191996

This appears to be stale service-side state left from the temporary subscription suspension. Is there a supported, non-destructive way to reconcile/reset SubscriptionSuspended and ProtectionStatus without deleting the backup instance, vault, or existing recovery points?

Clayton Parker 20 Reputation points

2026-08-25T01:43:40.3133333+00:00

A week has gone by with no response...
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-08-27T07:04:29.5233333+00:00

Hello Clayton Parker

Thank you for posting your query on Microsoft Q&A platform.

I have reached out with few details via Private message, Could you please share it?

Answer accepted by question author

0 additional answers

Your answer

Clayton Parker 20 Reputation points

2026-08-25T01:43:40.3133333+00:00

A week has gone by with no response...
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-08-27T07:04:29.5233333+00:00

Hello Clayton Parker

Thank you for posting your query on Microsoft Q&A platform.

I have reached out with few details via Private message, Could you please share it?

Answer 1

Hello @Clayton Parker

Thank you for posting your query on Microsoft Q&A platform.

As per our conversation we have an update from Product team that On 16-Aug around 16:57 UTC the subscription hit its spending cap and got suspended, then it was reactivated about 5 minutes later. While it was suspended, Azure disabled the storage account. Our backup service happened to run its suspend handling during that window and tried to touch the storage account (its lock and billing rules), but since the account was disabled those calls failed and the backup instance went into ProtectionError.

When the subscription came back online, the automatic resume kicked in, but it doesn't accept an instance that's already sitting in ProtectionError, so it just skipped it and moved on. There's no retry after that, which is why it's been stuck ever since. The last successful backup was on 10-Aug. The existing recovery points are all intact.

Current PG team working on to fix this issue. I will keep you posted updates via MS Teams.

If the answer is helpful, could you please click "Accept Answer" & "upvote" it and this helps other community members who may encounter a similar issue in the future.

Thanks,
Suchitra.