Share via

AVS SRM deployed in vSphere but is showing failed in Azure.

Tom Nesbitt 0 Reputation points Microsoft Employee
2025-03-04T16:08:46.36+00:00

When deploying AVS SRM it deploys successfully in vSphere but is showing failed in Azure. The error message we are experiencing is "Privilege check failed for user VSPHERE.LOCAL\cloudadmin for missing permission Cryptographer.ManageKeyServers".

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
878 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pranay Reddy Madireddy 2,490 Reputation points Microsoft External Staff
    2025-03-05T05:31:06.4933333+00:00

    Hi Tom Nesbitt

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

    Log into the vSphere Client.

    Navigate to Administration > Roles.

    Identify or create a role that includes the Cryptographer.ManageKeyServers privilege.Assign this role to the VSPHERE.LOCAL\cloudadmin user or group at the appropriate level.

    Verify that the VSPHERE.LOCAL\cloudadmin user has all necessary privileges for SRM deployment, including permissions related to disaster recovery and replication.

    Restart the vCenter Server and SRM services on both the protected and recovery sites after updating permissions to apply the changes.Retry deploying AVS SRM in Azure after resolving the permissions issue.

    https://learn.microsoft.com/en-us/azure/azure-vmware/disaster-recovery-using-vmware-site-recovery-manager

    Check that the same account used to install SRM has administrative privileges on both sites, as SRM deployments often require this consistency.

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

    If the answer is helpful, please and "Upvote it".

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.