Creating a Private Network Connection with ExpressRoute to your Skytap account

A Skytap Private Network Connection with ExpressRoute is a dedicated, secure network tunnel between a Skytap environment and an Azure virtual network.

For example, you can use a Private Network Connection with ExpressRoute to connect a Skytap environment to your corporate intranet to give your virtual data center access to corporate resources (such as databases, source repositories, and builds).

Your customer account can have up to ten VPNs or Private Network Connections connected at the same time. If you need additional VPNs or Private Network Connections, contact your Skytap sales representative.

Contents

Before you begin

Before you begin, you’ll need:

  • A valid and active Microsoft Azure subscription.
  • An administrator account in Skytap.
  • A Skytap environment.

    Use Skytap Subnet from the environment to define the Skytap subnet for the Private Network Connection with ExpressRoute.

    subnet

  • An Azure virtual network.

    The Azure virtual network will define the remote subnet. Included remote subnets cannot overlap with restricted subnets or the Skytap subnet defined in the VPN settings. For more information, see Remote Subnets settings.

  • An unattached Skytap static public IP address.

    A static public IP address is used as the Skytap peer IP address for the Private Network Connection with ExpressRoute.

    For instructions, see Adding a static public IP address to your account.

    If you do not have an available public IP address, contact your Skytap sales representative.

Creating and configuring a Private Network Connection with ExpressRoute

To create a Private Network Connection with ExpressRoute
  1. From the navigation bar, click Manage > WANs.

    Admin WANs

    The WANs page displays.

    WANS page

  2. Click New Private Network Connection. The New WAN page loads.

    New VPN

  3. Type a Name for the new Private Network Connection with ExpressRoute.
  4. Select the Azure Region the where the ExpressRoute will be created.
  5. Choose a Skytap static public IP address as the Skytap peer IP.
  6. To assign NAT IP addresses to any VMs connected to the ExpressRoute, select Apply NAT for connecting networks. This setting allows you to connect Skytap environments with overlapping IP addresses to the Private Network Connection with ExpressRoute. For more information, see Apply NAT for connecting networks.
  7. Type the Skytap subnet – the subnet of the environment that will be connected.
  8. Click Save. The Details tab displays a summary of the Private Network Connection with ExpressRoute settings, along with the message, We’re waiting for the authorization key so we can finish building your connection.

    New ExpressRoute connections are authorized during business hours (Pacific Time) and may take up to four hours.

    exr-pending

  9. After the connection is provisioned by Microsoft, a Resource ID and Authorization Key are displayed.

    exr-ready

  10. Sign into your Azure subscription and follow these steps to connect your ExpressRoute to your virtual network gateway.

    The Resource ID and Authorization Key are provided on the Details tab of the Skytap WANs page.

    • For the Authorization key of the Connection object, use the Authorization Key.
    • For the Peer circuit URI of the Connection object, use the Resource ID.
  11. Type the Azure virtual network subnet into Remote Subnet. Optionally, you can add remote subnets to exclude. Included remote subnets cannot overlap with restricted subnets or the Skytap subnet defined in the Private Network Connection with ExpressRoute settings. For more information, see Remote Subnets settings. remote subnets
    1. Enter a subnet range in Remote Subnets. The supported remote subnets are within the 3 to 32 bits range.
      1. Select include or exclude.
      2. Click Add.
  12. Test the WAN.
  13. Connect your Skytap networks to the Private Network Connection with ExpressRoute. The Skytap side of the Private Network Connection with ExpressRoute remains inactive until you attach at least one network with a running VM on it.
  14. Click Enable to begin sending traffic through the Private Network Connection with ExpressRoute. enable
  15. (Optional) Add Private Network Access Controls to limit the users, groups, or departments that can attach environments to the VPN. For more information, see Configuring access to a VPN or Private Network Connection.

Editing the name of an ExpressRoute connection

To change the name assigned to an ExpressRoute connection
  1. From the navigation bar, click Manage > WANs.

    Admin WANs

    The WANs page displays.

    WANS page

  2. Click Edit name (Edit) next to the name of the ExpressRoute connection.
  3. Enter a new name in the Rename WAN window.
  4. Click Save.

Editing the ExpressRoute connection access control list

See Configuring access to a VPN or Private Network Connection.