Azure ExpressRoute Direct in a nutshell

Related video mentioned on ExpressRoute Microsoft Peering: • Is the Microsoft Peeri...
Related video mentioned on ExpressRoute ExpressRoute FastPath: • Azure ExpressRoute Fas...
docs.microsoft.com/en-us/azur...
docs.microsoft.com/en-us/azur...
github.com/adstuart/azure-exp...
azure.microsoft.com/en-gb/pri...
00:00 Introduction
00:47 ExpressRoute components, Partner vs Direct
03:13 Context and PoP availability
05:00 Use case #1 - Bandwidth
05:39 Use case #2 - Security/MacSec
07:00 Use case #3 - Agility and circuit provisioning
07:59 Use case #4 - Commercial simplicity
09:22 Use case #5 - Operational simplicity
09:43 Use case #6 - Financial benefits of combining ER Direct with ER Local SKU
11:00 Use case #7 - ExpressRoute FastPath preview feature considerations
11:24 More detail on the provisioning process
14:54 Conclusion

[@besalmon3517]

Brilliant

[@sudheerbhat9024]

This is nice, concise information around ER Direct. Do we still need ER Gateways for ER Direct setup? I see that the provisioning workflow doesn't have a step for that (or is it prerequisite?).

[@laughtonsm]

Great content! I’m looking to provision ER Direct using two different providers from two different colo’s. How many ‘ports’ would I provision to generate the LoA’s?

[@AdamStuart1]

Two physical ports per ER Direct resource. One ER Direct resource per PoP/Colo, One LoA per ER Direct resource.

[@laughtonsm]

@@AdamStuart1 thanks for the prompt reply 👍🏼 Would this be the same with two different providers per colo. e.g. provider A and B in both colo1 and colo2?

[@AdamStuart1]

@@laughtonsm With ExpressRoute Direct, you do not use a provider, you connect your equipment directly to Microsoft routers. The only provider you talk to, is the one that owns the building/colo, to organise cross-connects

[@laughtonsm]

@@AdamStuart1 thanks. That’s great. Sorry for 20 questions, but would I also need to double these up for multiple regions e.g. uk west and uk south?