An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
Hello @Hunter
This is an important distinction with Rollup 83: you don't need to update the ASR replication appliance from Rollup 80 to Rollup 83 because Microsoft hasn't released a replication appliance update for Rollup 83.
Microsoft's current supported-version table shows:
- Rollup 83: Replication appliance = N/A, Mobility service = 9.66.7691.1
- Rollup 82: Replication appliance = N/A, Mobility service = 9.66.7643.1
- Rollup 81: Replication appliance = N/A, Mobility service = 9.66.7640.1
- Rollup 80: Replication appliance = 9.66.7567.1, Mobility service = 9.66.7567.1
So if your replication appliance is already on 9.66.7567.1 (Rollup 80), that is currently the latest published appliance version. Rollup 83 only updates the Mobility Service component.
The private endpoint behavior you're seeing is also expected. Microsoft explicitly documents that automatic upgrades aren't supported with Private Endpoints, so you need to handle Mobility Service upgrades manually in this configuration.
Therefore, I wouldn't try to force an appliance upgrade to Rollup 83. The corresponding appliance package doesn't exist. Keep the appliance on the currently supported Rollup 80 version, and update the Mobility Service separately when the appropriate 9.66.7691.1 package becomes available through the supported update path for your environment.
There also appears to be a documentation/distribution gap around obtaining the current Windows Mobility Service package; another recent Q&A thread reports the same issue with Rollup 83 and private endpoints.
Sharing these references with you:
What's new in Azure Site Recovery
Update Rollup 83 for Azure Site Recovery – Microsoft Support
Configure Site Recovery with Private Endpoints
So, based on Microsoft's current documentation, you don't need to wait for an ASR appliance Rollup 83. The appliance itself has no Rollup 83 release.