An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
Welcome to Microsoft Q&A
Hello @Pritam Jangid
Based on the details you've provided, you've already validated the two most common causes of Error 153017:
- DNS resolution to the private endpoints is working.
- TCP connectivity on port 443 is working.
That narrows the investigation significantly because Error 153017 is raised when ASR cannot upload replication data/logs to the cache storage account, and successful DNS/TCP tests don't guarantee that the actual Blob write operation is succeeding.
A few areas I'd focus on:
1. Validate the cache storage account configuration
For Azure-to-Azure replication, the cache account has specific requirements. Verify that:
- The cache account is General Purpose v2.
- The cache account is located in the same region as the source VM (Central India in your case).
- The cache account still exists and is the account currently selected for replication.
- Any unsupported storage features are not enabled.
Reference:
2. Verify actual Blob write access, not just connectivity
Test-NetConnection only proves the endpoint is reachable.
The most useful next step is to perform an authenticated upload test from the source VM to the cache storage account using AzCopy. If the upload fails, the HTTP response and storage request ID can often reveal whether the issue is:
- Authorization (403)
- Storage account policy
- Network/NVA/proxy interference
- Private endpoint routing
Reference:
3. Review outbound dependencies beyond the storage account
Even when using private endpoints, ASR still requires connectivity to several Azure services. In particular, verify that outbound HTTPS access isn't being restricted by:
- Proxy servers
- Azure Firewall
- NVA appliances
- Forced tunneling
Reference:
4. Enable ASR diagnostics and inspect the failed job
To get the actual backend error:
- Open Recovery Services Vault → Site Recovery Jobs.
- Locate the failed replication/protection job.
- Export the job details.
- Enable Site Recovery diagnostic logs and send them to Log Analytics.
- Reproduce the failure and review the corresponding records.
References:
5. Private endpoint support
Using a cache storage account with public network access disabled and a Blob private endpoint is a supported scenario, provided all private networking requirements are met.
Reference:
One question that would help narrow this down further:
Did you disable storage account key access ("Allow storage account key access") on the cache account, or are you using the newer managed identity-based cache account configuration?
That distinction can be important in isolating authentication-related causes for Error 153017.
If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions. Thanks!