my appliance is registered successfully but Azure file storage agent service is not connected

Hello Bi Bi Kadejatul kubra,

Thank you for reaching out to the Microsoft Q&A forum. 

It sounds like your appliance registered just fine but the Azure File Storage agent service itself isn’t coming online or showing as connected. Below are a few things you can try, plus some questions that’ll help us zero in on the root cause if you’re still stuck.

Troubleshooting steps to try first

Verify the service status

On Windows appliances (Azure Migrate appliance) go to the configuration manager → View appliance services and confirm the relevant service (for example, the DRA service) is running. If it’s stopped, open an elevated command prompt and run: • net stop dra • net start dra

On a Storage Mover agent VM (Linux or Windows), confirm the agent process is running. If on Linux, for example, run: systemctl status xdm-agent (or restart it with systemctl restart xdm-agent).

Check network connectivity to Azure endpoints

If you’re using Storage Mover: log into the agent’s restricted shell and run “Test network connectivity” (menu item 3) to make sure the agent can reach the Storage Mover service and any Private Link scopes you’ve configured.

If you’re on a Migrate appliance: rerun the prerequisites checks in the configuration manager and verify DNS resolution of your private link FQDNs (if you’re using private endpoints).

Review firewalls/proxies

Ensure your appliance or agent can reach all required Azure URLs or private endpoints: • For Azure Migrate: the appliance needs access to Azure Migrate project endpoints, Key Vault endpoints, Storage endpoints, etc. • For Storage Mover: it needs access to the public or private endpoint of your Storage Mover resource.

If you’re behind a proxy, double-check the proxy settings in the appliance/agent configuration and credentials (if required).

Look at the logs

Azure Migrate appliance logs are under C:\ProgramData\ASRLogs on Windows or in the appliance configuration manager.

Storage Mover agent logs can be collected from the agent VM (menu item 5 in xdmsh) for deeper insight.

If none of that helps, please share a bit more detail so we can dig in: • Which solution are you using? (Azure Migrate appliance vs. Azure Storage Mover agent vs. Azure File Sync agent) • OS and version of the appliance/agent VM • Exact name of the service showing as “not connected” and any error messages or codes you see • What network topology you have (public internet vs. private endpoints) and any proxy/firewall in between • Any log snippets or screenshots of the failure state

References

1. How to register and troubleshoot the Azure Storage Mover agent https://learn.microsoft.com/azure/storage-mover/agent-register?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#step-2-register-the-agent
2. Troubleshoot the Azure Migrate appliance (service-disconnected scenarios) https://learn.microsoft.com/azure/migrate/troubleshoot-appliance?view=migrate#appliance-is-disconnected
3. Azure Migrate appliance private endpoint DNS resolution guidance https://docs.microsoft.com/azure/migrate/how-to-use-azure-migrate-with-private-endpoints#verify-dns-resolution

Hope this helps—let me know the answers to those questions, and we’ll take it from there!

HI Bi,

Not sure which Storage account you need to connect but Azure Migrate does not require agent afaik, can you check the pre-req and process after successful registration over here and provide more details which agent you are looking to connect? https://learn.microsoft.com/en-us/azure/migrate/migrate-appliance?view=migrate

Hope this helps.

JS

==

If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.