Exercise A3: Configuring VNet Peering (Optional)

In this exercise, you use Microsoft Azure to configure bi-directional peering. You should configure VNet-to-VNet peering only if the following is true:

  • You created a new VNet that does not have an AD VM inside it
  • You are not using Express Route for VNet peering
  • You are not using VPN for express route peering

In this tutorial, it is assumed that another VNet is in the same region as the AD/DNS server, to which you are peering for access to those services.

1. Peering Connects the Horizon Cloud Service VNet on Microsoft Active Directory

  1. Select the Virtual Networks pane and select a network.
  2. Click Peering.
  3. On the right-most pane, verify that the peer is not yet connected.

2. Add Peering Details

  1. In the Add peering pane under Peer details, provide the required information:
    • Name: Enter a name to distinguish this action from others.
    • Virtual network deployment model: Select the Resource manager option.
    • Subscription: Select your subscription.
    • Virtual network: Click Choose a virtual network, and select your VNet.
  2. Under Configuration, provide the following required information: enabled
    • Allow virtual network access: Enabled.
    • Configure forwarded traffic settings: Enabled.
    • Configure gateway transit settings: Check to allow gateway transit.
  3. Click OK.

3. VNet Peering Is Connected

  1. Return to the third pane if you are not already there.
  2. Verify that VNet peering is now connected.

4. VNet Peering Overview Details

  1. In the second pane, click Overview.
  2. Review the additional details now displayed in the third pane.

For more information, see the Getting Started with VMware Horizon Cloud Service on Microsoft Azure guide.

After you finish configuring the VNet, proceed to the next exercise to configure the DNS server.


Add your comment

E-Mail me when someone replies to this comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.