In AVS Implementation related Queries

2024-05-22T11:42:39.0733333+00:00

Hi Team,

Need your expertise inputs on the below mentioned queries that are

  1. AVS integration with Active Directory / Azure AD (Customer wanted to know whether they need to create the users manually on AVS vCenter or can they integrate with On-Prem AD).
  2. Can the Customer Carve out a range of IP's (IP's for VM's in AVS) from /22 range which is a prerequisite for AVS Implementation.
  3. Will there be any default range that is available for VM's inside the AVS after deployment.
  4. If step 2 and 3 is not the correct understanding, then what is the right method for allocation of IP's to the VM's inside the AVS.
  5. How about DNS for Name Resolution (can we integrate DNS Server which is already in place in the HUB vNET).
  6. Any prerequisites of having DNS and DHCP during AVS Deployment.

Thanks & Regards,

Ashok Chandra Dev.

Azure VMware Solution
Azure VMware Solution
An Azure service that runs native VMware workloads on Azure.
330 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,076 questions
0 comments No comments
{count} votes

Accepted answer
  1. vipullag-MSFT 25,366 Reputation points
    2024-05-22T15:12:38.2266667+00:00

    Hello Ashok Chandra Venkumahanti (Microland)

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    1.    AVS integration with Active Directory / Azure AD (Customer wanted to know whether they need to create the users manually on AVS vCenter or can they integrate with On-Prem AD).

    AVS can be integrated with traditional ADDS, yes!

    2.    Can the Customer Carve out a range of IP's (IP's for VM's in AVS) from /22 range which is a prerequisite for AVS Implementation.

    No, the /22 is for AVS Platform use only.

    3.    Will there be any default range that is available for VM's inside the AVS after deployment.

    No, you need to define a  new range non-overlapping with the AVS /22, rest of Azure and on-prem or use HCX network extender to extend your workload networks from on-prem into AVS during the migration (non-long-term solution for duration of migration only).

    4.    If step 2 and 3 is not the correct understanding, then what is the right method for allocation of IP's to the VM's inside the AVS.

    Either stretch the on-prem workload networks with HCX NE during migration or define completely new CIDR ranges and dedicated them to use within AVS.

    5.    How about DNS for Name Resolution (can we integrate DNS Server which is already in place in the HUB vNET).

    Yes this is possible, and required for ADDS integration as mentioned in #1

    6.    Any prerequisites of having DNS and DHCP during AVS Deployment.

    No, no pre-req during deployment. Not required after deployment as well. DHCP integration depends on how you have done the IP address assignment.

    Hope this clarifies.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful