ASR Site Recovery Jobs

Question

ASR Site Recovery Jobs

GerryNicol 21

For a single server in ASR I am getting repeated Site recovery jobs running as follows

Update network settings on the primary virtual machine
Processing virtual machine migration

Is there an easy way to stop these jobs from running?

VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-07-24T13:35:08.9266667+00:00
Hello GerryNicol,

The behavior you're describing is generally seen when Azure Site Recovery is still maintaining or synchronizing configuration information for a protected or migrated VM. The recurring jobs"Update network settings on the primary virtual machine" and"Processing virtual machine migration" are commonly associated with ASR migration metadata, network mapping updates, or pending configuration synchronization activities.

To determine whether action is required, could you check the following:

Are these jobs completing successfully or failing?

Is the VM still actively protected by ASR, or has the migration already been completed?

Under Recovery Services Vault > Replicated Items > > Jobs, do the job details indicate any specific warnings or errors?

If the migration has already been completed and ASR protection is no longer needed, disabling replication for that replicated item will stop further migration-related processing. However, if replication is still required and the jobs are succeeding, these may simply be background synchronization operations performed by ASR.

Please share the job status (Succeeded or Failed) and a screenshot of the job details page, and we can determine whether this is expected behavior or a configuration issue requiring remediation.
GerryNicol 21 Reputation points

2026-07-24T14:20:05.7933333+00:00

The VM is still protected, and Replication Health is healthy. A successful test failover can be completed. These jobs are only running for this single VM out of many protected by ASR

They are successful however the processing virtual machine migration shows as follows,

ASR is showing

Prerequisite check

Successful

Update replication settings for the virtual machine

Skipped

Update protection for the virtual machine

Skipped

Update the virtual machine agent

Skipped

Updating the provider states

Skipped
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-07-25T14:53:30.92+00:00

GerryNicol Based on the information provided, I do not see evidence of an Azure Site Recovery replication issue. The VM remains Healthy, is still protected, and a Test Failover completes successfully, which confirms that replication and recovery functionality are working as expected. [

The key detail is that the"Processing virtual machine migration" job completes successfully, while all update-related stages are reported as Skipped. This indicates that Azure Site Recovery is evaluating the VM configuration but is not finding any changes that need to be applied.

Since this behavior is occurring for only one VM, I recommend reviewing whether there are any pending migration-related operations, network configuration updates, or automation processes targeting this specific replicated item. The best way to identify the source is to review the Activity Log and the Correlation ID associated with one of the recurring jobs to determine what is triggering the operation.

At this stage, I would not recommend disabling and re-enabling replication, as replication health is normal and there is no indication of protection failure.

Could you check the Activity Log for one of these recurring jobs and confirm whether a specific caller, service principal, automation account, Azure Migrate project, or Resource Mover operation is associated with the Correlation ID? That will help determine the exact source of the recurring jobs and the appropriate remediation.

1 answer

Your answer

VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-07-24T13:35:08.9266667+00:00

Hello GerryNicol,

The behavior you're describing is generally seen when Azure Site Recovery is still maintaining or synchronizing configuration information for a protected or migrated VM. The recurring jobs"Update network settings on the primary virtual machine" and"Processing virtual machine migration" are commonly associated with ASR migration metadata, network mapping updates, or pending configuration synchronization activities.

To determine whether action is required, could you check the following:

Are these jobs completing successfully or failing?

Is the VM still actively protected by ASR, or has the migration already been completed?

Under Recovery Services Vault > Replicated Items > > Jobs, do the job details indicate any specific warnings or errors?

If the migration has already been completed and ASR protection is no longer needed, disabling replication for that replicated item will stop further migration-related processing. However, if replication is still required and the jobs are succeeding, these may simply be background synchronization operations performed by ASR.

Please share the job status (Succeeded or Failed) and a screenshot of the job details page, and we can determine whether this is expected behavior or a configuration issue requiring remediation.
GerryNicol 21 Reputation points

2026-07-24T14:20:05.7933333+00:00

The VM is still protected, and Replication Health is healthy. A successful test failover can be completed. These jobs are only running for this single VM out of many protected by ASR

They are successful however the processing virtual machine migration shows as follows,

ASR is showing

Prerequisite check

Successful

Update replication settings for the virtual machine

Skipped

Update protection for the virtual machine

Skipped

Update the virtual machine agent

Skipped

Updating the provider states

Skipped
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-07-25T14:53:30.92+00:00

GerryNicol Based on the information provided, I do not see evidence of an Azure Site Recovery replication issue. The VM remains Healthy, is still protected, and a Test Failover completes successfully, which confirms that replication and recovery functionality are working as expected. [

The key detail is that the"Processing virtual machine migration" job completes successfully, while all update-related stages are reported as Skipped. This indicates that Azure Site Recovery is evaluating the VM configuration but is not finding any changes that need to be applied.

Since this behavior is occurring for only one VM, I recommend reviewing whether there are any pending migration-related operations, network configuration updates, or automation processes targeting this specific replicated item. The best way to identify the source is to review the Activity Log and the Correlation ID associated with one of the recurring jobs to determine what is triggering the operation.

At this stage, I would not recommend disabling and re-enabling replication, as replication health is normal and there is no indication of protection failure.

Could you check the Activity Log for one of these recurring jobs and confirm whether a specific caller, service principal, automation account, Azure Migrate project, or Resource Mover operation is associated with the Correlation ID? That will help determine the exact source of the recurring jobs and the appropriate remediation.

Answer 1

The repeated “Update network settings” and “Processing migration” entries appear to be Azure Site Recovery control-plane jobs associated with protected-item maintenance or migration state. Their exact purpose cannot be confirmed from the job names alone. Open each job and compare the protected item, operation ID, start time, duration, result, and error details, then review the replicated item’s health and recent events. There is no safe supported way to cancel recurring maintenance while keeping protection intact. If replication is still required and the jobs succeed, leave protection enabled and investigate only warnings, failures, or replication-health degradation. If the migration or protection is no longer required, use the normal Disable replication or Remove protected item workflow and verify cleanup completes. Do not use force deletion merely to suppress jobs; it can purge configuration without completing ordinary cleanup. If successful jobs continue unexpectedly, send their operation IDs and vault diagnostics to Microsoft support.