When configuring a backup for Blobs I get Protection Error: DppChannelAgentDefaultError
The template deploys successfully but there is a protection error. After clicking Fix protection I get this error message with no further details: DppChannelAgentDefaultError. This storage account was previously configured for operational backup, but that data has been deleted so this is setting up a completely new backup. There is no mention anywhere on the internet of 'DppChannelAgentDefaultError', I have no idea what it means.
Azure Backup
-
Naveena Patlolla • 7,500 Reputation points • Microsoft External Staff • Moderator
2025-11-05T11:26:15.61+00:00 Hi David Lane
Below are the possible causes:
1)A storage account was previously configured for Azure operational backup.2)The original backup data or configuration was deleted (either manually or due to retention expiry).
3)A new backup attempt is made using the same storage account, but Azure Backup still retains some internal metadata or expects a previous configuration.
To fix your issue try these steps:
Option 1: Clean up orphaned backup metadata
Go to Backup center → Vaults → [Your Vault] → Backup Instances.
Check if your storage account still appears there (even in a failed or deleted state).
If it does, stop protection and delete backup data:
Stop backup with delete data if possible.
Wait a few minutes for backend cleanup.
If it doesn’t appear, try removing old metadata via PowerShell:
Connect-AzAccount Select-AzSubscription -SubscriptionId "<sub-id>" # Check backup instances related to the resource Get-AzDataProtectionBackupInstance -ResourceGroupName "<vault-rg>" -VaultName "<vault-name>" | Where-Object { $_.Properties.DataSourceInfo.ResourceId -like "*<your-storage-account-name>*" } # If any exist, remove them Remove-AzDataProtectionBackupInstance -Name "<instance-name>" -ResourceGroupName "<vault-rg>" -VaultName "<vault-name>" -ForceOption 2: Re-register the storage account
Remove the storage account from the backup vault if it's still associated.
Reconfigure the backup ensuring no residual metadata remains.
Please let me know if you face any challenge here, I can help you to resolve this issue further
If the comment was helpful, please click "Upvote"
-
David Lane • 16 Reputation points
2025-11-05T16:14:11.5066667+00:00 I removed the backup instance, running those powershell command returned nothing so all must be cleaned up, and I even fully deleted the backup vault. After setting up again I still get the same protection error: DppChannelAgentDefaultError
-
Naveena Patlolla • 7,500 Reputation points • Microsoft External Staff • Moderator
2025-11-05T16:50:38.7933333+00:00 Hi David Lane
1)Use Azure Resource Graph to find orphaned backup metadataRun this query in Azure Resource Graph Explorer:
resources | where type =~ 'microsoft.recoveryservices/vaults/backupstorageconfig'If anything shows up, it means backup metadata still exists. You’ll need to manually purge it via support.
2)Try a different storage account (for testing)
To confirm the issue is tied to the original storage account, try enabling backup on a new storage account. If it works, that confirms the original account has stale metadata.
-
Kristjan Gudjonsson • 0 Reputation points
2025-11-06T01:55:55.5166667+00:00 I'm setting up AKS backup for the first time and getting the same error on all newly deployed infrastructure.
-
Håkon Johan Thallaug Heuch • 0 Reputation points
2025-11-06T08:42:28.3733333+00:00 I also get the DppChannelAgentDefaultError when clicking "Fix protection" after adding new storage account to a backup vault. The "Protection error" state appears when containers are initially missing in the storage account. This is normal. Then after adding containers to the storage account clicking the "Fix protection" button should normally fix the problem, but this is not working.
-
David Lane • 16 Reputation points
2025-11-06T11:17:57.25+00:00 Vaulted backups configure correctly on other storage accounts that have never had a backup policy.
It appears I am not the only person with this problem so there is an issue with the product that Microsoft needs to fix, and I should not have to pay for support for that.
The kusto query provided is not correct, that is for recovery services vaults and we are dealing with microsoft.dataprotection/backupvaults. Also nested resources can't be viewed like that in Azure Resource Graph Explorer. There are no results when querying for:
resources | where type == "microsoft.dataprotection/backupvaults/backupinstances" resources | where type == "microsoft.dataprotection/backupvaults/backupjobs" resources | where type == "microsoft.dataprotection/backupvaults/backuppolicies" resources | where type == "microsoft.dataprotection/backupvaults/deletedbackupinstances" resources | where type == "microsoft.dataprotection/locations/deletedvaults" resources | where type == "microsoft.dataprotection/locations/deletedvaults/deletedbackupinstances" -
Naveena Patlolla • 7,500 Reputation points • Microsoft External Staff • Moderator
2025-11-06T18:17:53.2466667+00:00 Hi David Lane
We are investigating from the backend and will update you soon. -
David Lane • 16 Reputation points
2025-11-07T14:13:20.1933333+00:00 This issue is clearly affecting multiple people and you are asking me to pay $100 per subscription to identify an undocumented bug in Microsoft's systems?
-
Naveena Patlolla • 7,500 Reputation points • Microsoft External Staff • Moderator
2025-11-11T13:25:57.36+00:00 Hi David Lane
I have reached out to you in a private messageThankyou
-
zshel • 0 Reputation points
2025-11-13T14:57:02.47+00:00 I'm have a similar if not the same issue. The interesting part is our infrastructure is controlled by terraform. Even using a known good version of our terraform code, we are unable to create new backup instances without getting the error "DppChannelAgentDefaultError: Received a non-success response". The issue was noticed for us the first week of November, but is unknown when it actually first started.
-
Frank Morrison • 0 Reputation points
2025-11-17T19:38:54.85+00:00 I am also getting this error when I tested creating a backup of one storage account. At first, it allowed me to delete the Backup Instance, but now I get an error when attempting to delete the instance. The account is stuck in a failed state and I cannot even attempt to resolve it because I cannot change the current configuration. This needs to be fixed by MSFT IMMEDIATELY!!
-
Naveena Patlolla • 7,500 Reputation points • Microsoft External Staff • Moderator
2025-11-18T06:14:25.85+00:00 In David Lane case, the issue was resolved after turning off Soft Delete and PITR on the storage account, which allowed the vaulted backups to configure properly.
Frank Morrison- Please raise a separate question so we can investigate and provide a solutionThank you
-
Simon Schneider • 0 Reputation points
2025-11-25T13:03:55.5233333+00:00 I am also encountering the
DppChannelAgentDefaultErrorwhen deploying backup vault with instances and policies using Terraform. The issue only appears when deploying the Backup Instances via IaC (Terraform) - creating the same configuration manually through the Azure Portal works without any problems.And im also stuck in the protection failed error not possible to delete the blob instances .
Need a fix asap.
-
Kristjan Gudjonsson • 0 Reputation points
2025-12-03T20:28:41.3366667+00:00 Our fix ended up being within the Storage Account network settings. Adding the backup vault to resource instance immediately cleared the
DppChannelAgentDefaultErrorerror.When deployed via Terraform, resource type is not required.
If you are doing via Portal, select
Microsoft.DataProtection/BackupVaults
Sign in to comment