Azure Migrate Replication - Agentless fails - "Provisioning is required as replication extension is in a failed state"

Vaughn DeFouw 31

I am trying to replicate a VMWare VM over to Azure Local using Azure Migrate. I have the source and destination appliances configured. When I choose to Replicate, it fails with the error: "Provisioning replication extension: Provisioning is required as replication extension is in a failed state". I am trying to do agentless replication. If I go under the "Discovered servers" section, it has inventory about the server and lets me choose "Dependencies (Agentless)". It also has the Software Inventory.

It feels like it is trying to migrate with the Agent instead of doing Agentless, but I can't seem to figure out how to do it without the agent.

Any help would be appreciated.

3 answers

Naveena Patlolla 400 Reputation points Microsoft Vendor

2025-02-11T03:23:18.9833333+00:00

Hi @Vaughn DeFouw

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Since Agentless Replication works via vSphere APIs and does not install an agent inside the VM.

1.Please check whether you configured Replication type Agentless , to check Navigate to Migration and Modernization---Overview—Under properties

2.Restart the Azure Migrate Appliance and try Replication. The Replication Extension used by Azure Migrate: Server Migration (Agentless Replication) is Manged by Microsoft.

3.If you created Agent based, please try re-creating Agent less using https://learn.microsoft.com/en-us/azure/migrate/vmware/tutorial-migrate-vmware#prerequisites

Feel free to reach out if you have any further questions or need additional information—I’m happy to assist!

Please provide your valuable comments

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Please sign in to rate this answer.
Vaughn DeFouw 31 Reputation points

2025-02-11T17:28:02.4166667+00:00

Thank you for the response.

It's already set to "VMware agentless". I did dig deeper into the "Azure Migrate: Migration and modernization" events, and it shows this:
Error ID 1005004:

Attempt to verify access to storage account '' failed with message: 'This request is not authorized to perform this operation.'.

Possible causes:

The storage account does not exist, has not been setup correctly or it has insufficient permissions for blob storage access.

Recommendation:

Ensure storage account is setup correctly. Contact Microsoft support for further assistance.

I'm not sure what to adjust on a storage account or why that might be failing. Any further help would be appreciated.

Naveena Patlolla 400 Reputation points Microsoft Vendor

2025-02-12T07:55:39.7666667+00:00

Hi Vaughn DeFouw,

I understand that you're experiencing difficulties accessing storage account.

Please follow below steps to resolve Azure Migrate Storage Access Issues:

1)Locate the Azure Migrate App Registration:

Open Microsoft Entra.

Navigate to App registrations > All applications.

Search for Azure Migrate.

Copy the Display Name of the app registration associated with Azure Migrate.

2)Assign Storage Blob Data Contributor Role:

Go to the Resource Group where your Azure Migrate Project is located.

Open the Storage Account used by Azure Migrate.

Navigate to Access Control (IAM).

Assign the Storage Blob Data Contributor role to the app registration (using the Display Name you copied).

3)Check Storage Account Firewall Rules:

In the Storage Account, go to the Networking section.

Ensure no firewall rules are blocking access.

If restrictions exist, either remove them or add an exception for Azure Migrate.

4)Assign Permissions for Managed Identity (if applicable):

Open Azure Migrate. Navigate to Properties.

Copy the Managed Identity associated with Azure Migrate.

Assign the Storage Blob Data Contributor role to this Managed Identity in the Storage Account’s IAM settings.

Thankyou,

Vaughn DeFouw 31 Reputation points

2025-02-12T16:58:58.1366667+00:00

Thank you for the assistance.

#3 on your list was especially important. It seems to have been a firewall issue where I had to add our local network in to the firewall rules on the storage account.

I assume that when you're actually migrating to Azure, maybe that isn't an issue - which is why none of the guides covered it.

The Storage Blob Data Contributor role was already applied when I checked.

Getting an error during the migration now.
ErrorCode: '1028' VM: 'Server'. Appliance: 'AZMigrate'. Error: 'The operation VirtualDiskSnapshotOpen failed with the error 'Unknown error' [Unknown error]'. DiskId: '6000C290-b8ab-d746-ce7e-7bb63be30e0f'. DiskPath: '[esxi-VVol] rfc4122.3b2995ca-552d-4aea-a1f3-f4b8fa773a1f/Server.vmdk'.

We utilize vVols on our VMware environment. I'm wondering if that is causing a problem now. I verified there are no snapshots on the VM. I will try moving the storage to a non-vVol to see if that makes it happy. I will likely open a new request if I can't get it to migrate stil.

Thank you again.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Pranay Reddy Madireddy 2,085 Reputation points Microsoft Vendor

2025-02-13T22:39:41.3933333+00:00

Hi Vaughn DeFouw

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Since you're considering moving the VM storage to a non-vVol datastore, this is a good approach. Migrating the VM to a standard VMFS or NFS datastore might help bypass any vVol-specific issues.

check your VMware environment, including vCenter and ESXi hosts, is using versions that work with Azure Migrate. Some versions or setups might not support all features, which can lead to issues.

check that there are no hidden or leftover snapshots linked to the VM. Even if there are no visible snapshots, remnants from old ones can still cause migration issues.

Make sure the Azure Migrate service account has the necessary permissions in vSphere to access and manage virtual disks. It may need specific roles or permissions for vVol management.
https://learn.microsoft.com/en-us/azure/migrate/vmware/migrate-support-matrix-vmware-migration?context=%2Fazure%2Fmigrate%2Fcontext%2Fvmware-context

If you have any further queries, do let us know.

If the answer is helpful, please and "Upvote it".
Please sign in to rate this answer.
Pranay Reddy Madireddy 2,085 Reputation points Microsoft Vendor

2025-02-17T16:46:38.5133333+00:00

Hi Vaughn DeFouw
If you had a chance to see my comment to your question. If it was helpful, please click "Upvote" and ''accept answer'' on my post let us know Thank you...!

Vaughn DeFouw 31 Reputation points

2025-02-17T16:54:18.1133333+00:00

I'm having some new issues with the cluster - one of the nodes had to be rebuilt due to an issue with Bitlocker and now I can't get that node to add back in - the add-server module doesn't want to work. Until I have 3 nodes back in the cluster, I can't test the migrations. I don't think it actually had anything to do with the vVol.

If I can figure out why this command won't work, I can go back to testing the Azure Migrate project.
Add-Server

VERBOSE: Looking up shared vhd product drive letter.

WARNING: Unable to find volume with label Deployment

VERBOSE: Suppressed Warning Unknown category for 'NuGet'::'GetDynamicOptions': 'Provider'

The 'Add-Server' command was found in the module 'ScaleNodeOperations', but the module could not be loaded. For more

information, run 'Import-Module ScaleNodeOperations'.

+ CategoryInfo : ObjectNotFound: (Add-Server:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CouldNotAutoloadMatchingModule
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Naveena Patlolla 400 Microsoft Vendor

Hi Vaughn DeFouw

I understand that you're facing issue in loading the module

Can you please Manually Import Module:

Attempt Import: Try importing the module manually to capture detailed error messages.

Run: Import-Module -Name ScaleNodeOperations -Verbose

The -Verbose flag provides additional context, which can help in diagnosing the issue

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Vaughn DeFouw 31 Reputation points

2025-02-18T16:26:36.99+00:00

That command isn't working - full output is in the next comment.

Vaughn DeFouw 31

It won't import with the command you provided or with the other command I tried below.

Import-Module : The specified module 'ScaleNodeOperations' was not loaded because no valid module file was found in
any module directory.
    + CategoryInfo          : ResourceUnavailable: (ScaleNodeOperations:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Import-Module "C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.AdminOperations\ScaleNodeOperations\ScaleNodeOperations.psm1" -Force
VERBOSE: Looking up shared vhd product drive letter.
WARNING: Unable to find volume with label Deployment
VERBOSE: Suppressed Warning Unknown category for 'NuGet'::'GetDynamicOptions': 'Provider'
Get-Package : No package found for 'Microsoft.AzureStack.Solution.Deploy.AdminOperations'.
At C:\Program Files\WindowsPowerShell\Modules\CloudCommon\InfraVmHelpers.psm1:140 char:28
+ ...  $package = Get-Package -Name $NugetName -Destination $drivePath -Err ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Microsoft.Power...lets.GetPackage:GetPackage) [Get-Package], Exception
    + FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.GetPackage
Import-Module : The specified module 'C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.A
dminOperations\ScaleNodeOperations\ScaleNodeOperations.psm1' was not loaded because no valid module file was found in
any module directory.
    + CategoryInfo          : ResourceUnavailable: (C:\Program File...Operations.psm1:String) [Import-Module], FileNot
   FoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Share via

Azure Migrate Replication - Agentless fails - "Provisioning is required as replication extension is in a failed state"

3 answers

Your answer