Microsoft.DataMigration Resource Provider Stuck in "Registering" State Across Multiple Subscriptions

Question

Hello,

I am attempting to register the Microsoft.DataMigration resource provider in Azure but the registration remains stuck in the Registering state for an extended period (1-12 hours)and never completes.

Issue Details

Resource Provider: Microsoft.DataMigration

Subscription Type: Pay-As-You-Go/VSES

Reproduced on: Multiple subscriptions

Registration Duration: More than 30 minutes consistently

Azure Portal Notification:

'Register' operation check timed out on Resource Provider 'microsoft.datamigration', please refresh resource providers list to check for registration status.

Azure CLI Output

az provider show --namespace Microsoft.DataMigration --query "{State:registrationState, Namespace:namespace}"

Output:

{

"Namespace": "Microsoft.DataMigration",

"State": "Registering"

}

Attempted registration from Azure Portal.

Attempted registration using Azure CLI.

Waited more than 30 minutes/overnight for registration to complete.

Verified that the provider remains in the Registering/Unregistering state.

Attempted unregister/register cycle.

I attempted to unregister the provider and reviewed the Azure Activity Log. The Activity Log shows the unregister operation completed successfully:

"status": {
    "value": "Succeeded",
    "localizedValue": "Succeeded"
},
"subStatus": {
    "value": "OK",
    "localizedValue": "OK (HTTP Status Code: 200)"
}

However, even several hours after the successful operation, the Resource Providers blade continued to display the provider in a transitional state (Unregistering/Registering).

I am currently evaluating ALZs and Azure Database Migration Service for a SQL Server to Azure SQL Managed Instance migration scenario. Since the Microsoft.DataMigration provider cannot be registered successfully, I am unable to setup a dummy environment.

Could somebody confirm whether there is a known issue with Microsoft.DataMigration provider registration or advise on additional troubleshooting steps?

Thank you.

Answer 1

Hello tashi-04,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Microsoft.DataMigration Resource Provider Stuck in "Registering" State Across Multiple Subscriptions.

It is failing because the Azure pre-upgrade validation detected one or more blocking conditions, most commonly unsupported extensions, incompatible entries in shared_preload_libraries, read replicas, pending restart-required parameter changes, logical replication objects, or authentication requirements for certain source versions. . - https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade

What you can do is to remove or remediate every blocker reported by the upgrade validation log before retrying the upgrade. Do not retry the upgrade repeatedly without fixing the validation errors. First run upgrade validation, review the failed checks, remove unsupported preload libraries such as blocked extension modules, drop or upgrade incompatible extensions, delete read replicas if present, complete pending maintenance or restart-required operations, verify sufficient free storage, and then rerun validation. When validation passes, perform the in-place major version upgrade from the Azure portal or Azure CLI. - https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade, https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-perform-major-version-upgrade You can remediate upgrade-readiness issue, this is not a backend-only issue.

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

---

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Answer 2

Please keep in mind that Azure may continue to show the Microsoft.DataMigration resource provider as Registering, even though it is already ready to use in the specific Azure region where you plan to deploy. This can happen because Azure completes provider registration separately in each supported region, while the portal displays an overall registration status.

Therefore, instead of repeating the unregister/register process, the most useful test is to try creating a current Azure Database Migration Service resource in the intended region. If the resource is created successfully, you can continue even though the provider still shows Registering. If the deployment fails with a provider-registration error after several hours, the issue is more likely on the Azure platform side and should be reported to Microsoft Support.