ExpressRoute.
for Microsoft Azure & Office 365

Provision fast, secure, and dedicatedconnectivity to Azure.

INFOPAPER

Connecting to Microsoft Azurewith Megaport
We make it easy to provision fast, secure, and private
connections between your data centre and MicrosoftAzure. As a Microsoft Azure ExpressRoute Partner, we
provide enterprises with dedicated access to Azure
private and Microsoft public resources via a global
Software Defined Network (SDN), from hundreds oflocations worldwide, in just a few clicks.

Provisioning ExpressRouteconnectivity to Azure withMegaport enables:••Improved security with private network accessthat bypasses the public internet
Higher network performance, consistency,and predictability•Savings on egress traffic costs from your VPC toyour on-premise network•API integration between Megaport and MicrosoftAzure that simplifies the provisioning of connections
for a fast and seamless user experience•Simplified connectivity options without the useof Q-in-Q

How it Works
Physical fibre connections (NNIs) between Megaportand Microsoft Azure are established to dual Microsoft’sEnterprise Edge (MSEEs) routers at each location.
These physical connections are maintained between
Azure and Megaport. Our Direct API integration withAzure simplifies the ordering, provisioning, and ongoing
management of your ExpressRoute connection.
ExpressRoute takes about a minute to be established.

VXCs can be ordered and provisioned in increments of1 Mbps speeds and scaled in increments of 1 Mbps up tothe port rate selected by you in Microsoft’s portal,
Azure Resource Manager. Using Q-in-Q, which isrequired by Azure, the VXC can be configured for bothAzure Private Peering and Microsoft public peering.
This creates the Layer 2 ExpressRoute and then youpeer directly with Azure at Layer 3 using BGP. If only asingle Peering is required Megaport can facilitate thiswithout the need for Q-in-Q. Azure also provides an
SLA of 99.9% availability for redundant Express Routeconnections. The redundant peering connections can beestablished on one or two Megaports or MCRs.

How to Order
1. Log into the Azure Resource Manager
2. Select ‘Create a Resource’ from your dashboard.
Select ‘Networking’ and then ‘ExpressRoute’.
3. Enter a name for the ExpressRoute and select‘Megaport’ as the provider.
Fill in the rest of template as required and selectcreate.
4. Several minutes later the ExpressRoute will beconfigured in the Azure Resource Manager and you
will need to copy the Service Key to use within thePortal.
5. Log into the Megaport Portal: portal.megaport.com
6. Establish a Megaport Port or MCR if you are notalready enabled on the Megaport Network.
7.

Click on the Azure icon or select ‘+connections’ andchoose ‘Cloud’ then ‘Azure’. Paste the Service Key
as requested. Follow the steps to create the VXC
which establishes the ExpressRoute to Azure.

To create a secondary connection, select ‘Azure’
again and use the same Service Key.

Megaport InfopaperYou have the control and ability to enable multiple Virtual Cross
Connects to Azure from a single location which provides the scalabilityand agility required in response to evolving business needs.
— Matt Simpson | Head of Cloud, Megaport

FAQs
Are there any Azure port fees associated?
Yes, Azure will charge a month-to-month fee dependent on your port speed selected in the Azure Resource
Manager (ARM). This is charged directly to you.
Are there still data egress charges by Azure when I provision a connection via ExpressRoute instead of thepublic internet?
Yes, but Azure will substantially reduce the egress charges when using an ExpressRoute connection.
How do I establish redundancy between my data centre and Azure?
Azure requires two BGP peering sessions to meet their requirements for 99.9% uptime SLA.
These peering sessions can be over one or two Megaports and MCRs as shown in the diagram below.
Are my bandwidth speeds set?
No. You have the ability to scale between your private data centre and Azure in increments of
1 Mbps up to the speed of the port you choose in the Azure Resource Manager.
Does Azure support public or private ASNs?
Azure supports both private and public ASNs.
Are there special requirements for O365?
Using Q-in-Q, which is required by Azure, the VXC can be configured for both Azure Private Peering and Microsoft
public peering. For information about using ExpressRoute to access Office 365, visit Azure ExpressRoute for Office365. O365 services require Microsoft approval and subscription white-listing before the routes will work within theroute filters.
Does connecting to Azure require me to run Q-in-Q?
If both Private peering and Microsoft peering are required in a single Megaport VXC (Virtual Cross Connect) thenQ-in-Q is required. If your equipment does not support Q-in-Q we have a number of options to help with that.
What are my options if I do not support Q-in-Q on my device?
If your equipment does not support Q-in-Q, you have these options:•If you only need a single peering (Private or Microsoft) you can configure the VXC so that Megaport removes
the Q-in-Q requirement.

•Megaport Cloud Router (MCR), our virtual routing service for Layer 3 connectivity, can handle the Q-in-Qfor you.
For more details and other options, please visit our Documentation Portal or our Configuring Q-in-Q guide.

Megaport Infopaper

Private Peering
Private Peering
Private Peering

Single Azure Connection

Virtual Network

Physical SMF Cross Connect
Customer CPE to Megaport

Virtual Network
Virtual Network

Physical SMF Cross Connect
Physical SMF Cross Connect
Customer CPE to Megaport
Customer CPE to Megaport

Megaport Enabled

Megaport

Primary VXC

Data Centre
Megaport Enabled
Megaport Enabled
Data Centre
Data Centre

Express Route

Megaport
Megaport

Primary VXC
Primary VXC

OnrampExpress RouteExpress RouteOnramp
Onramp

PaaS/ SaaS(Public Facing)PaaS/ SaaS
PaaS/ SaaS
(Public Facing)(Public Facing)Microsoft Peering
Megaport Representation

Microsoft Peering
Microsoft Peering

1 x 1 or 10 Gb Megaport
2 x V XC to Azure Private and/or Microsoft Public using an Express Route on-ramp

Redundant Azure Connection

Private Peering
Private Peering
Private Peering

Primary VXC
Physical SMF Cross Connect
Customer CPE to Megaport

Virtual Network

Primary VXC
Primary VXC

Virtual Network
Virtual Network

Physical SMF Cross Connect
Physical SMF Cross Connect
Customer CPE to Megaport
Customer CPE to Megaport

Megaport Enabled
Data Centre
Megaport Enabled
Megaport EnabledData Centre
Data Centre

Megaport
Megaport
Megaport

Secondary VXC
Secondary VXC
Secondary VXC

Express RouteOnramp
Express RouteExpress RouteOnramp
Onramp

PaaS/ SaaS
(Public Facing)
PaaS/ SaaS
PaaS/ SaaS
(Public Facing)(Public Facing)Microsoft Peering

Megaport Representation
1 x 1 or 10 Gb Megaport
2 x V XC to Azure Private and/or Microsoft Public using one Express Route on-ramp and one service key

Microsoft Peering
Microsoft Peering

Fully Redundant Azure Connection
Physical SMF Cross Connect
Customer CPE to Megaport
Physical SMF Cross Connect
Physical SMF Cross Connect
Customer CPE to Megaport
Customer CPE to Megaport

Megaport Enabled
Data Centre
Megaport Enabled
Megaport Enabled
Data Centre
Data Centre

Private Peering
Private Peering
Private Peering

Primary VXC

Virtual Network

Primary VXC
Primary VXC

Secondary VXC
Secondary VXC
Secondary VXC

Virtual Network
Virtual Network
Express RouteOnramp
Express RouteExpress RouteOnrampOnramp

Megaport Enabled
Data Centre
Megaport Enabled
Megaport Enabled
Data Centre
Data Centre
Megaport Representation
2 x 1 or 10 Gb Megaport
2 x V XC to Azure Private and/or Microsoft Public using one Express Route on-ramp and one service key

Microsoft Peering
Microsoft Peering
Microsoft PeeringPaaS/ SaaS
(Public Facing)
PaaS/ SaaS
PaaS/ SaaS
(Public Facing)(Public Facing)

MCR Solution: Azure Cloud to other Clouds

Megaport Representation
1x 10 Gps Megaport Cloud Router (MCR)
2x 10 Gps VXCs from Clouds to MCR

Availability
Enabled ExpressRoute
Locations for National
Clouds (GovCloud)North America

CanadaAsia-PacificWashington

TorontoAucklandAtlanta

Montreal

PerthBoston

Vancouver

Melbourne

ChicagoDallasQuebec City

SydneyDallasNew YorkEurope

Canberra

SeattleChicagoLondonSingapore

Washington

HoustonAmsterdamHong Kong

San Antonio

Los Angeles

Frankfurt

Silicon ValleyDublin

Tokyo
Osaka

SeattleStockholm

Middle East

Las Vegas

Paris

Dubai

PortlandGenevaDenver

Oslo

Columbus

ZurichMiami

Stavanger

Minneapolis
San Antonio

Further Reading
Visit our Documentation Portal for more information on Azure connectivity.

Megaport Infopaper

Why Megaport?

Scalable Bandwidth

Multiple Cloud Regions

Select from 50Mbps, 100Mbps,200Mbps, 500Mbps, 1Gbps, 2Gbps,5Gbps, 10 Gbps

Connect to multiple regions from asingle interconnection point. Thismeans you can leverage multi-region
redundancy at a fraction of the cost.

Real-Time Provisioning
Provision connections in under
59 seconds once you’re on theMegaport network.

Private Connectivity

Rich Ecosystem

Access secure, private connectivity
throughout our redundant network
infrastructure. Your traffic will
not transit the public internet.

Access an ecosystem of global service
providers on our neutral, inclusive
marketplace using a single interface.

Reimagine Connectivity.
Megaport is the highly scaled Network as a Service (NaaS) organisation utilising 100 Gbps technology to deliver dedicatedaccess to cloud services. Megaport’s Software Defined Network (SDN) enables the interconnection of enterprises andservice providers across hundreds of data centre locations around the globe. Fast, flexible, and dynamic, Megaport’s
connectivity solution is transforming the way businesses reach leading cloud services from Microsoft, Google, Oracle,
Amazon Web Services, Nutanix, IBM, Salesforce, Rackspace, Cloudflare, OVHcloud and Alibaba.

megaport.com

Phone: +61 7 3088 5999

Level 3, 825 Ann St,

info@megaport.com

Fax: +61 7 3088 5998

Fortitude Valley, 4006, AU.

E megaportnetworks

C @megaport

D @megaportnetwork

ABN: 46 607 301 959