# Register a manually installed Mobility agent without discovery credentials

> How should a modernized Site Recovery agent be registered when machine and virtualization discovery credentials cannot be supplied?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:40+00:00
- Modified: 2026-09-10T00:32:00+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

How should a modernized Site Recovery agent be registered when machine and virtualization discovery credentials cannot be supplied?

## Potentially affected

Consider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.

## DSE recommendation

Document the machine-to-appliance pairing before distributing installation material.

## Article

## Source facts

Modernized Azure Site Recovery offers credential-less discovery when the machine and vCenter or ESXi credentials cannot be provided. This path requires manually installing the Mobility service and enabling its credential-less discovery option. Registration uses a configuration file generated on the chosen appliance from the source machine’s unique details string. The configuration file is then supplied to the agent on that source machine. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview).

## Applicability

Consider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.

## DSE recommendation

Document the machine-to-appliance pairing before distributing installation material. Keep each source identifier associated with its own generated configuration file; do not circulate one convenient file as a fleet-wide registration package. Separate approval to install the service from the decision to supply discovery credentials, and record which documented installation mode was selected.

## Verification

On a controlled candidate machine, verify the identifier used to generate the file, the intended appliance, and the registration result. Reconcile the registered source with the inventory before enabling replication. Treat a completed software installation as an intermediate checkpoint: do not close onboarding until the correct machine has registered through the chosen workflow.

## Official references

[Microsoft Learn: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview).

## Primary reference

- Name: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery - Azure Site Recovery | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Register a manually installed Mobility agent without discovery credentials,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.