Skip to main content

Creating Cloud Connection (Azure)

This page explains how to connect to Microsoft Azure (hereinafter referred to as Azure) using the Create Cloud Connection function on the OCX Portal. OCX provides virtual interconnection for ExpressRoute to Azure.

About ExpressRoute *External link.

Preparation​

Please confirm the following before creating a Cloud Connection:

Preparation in OCX Portal​

  • Your User Role must be either admin or user.

Preparation in Azure Portal​

Please create an ExpressRoute circuit in the Azure portal and have the following information ready:

Determining the Communication Method with CPE​

When using Azure, you can connect the cloud and your CPE (Customer Premise Equipment) using one of the following two methods. Please choose the method suitable for your network environment. Unless there is a specific reason, the Single Tag (dot1q) method is recommended, as the Double Tag (QinQ) method is highly complex and offers few advantages.

  • Single Tag (dot1q) Method

    • Packets delivered from Azure are sent to the CPE using the dot1q method (IEEE 802.1Q).
    • When connecting an Azure Cloud Connection to a VCI, the VLAN ID configured on the CPE side will simply be the VLAN ID set for the VCI.
    • Note: This method must be selected if you plan to connect the Azure Cloud Connection to an OCX-Router (v1) Interface.

  • Double Tag (QinQ) Method

    • Packets delivered from Azure are sent to the CPE using the QinQ method (IEEE 802.1Q Tunneling).
    • For network design patterns and CPE configuration examples using QinQ, please refer to Connection Patterns for Microsoft Azure and On-premises.
    • When connecting an Azure Cloud Connection to a VCI, your CPE must handle QinQ packets. In this case, the S-Tag/C-Tag on the CPE are as follows:
      • S-Tag (Outer VLAN ID): The VLAN ID set in the VCI.
      • C-Tag (Inner VLAN ID): The VLAN ID specified when creating the Azure Cloud Connection.

Procedure for Creating a Cloud Connection (Azure)​

  1. Log in to the OCX Portal.

  2. Click [Cloud Connections] from the left navigation bar.

  3. From the Cloud Connections list page, click [Create] and select Microsoft Azure.

  4. Fill in the following items on the input screen and click [Create]. Items marked with an asterisk (*) are required.

    • Note: For Azure, only Cloud Connection with Redundancy can be created.
    • You must enter the following settings for both the Primary and Secondary Cloud Connections.
    • Name
      • Enter any name (Max 40 characters). Using an easily identifiable name is recommended for easier management.
      • Leading and trailing spaces are automatically removed.
    • Speed (Bandwidth)
      • Select from 50, 100, 200, 500Mbps, 1, 2, or 5Gbps. (Bandwidths below 1Gbps have been supported since November 2023).
      • The value will be the same for both Primary and Secondary connections.
      • Warning: Once created, you cannot change the bandwidth to a value lower than the initial setting.
    • VLAN ID
      • As of November 2023, VLAN IDs are automatically assigned by the OCX system, so this parameter does not need to be entered. Existing resources can continue to be used as-is.
    • Cloud Name
      • Azure will be displayed.
    • Cloud NNI PoP Name
      • Select the same Peering Location used when creating the ExpressRoute circuit in the Azure portal.
      • The Cloud NNI PoP for the Secondary connection is automatically selected as the optimal pair for the Primary selection.
    • Transfer Method to CPE
      • Select either Single Tag (dot1q) or Double Tag (QinQ) as determined during preparation.
    • Cloud Connection Service Key
      • Enter the Service Key issued by Azure.

  5. Review the costs in the [Confirm Creation] pop-up and click [Create].

  6. Confirm that the status of the created Cloud Connection becomes available on the list page. The status billing pending will also be displayed, indicating a grace period before billing begins.

Configuration on the Azure Portal​

After the Cloud Connection is ready, you must configure the BGP settings for ExpressRoute circuit peering (Microsoft Peering / Azure Private Peering) in the Azure portal.

Please refer to the following for procedures (External links):

The creation of the Cloud Connection (Azure) is now complete.

Remarks​