Azure Migrate-Initial Replication Failing-Installing Mobility Service and preparing target Failed

Gopi Chander 0 Reputation points
2024-01-10T13:21:06.6766667+00:00
  • Error ID

28040

  • Error Message

An Azure Resource Manager operation failed.

  • Possible causes

Azure error message: 'Resource 'asrseeddisk-P_PREECC-PHYSICAL-9c6ee5c4-7cb6-44a2-a6e5-02ba507099ee' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"Require a tag on resources","id":"/providers/Microsoft.Management/managementGroups/SAPQAS/providers/Microsoft.Authorization/policyAssignments/ea3db953d7f34823a914c622"},"policyDefinition":{"name":"Require a tag on resources","id":"/providers/Microsoft.Authorization/policyDefinitions/871b6d14-10aa-478d-b590-94f262ecfa99"}}]'.'.

  • Recommendation

Please resolve the error and try the operation again.

  • First Seen At

1/10/2024, 2:08:50 PM

-

  • Error ID

539

  • Error Message

The requested action couldn't be performed by the Replication Provider.

  • Possible causes

The Provider action failed. Check other errors for more information.

  • Recommendation

Resolve the issue and retry the operation.

I'm getting this error suddenly for set of servers during replication, whereas the same appliance VM was used for replicating/migrating servers couple of weeks back. successfully.

Any assistance ?

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
718 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Gopi Chander 0 Reputation points
    2024-01-16T00:59:50.66+00:00

    @SadiqhAhmed-MSFT ,thanks for your response.

    Few points i would like to highlight.

    1. there are no firewall/network/connectivity or proxy issues during Azure Migrate Replication configuration.
    2. Last week we migrated few systems using the same appliance to the Azure QAS Subs/Vnet without issues.
    3. upon checking the changes implemented, customer had created Azure Policies for tagging in the QAS Subscription which is the root cause for this issue.

    Finally, after removing the policy from the Subscription, the issue is sorted and the Replication works.