Skip to content

Azure Cloud Connect

Azure Cloud Connect enables you to establish a Microsoft Azure ExpressRoute circuit directly to the Wanscale Platform. This provides a private, high-bandwidth connection to your Azure resources.

Provisioning Workflow

The diagram below outlines the lifecycle of creating and deploying Azure Cloud Connect:

flowchart LR
    A(Create the ExpressRoute in Azure) --> B(Receive S-Key from Microsoft) --> C(Create Azure CLoud Connect in the portal) --> D(Link to the ExpressRoute in the portal) --> E(Configure BGP sessions in the portal)

    %% Custom style for nodes
    style A fill:#34ebb1
    style B fill:#34ebb1
    style C fill:#34ebb1
    style D fill:#34ebb1
    style E fill:#34ebb1

Prerequisites

Step 1 - Create the ExpressRoute in Microsoft Azure

Follow the Official Microsoft Documentation to create your ExpressRoute circuit.

Info

Required Connection Details: During the Azure setup, you must specify the following:

  • Connectivity Provider: Digital Realty
  • ExpressRoute Location: Amsterdam

Step 2 - Retrieve the Service Key (S-Key)

Once the circuit is created in the Azure Portal, Microsoft will provide a Service Key (S-Key). Copy this key; it is required to bridge your Azure circuit with the Wanscale Platform.

Configuration Workflow

Step 3 - Create Azure Cloud Connect in the Wanscale portal

  1. Navigate to the Home page of the Wanscale Platform.
  2. Click the Add Service button.
  3. Select Azure Cloud Connect from the service list.
  4. Click Go to service form.
  5. Complete the following fields:
    • Label: Enter a descriptive name for the Azure Cloud Connect.
    • Tags (Optional): Add metadata for internal organization.
    • Cloud Type: Choose Azure
    • Speed: Select the bandwidth that matches your ExpressRoute circuit.
    • Cloud connection type: For Azure, select Redundant.
    • Virtual Network: Select the VNET to which this circuit will attach.
    • Primary Subnet: Enter the primary subnet in CIDR notation exactly as provided in the Azure setup.
    • Secondary Subnet: Enter the secondary subnet in CIDR notation exactly as provided in the Azure setup.
    • Vlan (C-TAG): Enter your C-Tag if applicable to your setup.
    • AS Number: Enter the Local AS Number for this BGP connection.
  6. Click Save.

After saving the configuration, you must link the service to Microsoft using your Service Key.

  1. From the Azure Cloud Connect service screen, expand General in the left sidebar and select Basic.
  2. On the General Details screen, click Connect to the cloud (bottom-left box).
  3. In the right sidebar, enter your Service Key.
  4. Click Connect to the cloud

Step 5 - Configure BGP sessions

Finally, configure the BGP settings to enable routing between Wanscale Platform and Azure. Note: This process must be completed for both BGP Peers.

  1. Navigate to the Home page of the Wanscale Platform.
  2. Select the new Azure Cloud Connect from the services list.
  3. In the lift sidebar, expand Configuration and select BGP
  4. Click the button Add BGP Configuration
  5. The right sidebar opens, complete the following fields:
    • Neighbor IP: Select the appropriate Neighbor IP from the dropdown menu (AS Numbers will auto-fill).
    • Enable BFD: Toggle to On for sub-second failure detection.
      • Detect Multiplier: Default is 3.
      • Receive Interval: Default is 300ms.
      • Send Interval: Default is 300ms. Route Policy Settings:
      • Click Add import settings Define rules for incoming routes.
        • Select Local Preference: Set the preference value for routes learned from this peer.
        • Select Import Default Route: Check to accept a default route if advertised.
        • Select Import Prefixes: Enter prefixes in CIDR:operator-size format (e.g., 10.0.0.0/16:le-24). Multiple entries should be comma-separated.
      • Click Add export settings Define rules for outgoing routes.
        • Select Export VNET Space: Check to advertise all known VNET routes to Azure.
        • Select AS Prepend: Enter AS numbers to prepend for path engineering (e.g., 65000,65000).
        • Select Export Prefixes: Enter prefixes in CIDR:operator-size format (e.g., 10.0.0.0/16:le-24). Multiple entries should be comma-separated.
        • Select Export Default Route: Check to advertise a default route to Azure.
  6. Click Create

Note

Understanding BFD: Bidirectional Forwarding Detection (BFD) provides rapid link failure detection. If "hello" packets fail, BFD instantly triggers BGP to reroute, ensuring higher availability than standard BGP timers.

The default BGP timers (Multiplier=3, Receive- and Send Interval=300ms) are defaults also used on the Azure side.

Note

Applying Changes: Like all networking services in the portal, your new Azure Cloud Connect will not be active until you deploy the changes. See Workflows and Applying Changes.