Leaseweb offers private connectivity to Azure services from selected Leaseweb Data centers.
You can create a network connection from your Leaseweb services to Azure services
Description
Cloud Connect supports ExpressRoute to connect your Leaseweb services to Azure.
ExpressRoute has different two different peering options, Azure private peering and Microsoft peering,
Cloud Connect supports only the Azure Private peering, which provides access to Azure resources on Private IP space (RFC 1918)
Deploying a connection to Azure with ExpressRoute
The delivery of a Cloud Connect - Azure order has 3 phases:
- Phase 1: Requesting information
- Phase 2: Providing connection details for Azure
- Phase 3: Configuring BGP and testing
Phase 1
To deploy a connection to Azure, we need some information. You will receive an email requesting the below:
- Azure service key
- Private IP space used in VPC in Azure
- Login to Azure portal
- Click on Express Route circuits.
- On the new window, click on Create.
- The fields required to fill in are:
- Resource group = select a group form the drop down
- Region: Select the region with your Azure resources that you want to connect to
- Name: provide a name for the Express Route circuit
And click Next: Configuration > at the bottom of the page
5. On the Configuration tab, the fields required to be filled are:
- Port type: Select Provider
- Create new or import form classic: There are 2 options, Create new or import. Please select the one that suits your purposes.
- Provider: Select Megaport (Megaport is our partner for our Cloud Connect services)
- Perring location: Select the metro area that you would like to connect Azure.
- Bandwidth: select the bandwidth from the drop down
- SKU: there are two options, Standard and Premium
- Standard: provides connectivity to all Azure regions in a geopolitical area
- Premium: provides connectivity to all Azure regions globally
- Billing model: There are two options. Metered and Unmetered, select one that suits your purposes
- Allow classic operations: There are two options, Yes or No. Please select one that suits your purposes
Click Next: Tags if you would like to add tags or Review + create at the bottom of the page
6. After validation, click Create at the bottom of the page
7. The message “Your deployment is complete” appears, click the Go to resource button.
8. The service key will appear in this window.
Please, reply to our email providing the key and the IP prefix that you are using in Azure VPC(s).
Phase 2
Once we have deployed, we will notify you by email and provide the connection details to enter in Azure portal.
We provide the below details:
- Customer ASN
- Microsoft IP address
Please, follow the instructions below to enter the details in the ExpressRoute circuit that you created for this connection
- Login to Azure portal
- Click on Express Route circuits icon
3. The new window will display your Express route circuits. Click on the one that you created for this connection.
4. In the next window, you will see all details of the circuit, under Peerings click on Azure private peering, as this is the only peering that Leaseweb Cloud Connect supports
5. The fields that need to be filled are:
- Customer ASN: please fill in the one that we provided
- Subnets: select IPv4
- IPv4 Primary subnet: please fill in the Microsoft IP addresses that we provided.
- If you have ordered two connections for resiliency, please fill in the second IP subnet that we provided to IPv4 secondary subnet
- VLAN ID: please fill in the Leaseweb Private Network VLAN ID
Click Save at bottom of the page and confirm that the above actions have been performed by replying to our second email.
If you have already a Virtual Network gateway for the Azure resources that you would like to connect to, you need to connect it to your ExpressRoute circuit
- Go to the ExpressRoute circuit that you created for the connection and click on Connections
2. On the next window, the fields required to be filled are:
- Name: provide a name for the connection
- Connection type: Select ExpressRoute
- Virtual network gateway: select the gateway
- ExpressRoute circuit: Select the ExpressRoute circuit that you created for this connection
3. Once you saved, under status you will see the message Succeeded.
The connection between ExpressRoute circuit and VNet is established,
If you do not have a Virtual network gateway yet, please follow the instructions here to create one.
Phase 3
You will be notified by email that the BGP session on Leaseweb side has been configured and asked to test the connection.
We will also provide the the Leaseweb Private IP address that we reserved to be the Gateway,
On your Leaseweb servers, please add a static route for your Azure IP space using the Leaseweb Private IP address as Gateway that we provided.