Hello and welcome back to Cyber Aires. Microsoft Azure Administrator A Z 103 course. I'm your instructor, Will Carlson. And this is Episode 40 to express routes.
In today's episode, we're going to talk about and understand what express routes really are
what the benefits of express routes are. And we're gonna talk about one additional interesting architecture standpoint that we can take when using express routes. In addition to a site to site VPN
to get started, we're gonna do something a little different than normal here. We're gonna go ahead and jump into the Internet instead of portal directly.
We're gonna jump into the documentation here provided by Microsoft for express route, but for a number of reasons, primarily because I think this is really a great graphic. And there's not a whole lot of information about express routes in portal versus some of the other functionality. There is a whole lot of extensive documentation and doors tool tips for screenshots, more text
for the functionality. But
I find that there's a lot more information here about express routes, then in the portal itself and
what is an express around right? So express run is going to be a service that you ultimately purchase from another vendor that connects you into the Microsoft environment directly. So these were gonna be connections
direct from Microsoft to you, not over the public Internet.
So we can see here from this graphic that here is our network here, and it's gonna connect to our partner edge. And this could be a whole host of providers from A T and T to co logics. Toe will look through the list of them when we get into portal. But there really are a number of them available to you, depending on where you are at
and this is going to be a relatively close connection,
so you'll connect into the partner network and this partner is going to be connected ultimately into data center facilities where Microsoft's backbone network or where azure data centers are ultimately located. And these air gonna be redundant connections, which is another benefit here of express routes.
It's gonna be redundant. Layer three connectivity
into the Microsoft edge, and that's gonna get you really low latent. See really high quality connections all the way into both your virtual networks that are running in azure. Your other service is running an azure and into the office 3 65 and dynamics environments as well. So if
low latent see and high bandwidth
or security of not writing over the public Internet are major concerns for your organization, express route circuits are a really wonderful way to help solve a number of those problems.
Another benefit here, in addition to the redundant connections available via express routes are really gonna be enabled and enhanced by the fact that these air routed using B G p.
So as changes happen or occur in those routes, there is nothing needed to be done by you because B. G. P is going to handle any of those changes and communicate them to your edge device and your partner's edge device as well.
Now we're gonna go ahead and jump here into portal and see how it would go about provisioning and express around circuit. I'm gonna go ahead and select, create resource, and you probably guessed it. We're gonna search for express route, and we're gonna create an express around here.
I'm gonna go ahead and name this express route, and then we see our list of providers here and as I mentioned this list of providers is really quite extensive,
and which provider you pick is going to depend on what locations are ultimately available to you to peer with. So let's go down here to the bottom just for fun and select ZEO Group, and I can see here the locations that ZEO group allows peering with the azure environment.
I could also come down here and let's try xao and see what our options are there.
And I can see that Dallas is the location also like that one, because Dallas is relatively close to me, and then I can go ahead and select the band. With that, I would liketo have. Clearly the more bandwidth we select, the greater the cost of the express route.
I have some options here as to the skew that I choose, and we can see that the premium skew just provides access to more routes through between myself and azure for 1000 of them to be accurate, and that will allow me to connect into 10 virtual networks and global connectivity as well.
We also have a couple of options here for billing model
and all inbound traffic is going to be unlimited. It's the outbound traffic that's goingto either be unlimited or metered. And obviously there's an impact here on cost. A meter connection is going to be more affordable than an unlimited connection.
Allow classic operations is gonna be a check box that will need to select if we plan on using this express route circuit to interact with any classic deployment model. Resource is,
for the most part, you likely will not need to select that. And then we simply select the subscription that we want to use the resource group we like to tie it to and then our location that we're peering with and we would select create now one thing to keep in mind, and it's mentioned here in the footnote
building will start immediately as soon as you create this resource. That does not mean that it's set up completely. That does not mean that you have all the information configured for your network to communicate over the peer network to Azure, but billing will start immediately, so it's well advised to go ahead and
step through this process and figure out what provider it is that you're going to be using to Pierre
or express route back to azure. Get that ball rolling and then once you're ready to go, then provisioned the express route surrogate here in the portal.
In this episode, we explained that an express around circuit is a way to provide a really low, latent, see high quality bandwidth connection that's redundant and dynamic between myself and ultimately, the azure environment, by contracting with appear provider.
We also talked about how that can increase your network redundancy because of that dynamic flexibility and redundancy in that network connection.
And at this point, I want to talk real briefly about an interesting way. You could use express route instead of just having express route Only. You could also go in and set up a site to site B, P and over the public Internet to further increase your redundancy between the express route and your location. So
using express right really does provide you a lot of interesting options for
increasing your redundancy, blowing your Leighton see and providing a high quality connection back to the azure environment, but not only to azure but also to office 3 65 and dynamics as well express right could be a really powerful tool for organizations that need that type of connectivity
coming up next. We've talked a lot about how we allow and prevent certain traffic and how we get there faster. But we haven't talked any about routing here in Azure, so it's high time that we begin the routing discussion. Thanks so much for joining me today, and I'm looking forward to the routing episode.