5.5. Microsoft Azure Inter-connectivity

5.5.1. Service Menu Overview

  • In this menu, Microsoft Azure Inter-Connectivity, customer can connect Enterprise Cloud 2.0 (hereafter ECL2.0) to Microsoft Azure (hereafter Azure) by using Express Route Private Peering service.

  • By this menu, customer can establish closed connection between ECL2.0 and Azure and use multi cloud solution combining ECL 2.0 and Azure.

../../_images/Azure_summary_jp.png

5.5.1.1. Service Menu Features

The Microsoft Azure Inter-Connectivity service menu contains the following features and benefits.

  • Stable connection to Azure directly without Internet connection

  • Establish a physically redundant connectivity infrastructure.

  • Automatic provisioning of customer LAN side setting

5.5.2. Available Functions

5.5.2.1. List of Functions

The following functions are available from this service menu.

Functions

Function Overview

Azure Gateway Function

It provides a gateway function to connect between “ECL 2.0 Logical Network” and “Azure virtual network gateway”.

Self-Management Function

Provide the function to manage the Microsoft Azure connection menu by customer’s own operation via customer portal / API.

5.5.3. Description of Functions

5.5.3.1. Azure Gateway Function

In order to realize connection with Azure, we provide the following functions.

No.

Functions

Functions

1

Network Connectivity Function

  • It provides an interface for connecting with ECL 2.0 Logical Network and Azure virtual network gateway.

  • Please check the plan list for the destination Azure region name.

  • Connect with Azure via an intermediate router.

  • Provide connection with Azure’s private service (such as Virtual Machine). It is not possible to connect directly with Azure’s public service (Machine Learning, BLOB storage, etc.).

2

Address Setting Function

  • Customers are able to assign IP addresses and VRRP Group ID.

3

Advertisement using BGP / Static Route Function

  • Azure Provides BGP connection function with virtual network gateway.

  • Customers are able to set the Static Route destination for the Logical Network.

  • The destination network address of the static route and the connection network address of the gateway interface can be advertised to Azure as a BGP route.

  • The maximum number of allowable Static Routes is 32.

  • No restrictions are imposed to IP address ranges which can be set to the destination network of a static route. However, do not set a network which includes the IP address below and whose mask length is longer than the IP address below. BGP and VRRP operations may be affected resulting in communication disconnection, due to longest match.

    • Gateway IPv4 address, primary IPv4 address, and secondary IPv4 address of the gateway interface (Figure in the address setting section: G1/P1/S1)

    • The IPv4 address of the Azure connection interface and the IPv4 address of the intermediate router (figure of address setting section: P2 / S2 / P3 / S3)

4

Bandwidth Setting Function

  • You can set the bandwidth that can be processed by Azure gateway.

1.Network Connectivity Function

The Azure gateway provides the following two types of interfaces.

Functions

Specs / Restrictions

Azure connection interface

  • Azure Provides an interface for connecting with the virtual network gateway.

  • Only one interface is provided for one Azure gateway.

  • This interface is created at the same time as applying for Microsoft Azure connection.

  • Customers are not able to perform operations (addition, IP Address configuration, deletion) on the Interface by themselves.

  • This Interface implements the use of the Border Gateway Protocol (BGP) for redundancy.

Gateway Interface

  • Provides the Interface for connectivities with the Logical Network.

  • Only one interface is provided for one Azure gateway.

  • Note: Customers are able to assign the Logical Network destination of this Interface, and detach the connection.

  • Only one Azure gateway can be connected to one Logical Network. Multiple Azure gateways can not be connected.

  • This Interface implements the use of VRRP Protocol for redundancy.

../../_images/Azure_interface_jp.png

2.Address Setting Function

  • Provide the function of setting the address for the gateway interface.

  • The Azure gateway and the virtual network gateway are connected via the intermediate router, and the IP address of this section is allocated from the IP address of the subnet mask / 28 specified at the time of plan application. Please note that it can not be changed after application.

Parameter

Details

Gateway IPv4 Address

The Virtual IP Address for VRRP.

Primary IPv4 Address

IP address to be assigned to the interface on the primary side among the redundant Azure gateways

Secondary IPv4 Address

IP address to be assigned to the interface on the secondary side among the redundant Azure gateways

VRRP Group ID

The identifier of the specific VRRP group.

../../_images/Azure_ipaddress_jp2.png

Note

  • The following addresses are reserved by the provider and can not be used by the customer.
    • 100.127.0.0/26

3.Advertisement using BGP / Static Route Function

  • Azure Provides BGP connection function with virtual network gateway.

  • Customers can configure static routes from the Azure gateway for Logical Networks.

  • The destination network address of the static route and the connection network address of the gateway interface can be advertised to Azure as a BGP route.

  • The maximum number of allowable Static Routes is 32.

  • No restrictions are imposed to IP address ranges which can be set to the destination network of a static route. However, do not set a network which includes the IP address below and whose mask length is longer than the IP address below. BGP and VRRP operations may be affected resulting in communication disconnection, due to longest match.

    • Gateway IPv4 address, primary IPv4 address, and secondary IPv4 address of the gateway interface (Figure in the address setting section: G1/P1/S1)

    • The IPv4 address of the Azure connection interface and the IPv4 address of the intermediate router (figure of address setting section: P2 / S2 / P3 / S3)

  • The default route can be set to the destination network of a static route.

../../_images/Azure_routing_jp.png

4.Bandwidth setting function

  • You can set the bandwidth that the Azure gateway can handle. The band to be set up conforms to the band plan for which the customer has been contracted.

5.5.3.2. Self-Management Function

Customers are able to perform the following operations via the Customer Portal / API.

No.

Operations

Operable Actions

Details

1

Add / Remove Gateway Interface

Add / Remove Connectivity

Customers are able to create a Gateway Interface and connect to any Logical Network.
Customers are able to assign an IP Address to the Gateway Interface.
Customers are able to remove, and disconnect from the Gateway Interface.
2

Static Routing Setting / Routing Advertisement

Add or Remove Static Route / Advertised routes

You can set up a static route on Azure gateway and advertise BGP route to Azure side.


1.Addition / Removal of Gateway Interface

  • Customers are able to create a Gateway Interface and connect with any Logical Network. Customers can remove, and disconnect from the Gateway Interface.

  • Customers are able to select any IP Address whilst creating the Gateway Interface. As the Gateway Interface uses a redundant VRRP Protocol, the following addresses can be assigned.

Parameter

Details

Connected Network

Customers are able to connect to any Logical Network.

Gateway IPv4 Address

Virtual IP Address for VRRP.

Primary IPv4 Address

An IP address to be assigned to the interface of the Azure gateway on the ACT side among the redundant Azure gateways

Secondary IPv4 Address

IP address to be assigned to the interface of the Azure gateway on the STANDBY side among the redundant Azure gateways

VRRP Group ID

The VRRP ID utilized at the Gateway Interface.

Note

  • If a VRRP group ID duplicates on the same logical network, communications may not be performed properly. Therefore, be sure to specify a different value.

  • Customers are duly advised that the IP Address cannot be modified. Hence, if Customers would like to change / modify the IP Address, they are required to first remove and add a new connectivity for the Logical Network.

2.Static Route Setting / Routing Advertisement

Customers can set up static routes on the Azure gateway. Also, the setting contents of the static route are advertised on the Azure side as the BGP route.
Parameters for Static Route Settings are as follows.

Parameter

Details

Name

The name of specific Static Routes can be set.

Description

The description of specific Static Routes can be set.

Destination

You can set the destination network (IP address block) for this static route. Also, this address will be advertised on the Azure side as route information.

Next Hop

The next hop for the communication to the network specified as the destination can be set.


Note

  • Maximum number of Static Route will be 32.

  • The destination and next hop cannot be changed. If changes are to be made, deletion and creation of the static route are required.

5.5.4. Service Menu

5.5.4.1. Service List

  • For Microsoft Azure connection, we will provide the following plan to customers.

  • For Microsoft Azure connection, we will only provide bandwidth reservation type.

    • Guaranteed Bandwidth Plan

      • NTT Com provides the guaranteed transmission speed up to the designated bandwidth.

      • Stable throughput is expected because we have designed with enough margin to secure the bandwidth of the customer’s traffic.

Region

Plan (Maximum Bandwidth)

Guranteed Bandwidth

JP4 JP5

Azure region to be connected

   

East Japan

East Japan

Guaranteed Bandwidth

50M 50M
  100M 100M
  200M 200M
  500M 500M
  1G 1G

5.5.4.2. Order Types and Methods

  • This menu can be subscribed via order form.

Order Types

Order Methods

Offering Date

New application for Microsoft Azure connection

Submit order form (* 1)
Before applying, you need to obtain a service key at Microsoft Azure Portal (clearly stated in the application form)

20 business days

Application for discontinuation of Microsoft Azure connection

Submit order form (* 1)
Before applying, it is necessary to disconnect the Azure Express Route line from VNet.

20 business days


Note

  • (* 1) The Terms and Conditions for orders through the application form are as follows.

    • When making a new application, we start charging from the desired date of application. In the case where the month including the date on which provision is started and the month in which the cancellation or abolition occurred are the same month, or when the application date is the first day of the month, the contractor pays the fee for the month will do.

    • With regard to billing, new application starts and applies from 0:00 (UTC) on application date. Abolition will be applied 0:00 (UTC) on the desired date of discontinuation.

    • When compatible with portal / API, it is necessary for customers to implement new construction and abolition.

    • On the ECL 2.0 portal, it will temporarily appear as a VPN connection agreement. After the desired opening date, it will be displayed as Azure connection agreement.

    • Self-Management Function can not be used. “Add / Delete Gateway Interface”, “Static Routing Setting / Routing Advertisement” etc will be handled in correspondence with new connectivity / changes.

    • If you want to speed up and decelerate, you need to prepare in advance for Azure GW of the speed-up / decelerated band and switch it.


5.5.4.3. Order Flow

../../_images/Azure_order_jp.png

5.5.4.4. Important Things to Note when Ordering

Application conditions for Microsoft Azure connection are as follows.

  • Before applying, Azure’s contract · “Azure Express Route line” creation must be completed.

  • The service key issued in the creation of “Azure Express Route line” needs to be specified on the application form.

  • After applying this menu, you need to add “gateway interface” and “add a static route” on the Customer Portal.

  • After that, application will be completed by connecting “virtual network” to “Azure Express Route line” at Microsoft Azure Portal.

  • Support for Microsoft Azure Portal is not included in this menu. Please check Azure support (official document etc).

  • Multiple contracts are available for one tenant in this menu. The maximum number you can contract with one tenant is “4 contracts”. Therefore, customers who have the possibility of considering acceleration / deceleration, we recommend that you leave one contract for switching.

  • When two or more Azure gateways are connected to the same Logical Network, it is impossible to communicate because MAC addresses duplicate.

  • If you connect the Azure gateway, VPN gateway, AWS gateway to the same Logical Network, you can not communicate because the MAC address is duplicated.

Note

  • Newly establishing / abolishing one Microsoft Azure connection agreement can be applied once a day.

  • The reception hours for this Service Menu is 9: 30 - 17: 30 Japan Time on Weekdays.

5.5.5. Terms and Conditions

5.5.5.1. Usage Conditions with Other Service Menus

  • This service menu can be combined with all other service menus. Connections with the Logical Network is only possible with connectivities to the Data Plane.

  • It is possible to use it in combination with _ Hybrid Cloud with Microsoft Azure <https://ecl.ntt.com/documents/service-descriptions/hca/hc-azure.html> _. For details on Hybrid Cloud with Microsoft Azure, please check the service description.

Note

  • Since Hybrid Cloud with Microsoft Azure is not resaleable, customers need to contract directly with Microsoft Azure when reselling.

5.5.5.2. Minimum Usage Period

There is no minimum contract period.

5.5.6. Pricing

5.5.6.1. Initial Fee

There is no initial fee for this service.

5.5.6.2. Monthly Fees

This menu will charge for usage fee monthly. Monthly usage fee will be fixed monthly.

Note

  • “Azure Express Route” “Port charge”, “Transmission data transfer fee” will be charged from Microsoft Azure based on Azure Express Route specifications.

5.5.7. Quality of Service

5.5.7.1. Support Coverage

  • The functions described in this Service Description are subject to Support Services.

  • Problems caused by incorrect settings by the Customer (eg. Static Route Configuration etc.) are not supported.

  • Microsoft Azure service specification · Microsoft Azure Portal operation will not be supported in this menu. Please check Azure support (official document etc).

5.5.7.2. Operations

  • The Quality of Operation for this Service Menu meets the Operation quality of the prescribed Enterprise Cloud 2.0 Standards.

5.5.7.3. Maintenance

  • About disconnection time obstacle of less than 1 minute, since we may not be able to notify you, we appreciate your understanding.

5.5.7.4. SLA

  • The SLA for this Service Menu meets the SLA Standards defined by Enterprise Cloud 2.0.

5.5.7.5. Points to Note

  • Communication to the Azure connection gateway implements flow restriction to protect the service infrastructure.

  • For communication passing through the Azure connection gateway, flow rate restriction is not implemented, and quality and speed according to the contract plan are offered.

  • The maximum MTU size is 1,500 bytes.

  • We will not support except for the connection section of this menu. We will not notify customers about breakdowns of sections that Microsoft provides directly to customers.

  • The customer can not connect until VNet is connected. Therefore, we do not perform the opening test using Ping etc.