Updating ASR application to Rollout 83 with private endpoints enabled.

Hello Hunter,

Based on the current Azure Site Recovery (ASR) rollout model, there is no publicly available standalone download package for every ASR application rollout version. For environments using private endpoints, automatic updates from Azure may not be possible if the appliance cannot reach the required update endpoints.

For Update Rollup 83, Microsoft documentation indicates that the latest Mobility Service installers should normally be obtained through the Azure Portal (Recovery Services vault > Site Recovery Infrastructure > Prepare Infrastructure) rather than from the GitHub repository, which is no longer maintained with the latest Windows installers.

If the Rollout 83 binaries or Mobility Service installer are not currently available in your vault or through the documented download locations, there is generally no supported alternative public download source. In that situation, you may need to either:

1. Allow temporary connectivity to the required update endpoints so the appliance can retrieve the update automatically.
2. Open a Microsoft Support request to verify whether the Rollout 83 package is available for your specific deployment and obtain guidance for an offline/manual update path.

At this time, if the rollout package has not yet been published to the available download channels for your appliance scenario, waiting for Microsoft to make the update available may be necessary. The Rollup 83 release itself is documented and includes Mobility Service version 9.66.7691.1

https://support.microsoft.com/en-us/servicing/azure/update/2026/02/update-rollup-83-for-azure-site-recovery

I hope this helps. If you're using the modernized VMware/Physical appliance, please share the appliance type and deployment model, and we can identify the recommended update path for that specific configuration.

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.