Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes the issues that are fixed in Update Rollup 74 in the following versions of Microsoft Azure Site Recovery:

Learn about the details of the issues that are fixed and the prerequisites that should be verified before you install this update.


To install Microsoft Azure Site Recovery Provider Update Rollup 74, you must have one of the following installed:

  • Microsoft Azure Site Recovery Provider (version 5.23.x or a later version)

  • Microsoft Azure Recovery Services Agent (version 2.0.9263.0 or a later version)

Note: You can check the installed provider version in the Programs and Features item in Control Panel.

Improvements made and issues fixed in this update

After you install this update, the following issues are fixed, and the following improvements are included.

Mobility Service

Linux OS Support

  • Azure to Azure/Modernized VMware/Physical to Azure

    • Debian 11

      • 5.10.0-30-amd64

      • 5.10.0-30-cloud-amd64

      • 6.1.0-0.deb11.21-amd64

      • 6.1.0-0.deb11.21-cloud-amd64

    • SLES12

      • 4.12.14-16.185-azure:5

    • SLES15

      • 5.14.21-150500.33.54-azure:5

    • RHEL9​​​​​​​

      • 5.14.0-70.97.1.el9_0.x86_64

      • 5.14.0-70.101.1.el9_0.x86_64

      • 5.14.0-284.62.1.el9_2.x86_64

      • 5.14.0-284.64.1.el9_2.x86_64

      • 5.14.0-284.66.1.el9_2.x86_64

      • 5.14.0-284.67.1.el9_2.x86_64

      • 5.14.0-284.69.1.el9_2.x86_64

      • 5.14.0-284.71.1.el9_2.x86_64

      • 5.14.0-427.13.1.el9_4.x86_64

      • 5.14.0-427.16.1.el9_4.x86_64

      • 5.14.0-427.18.1.el9_4.x86_64

      • 5.14.0-427.20.1.el9_4.x86_64

      • 5.14.0-427.22.1.el9_4.x86_64

  • New Distro Support

    • Redhat 8.10

    • Redhat 9.4


  • Added ASR V2A support for NVME disks in Linux.

Issues fixed:

  • Fixed issue of resync not being marked as complete after Windows upgrade.

  • Fixed issue related to failure of re-protect when there is difference of agent version in source and target region.

  • Fixed issues of upgrade failures and restart the service after upgrading. 

  • Fixed issue related to collection of Logs using ASRDiagnosticTool as an administrator.​​​​​​​

Microsoft Azure Site Recovery replication appliance


  • Delete and reset replication appliance

Issues fixed

  • Fixed an issue with throwing exception whenever the attachments registry key is not found



Physical discovery server


Discovery server


Site Recovery provider


Appliance configuration manager


Proxy server


Replication service


Re-protection server


Push install agent


Recovery Services agent


Process server


Updating your Azure Site Recovery On-Premises components

Between an on-premises VMware or physical site to Azure (Modernized experience) 

  1. Ensure that your on-premises management appliance is up to date by navigating to the Appliance configuration manager. If not, download the latest version for the components that are behind the latest version.

  2. Go to the Azure portal, and then go to the Protected Items > Replicated Items page. Select a VM on this page. Select the Update Agent button that appears at the bottom of the page for each VM. This updates the Mobility Service Agent on all protected VMs.

Agent version during last restart

Upgrading to

Is a restart mandatory?



Not mandatory



Not mandatory



Not mandatory




First upgrade to version 9.29, and then restart before you upgrade to version 9.30 (because the difference between the last restart version and the target version is greater than 4).

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!