Hi there, thanks for joining.
My name is Mahesh Nayak and I'm a
principle program manager in the
Azure networking organization.
In this system today,
I'm going to talk about how you
can optimize connectivity for your
traffic between your resources in
Azure and the clients in the Internet.
To set some context,
we see a significant increase in Internet
traffic globally for all our services.
And that's because our customers are going
through rapid digital transformation
to accelerate their business growth
as well as to empower their employees.
But also another big factor that is
contributing to this huge increase
in Internet traffic is the current
global health situation.
The global health situation has
dramatically changed the consumer behavior.
The way we work, the way we lead,
the way we communicate.
Everything is now transparent,
which is resulting to an incredible
increase in overall Internet traffic.
I'm going to talk about some of the
infrastructure capabilities that is
built an optimized to provide you
optimal Internet connectivity experience.
And also I'm going to talk about
some of the services built in the
platform that counts you more control,
more flexibility so you can optimize
for your Internet.
Traffic, let's start with the infrastructure.
When it comes to Internet facing workload,
the global Age footprint place
agree important part in delivering
seamless connectivity experience
to your cloud resources.
Each put Green Dot eight points of
presence and where we connect our
network to the rest of the Internet.
So this defines our network
boundary traffic from Microsoft to
Internet goes through the Xbox and
also traffic from Internet.
When it comes to Microsoft,
it also comes through the Xbox.
Now from the very beginning we
have adaptive design principle to
place these edge pops closer to
the user so that we can observe
the traffic as soon as possible,
carry them in our own premium
private backbone network all the
way to the hosted service region,
and then the return traffic also
follows the same principle and exits
our network closest to the user so that
you get the premium optimal experience.
Then comes the last mile optimization.
So the last mile is the ISP
network from our base points of
presence to the user in Internet.
To prove it into an optimal experience,
we also need to optimize the last mile.
So this is where Microsoft peering
service comes into picture.
Map service provides a platform
to our ISP partners so that they
can optimize the last mile so
the mutual customers can get end
to end connectivity experience.
It could connectivity experience from
all the way to the user location to
the surface hosted in the data center.
That I'm going to touch on global network.
It's how much you already know.
Microsoft owns and operates one
of the largest and most advanced
private global network in the world.
Microsoft has been consistently
investing for last 25 years.
And has built a network that is
exceptionally highly reliable,
secure and highly available,
and that enables you to connect to any
of the Microsoft cloud services from
anywhere in the world quickly and securely.
Then I'm going to talk about a new
service called Routing Preference.
The service empowers you to choose
the underlying network that will
carry the traffic from Microsoft
to the user or from the user to
the service hosted in Microsoft.
So you have the choice to
optimize for the best performance,
or if you want to choose the network
that is more cost optimized so you have
that choice with routing preference.
Along with the connectivity optimizations
that a number of services that we
have deployed in our edge locations,
for example as your front door Azure CDN,
provide you a number of functionalities
that you can leverage to optimize
your web application.
Functionality such as application
acceleration, SSL offload,
global load balancing with instant
fellow are static content caching
security on the security front,
you have the web application parallel,
which is a layer 7 protection
and protect your application from
attacks such as SQL injection,
cross site scripting.
Another layer 7 attacks so there is a
separate session schedule for this one.
If you are interested to learn
more about these two services at
your front door and Azure CDN,
please join that session.
It is pretty interesting.
Let's dive into Azure Global network.
Our global network is the partition
apart network infrastructure.
The map in this slide outlines
the massive scale of the network.
As you can see,
there are 61 Azure regions and it
will continue to grow and these
regions are globally distributed.
Microsoft Global Network connects
all these regions,
reconnects our data center to
the rest of the Internet via our
age points of presence.
The network spans the globe with
more than 165 thousand fiber
miles and these are high capacity
fiber optics that includes both
traditional agile and subsidy optics.
On the Internet side,
we have more than 180 age pops and
TJ's pops are strategically placed
closest to the user so that we
can observe the traffic as soon as
possible and route them in our own
private Microsoft global network and
you can get the premium experience.
DJ spots are connected to thousands
of Internet service providers
across the world to provide the
last mile experience.
Besides Azure,
this Microsoft Global Network
also powers all of the cloud
services from Microsoft Office 365,
Windows Dynamics Azure,
Active Directory,
Xbox being teams.
All these services are powered by
the same global network that's are being you.
In addition to Microsoft Services,
thousands of enterprise customers
they rely and trust on this global
network to run their mission.
Critical applications and services.
It's a men scent.
We have 180 + 8 points of presence
in teaches.
Pops are strategically placed approaches
to the user so that we can observe
the traffic as soon as possible,
route them on our own Microsoft
Private backbone network all the
way to the hosted service region,
and then the return traffic also
follows the same principle and exits.
Our network closes to the user.
So by observing and delivering the
traffic to the point closest to the user,
we provide premium connectivity
experience in terms of latency,
throughput and mode.
And this is called cold potato routing,
and so once the traffic enters
to Microsoft Network,
it stays on Microsoft Network.
It doesn't flow over the Internet.
And also all communication
between our data centers,
whether within a region or cross region
which stays on our network all the time.
Whether it's a communication between
a personal machine or a storage
account or between Azure and Office
365 or between Office 365 and Xbox,
all the communications between 2
Microsoft IP address always remain
on our Microsoft Global Network.
It doesn't go over the Internet.
Another point to call out here is all
the traffic between our data centers,
whether within a region or across the region.
Is encrypted automatically
at the physical layer,
so your data in transit is
already encrypted by default.
When it comes to cloud,
one size doesn't fit. All.
You have different types of workload.
You have different type of use cases,
so more code requires extremely
high performance or more protein
quests to optimize for cost.
And this is where routing
preference come into picture.
It empowers you,
it empowers you to customize the
underlying network and letting you
choose the network that is optimized
for performance are optimized for cost.
Now you have the choice.
Depending on the use case,
you can choose one over the other.
So in the previous slide we
talked about cold potato routing.
So we have placed our age points
of presence cruises to the user
globally so that we can observe
the traffic as soon as possible,
write them on our own premium
Microsoft Global network all the
way to the hosted service region
and the return traffic follows
the same principle and exits our
network closest to the user.
For example,
if a user in Singapore trying to access
the storage account date in Chicago,
so the traffic enters Microsoft
Network in Singapore itself,
their travels on our own Microsoft
Private network all the way to Chicago,
and the return traffic from Chicago
also travels on Microsoft Mobile Network
from Chicago all the way to Singapore,
then exits in Singapore.
So you can see bunk of the time the
traffic was in our Microsoft mobile
network because it's a premium.
Private global Network were able
to provide you premium quality of
service with cold potato routing,
but we understand you may have some
workload that do not require premium
predictability and premium performance
of the Microsoft over network.
You may need a cost optimized
option for some of your use cases,
and this is where routing
preference keeps your second choice,
so you may choose the underlying
network that is more cost optimized
and in this case it will be ISP
Network instead of Microsoft Global
Network in casing ISP network.
We do hot potato routing.
If I pick the same example,
the user in Singapore trying to
access the storage account in
Chicago with the hot potato routing
the traffic from Singapore will
take the public Internet route.
All the way of coming up to Chicago.
It will enter Microsoft Network in
Chicago and the return path also exists.
Microsoft Network in Chicago takes
the public Internet route all
the way to Singapore.
The difference is you can see
the cold potato routing is using
Microsoft Global Network and the
hot potato routing is ISP Network.
What comments are the hot potato
routing is predominantly dominated
by the ISP network performance and
it is compatible to other cloud
service provider.
Now how to enable routing preference
for infrastructure ages?
Resources such as virtual machine,
virtual machine scale set load balancer.
You can enable through the public IP.
So when you create a public IP you
will see two routing preference
choices there.
By default it will be always
Microsoft Global network,
but you have the option to
change it to the ISP network.
Once you create the public IP
you can attach the public IP
to any of these resources,
for example in virtual machine
Nic or in the load balancer.
Is your content content Internet facing IP?
So based on based on the routing
choice that you have selected.
A tactical do either hot potato cold
put it routing and you can also
enable routing preference for your
storage services such as blogs piles,
Azure Data Lake and the default is
always Microsoft Global network.
It can instrument better with the
support of enabling both routing
choices for your Azure resource.
For example,
for a virtual machine can have a
network interface with two public IPS,
one public IP router via Microsoft
Global Network and the second
public IP router by ISP Network.
You can also have two separate network
interface one network interface.
Is Mac to your Microsoft Public IP
and the second network interface
is mapped to the public IP that
is routed via ISP Network?
You can do the same thing for
the storage account.
So you can optimize performance.
You can optimize for cost.
You can do all those combinations.
I'm going to give you a demo about
how to enable both routing choices
for your Azure resources for a virtual
machine and will also talk about
how to enable for storage account.
In this demo I'm going into two scenarios.
The first one I'm going to enable
routing preference with the ISP
network routing for my storage account,
and that's going to create an additional
endpoint for my storage services.
So now I'm going to have two endpoint,
one that comes by default which is
always routed via Microsoft Network.
And the second one created from routing
preference is routed by ISP Network.
Now I'm going to use both these
endpoints to access a file from my block
container for the second scenario.
I'm going to enable both routing
choices for a virtual machine Salahaddin
Network interface with two public IP address,
one public IP it's routed by Microsoft
Network and the second public IP
is routed by ISP Network.
Let's start with the story scenario.
I'm here in the Azure portal.
So to save some time I have already
created my storage account and
routing preference option is there
in the networking tab.
So as you can see I have already
turned on routing preference.
You can go to properties.
Now you can see that it's a second endpoint
got created because I turned on route
encryptions for my storage services.
So now I have two endpoints I'm
going to access a file from my blob
container using both the endpoints.
Let's go to the container.
So this is the file that I'm going
to access using both the endpoints.
I have a simple HTML file.
As you can see, my estimate Pi has two URLs,
one that is routed by Microsoft
Global Network and the second
one is routed by ISP Network.
Now let me go ahead and load
this HTML file on my browser.
So let me rephrase.
So as you can see, the same
storage service is now accessible
via two separate routing network.
So now you have choices.
You can use the one that
works best for you.
Routing by Microsoft Network
is performance optimized.
And routing by ISP Network is
cost optimized.
Now let's move on to the
virtual machine demo.
Again, to save some time,
I have already created a virtual machine.
I'm in my networking tab.
As you can see, my network
interface has two public IP's. 1.
So this one is using ISP
Network and it could go back.
And click on the other one.
You see the properties.
And this one is using Microsoft Network.
So now I have a virtual machine
which has a network interface and is
associated with two public IP address,
one public IP address is routed by
Microsoft Network and the second public
IP address is routed by the ISP network.
Now I'm going to use these two public IP's to
access a directory from my virtual machine.
So this is my Microsoft Network public IP,
so if I hit on the press.
Start spitting the data from my directory.
And this one is routed by the ISP
network and I'm going to refresh here.
And it's also picking the
data from the directory.
Now, as you can see,
the same virtual machine I can access
using two separate routing network.
You can also enable both routing choices for
your Internet facing load balancer scenarios.
That concludes the demo.
Let's go back to the presentation Maps.
Russia, pretty important
part in your Internet.
First strategy to provide the
enterprise grade Internet connectivity
experience to Microsoft Services.
Earlier we talked about Microsoft
Global Network reliability
availability and how it is designed
and optimized to provide you
consistently high quality of service.
Now to provide end to end
seamless connectivity experience.
We also require optimizes
and in the last mile,
so that's the network from your location
to Microsoft Edge points of presence.
And this little Maps come into picture Maps.
Platform solves that last mile
problem and enables reliable,
high performing connectivity from your
location to the Microsoft Network.
Maps is a collaboration platform and we have
partnered with Internet service providers,
Internet Exchange partners,
STI providers to provide optimized
labl and high performing last mile
connectivity from the customer
location to the Microsoft Network.
To call out some of the
key Maps capabilities,
first it starts with performance.
The service guarantees that
there is only one agent.
How between you and Microsoft Network?
2nd on the reliability.
Front local and Geo redundancy
is built in to provide high
availability in the last mile.
Each Maps partner is required to
have both local and redundancy.
And each building location is provisioned
with redundant and diverse peering links.
Then on the capacity side,
each piering rich to have
high purine capacity to handle
unpredictable demand spikes.
Maps also provides a performance
telemetry platform and the service
collects a number of network
performance metrics such as latency,
jitter, packet loss and other metrics,
and it processed those data at me real
time and aggregates them by First mile,
middle mile, and last mile connectivity.
So from a customer standpoint,
you get network performance insides
for network connectivity all the way
from your location to the Microsoft
Cloud service in the data center.
Additionally, you can also configure to
get notified for performance degradation,
route animales, route, legs and more.
On the security front,
Microsoft has developed an industry leading
route leak detection and mitigation platform,
and we call it as radar.
Radar monitors over 20 million Internet
prefixes at real time every day,
and it protects our network
against out animal.
Easier outlets now map
service also leverages radar,
and it extends the same radar capabilities
to the last mile partner network.
Nothing really matters if you
cannot connect to the cloud.
Maps Impulsar customers with strong
last mile fell over plan for
Internet connectivity when they're
connecting to Microsoft Services.
Now it is mentioned in the previous slide,
each peering location is provisioned with
redundant and diverse peering links.
Also,
providers interconnected multiple Microsoft
Edge locations in different geographies.
So if one of the edge nodes has
degraded performance or in case of
a disaster the traffic route how
Microsoft or two Microsoft had the
alternative sides with the same partner
instead of going over the Internet.
From a customer standpoint,
configuring primary and backup
apps is very straightforward.
Customers can look up for their
Internet provider in Azure Portal
and then they can choose the primary
and backup path for their traffic.
Thank you so much for joining if you
want to learn more about routing,
trans Azure peering service or
other Azure networking services,
please visit our website and there
are plenty of materials there.
Thank you.