Azure Migrate Replication Appliance registration failing with "Resources creation for the appliance timed out" and InternalServerError

Question

Azure Migrate Replication Appliance registration failing with "Resources creation for the appliance timed out" and InternalServerError

Bingxue Zhang 0

I am setting up Azure Migrate for migrating 3 Linux VMs from GCP to Azure using the agent-based (physical server) method.

I have successfully deployed the Azure Migrate Appliance on a Windows Server for discovery.
I am now configuring the Replication Appliance (separate Windows Server).
During the configuration/registration process, I encounter the following error:

Error Details:

Resources creation for the appliance timed out. Please retry the operation. If the issue persists, please contact Microsoft support. { 'ProvisioningState': 'Running', 'RequestId': null, 'StatusCode': 'InternalServerError', 'TargetResource': { 'id': '/subscriptions/<PII Removed>/resourceGroups/rg-team-5027/providers/Microsoft.OffAzure/ServerSites/gcp-to-azubb8aphysicalsite', 'resourceName': 'gcp-to-azubb8aphysicalsite', 'resourceType': 'Microsoft.OffAzure/ServerSites' }, 'StatusMessage': { 'status': 'Failed', 'error': { 'code': 'InternalServerError', 'message': 'Encountered internal server error. Please try again', 'target': null, 'details': null, 'additionalInfo': null } }}

Steps Already Tried:

Restarted the Replication Appliance server multiple times.
Retried the operation after waiting 10-30 minutes. <PII Removed>
Appliance Type: Replication Appliance (for physical/GCP servers)
Number of servers to migrate: 3 Linux VMs from GCP
The discovery appliance works fine; the issue occurs specifically during Replication Appliance resource creation.

Please help investigate why the ServerSites resource creation is failing with InternalServerError and timeout.

Lakshma Reddy Vattijonnala 1,415 Reputation points Microsoft External Staff Moderator

2026-07-06T08:27:02.9466667+00:00

Hi @Bingxue Zhang Thank you for reaching out to Microsoft Q&A. We are looking into the issue and we will get back to you shortly with an update
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-06T13:27:39.1433333+00:00
Hello Bingxue Zhang

Thank you for posting your query on Microsoft Q&A.

The error you're seeing is not at the appliance/OS level , it's failing at the Azure Resource Manager (ARM) layer while creating the backing Microsoft.OffAzure/ServerSites resource (gcp-to-azubb8aphysicalsite) for your Replication Appliance. The ProvisioningState: Running → StatusCode: InternalServerError →*"Resources creation for the appliance timed out"* pattern typically points to one of the following:

1. Required resource providers are not registered on the subscription The Replication Appliance registration creates resources under Microsoft.OffAzure, Microsoft.Migrate, Microsoft.RecoveryServices, Microsoft.KeyVault, and Microsoft.Storage. If any of these are in NotRegistered / Registering state, the ServerSite ARM PUT will time out with an internal error.

Run these on the target subscription and confirm all return Registered:

Get-AzResourceProvider -ProviderNamespace Microsoft.OffAzure Get-AzResourceProvider -ProviderNamespace Microsoft.Migrate Get-AzResourceProvider -ProviderNamespace Microsoft.RecoveryServices Get-AzResourceProvider -ProviderNamespace Microsoft.KeyVault Get-AzResourceProvider -ProviderNamespace Microsoft.Storage

If any are missing, register them and retry:

Register-AzResourceProvider -ProviderNamespace Microsoft.OffAzure

2. Account used on the appliance doesn't have the right roles on the project / resource group:

For the ServerSite resource to be created, the signed‑in user on the appliance configuration manager needs, at minimum, Contributor on the resource group rg-team-5027 and the same permissions that were used to generate the project key. If a different user is used, ARM creation of the child resources silently retries and eventually times out. Please use the same Azure account that generated the project key from the Azure Migrate hub, or grant it Contributor + Key Vault access (Get/List/Set for Keys, Secrets, Certificates).

3. Azure Policy / resource lock blocking Microsoft.OffAzure/ServerSites creation Check the resource group rg-team-5027 and the subscription scope for:

Any DeleteLock / ReadOnly lock on the RG.

Any Azure Policy with deny effect on Microsoft.OffAzure/*, tag-required policies, or region-restriction policies. A silently denied nested deployment will surface as InternalServerError from the OffAzure RP.

4. Stale/orphaned Server Site with the same name If a previous replication appliance registration was attempted (or a project was recreated in the same RG), an orphaned gcp-to-azubb8aphysicalsite ServerSite may still exist. Delete it via Resource Explorer (portal → All resources → filter type Microsoft.OffAzure/ServerSites) and retry registration with a new, unique appliance name.

5. Appliance‑side connectivity to OffAzure endpoints The appliance must reach the OffAzure/Migrate control‑plane URLs on TCP 443 without proxy/firewall interception. Run Diagnose and solve from the appliance configuration manager and confirm the checks pass, especially Service endpoint connectivity and Essential resources availability.

6. Transient regional issue Because the error is InternalServerError from the OffAzure RP, it can also be a transient backend condition in the project's region. If steps 1–5 are clean, wait 30–60 minutes and retry with a different appliance name so a fresh ServerSite is created (retrying with the same name may re-hit the half-created resource).

Hope this helps!

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-09T06:55:29.0233333+00:00

Hello Bingxue Zhang

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thank you.

1 answer

Your answer

Lakshma Reddy Vattijonnala 1,415 Reputation points Microsoft External Staff Moderator

2026-07-06T08:27:02.9466667+00:00

Hi @Bingxue Zhang Thank you for reaching out to Microsoft Q&A. We are looking into the issue and we will get back to you shortly with an update
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-09T06:55:29.0233333+00:00

Hello Bingxue Zhang

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thank you.

Answer 1

hi Bingxue Zhang & thx for sharing urs issue here at Q&A portal,

so this looks backend-side, the discovery appliance working is a good clue. The failure happens while Azure Migrate is creating the Microsoft.OffAzure/ServerSites resource for the replication appliance, and the service returns InternalServerError with the operation stuck in Running until timeout. That points to a failed control-plane provisioning step, not the Windows appliance itself. Restarting the server or retrying the wizard won’t fix a stuck ServerSites resource. I’d check the resource group Activity Log once for a correlation ID or failed deployment details, then open an Azure Migrate support case with the subscription, resource group, site resource ID, timestamp, and full error payload.

The real root cause is the ServerSites resource creation failing in Azure. The timeout is only the secondary symptom. Microsoft will need to trace and clear or repair that backend operation.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/