Connecting PaaS to Express Route

%3CLINGO-SUB%20id%3D%22lingo-sub-102654%22%20slang%3D%22en-US%22%3EConnecting%20PaaS%20to%20Express%20Route%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-102654%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20been%20going%20around%20the%20merry-go%20round%20reading%20anything%20to%20do%20with%20express%20routes%20to%20try%20and%20find%20out%20the%20following.%20If%20I%20have%20a%20Azure%20PaaS%20solution%20(OMS%5CVault%20etc%20etc)%20not%20o365%20how%20can%20force%20these%20services%20traffic%20down%20the%20express%20route%20circuit%2C%20or%20is%20this%20only%20possible%20with%20express%20route%20could%20I%20use%20a%20IPSEC%20tunnel%20(not%20for%20production%20)%20to%20do%20the%20same%20thing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-102654%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-103155%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20PaaS%20to%20Express%20Route%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-103155%22%20slang%3D%22en-US%22%3E%3CP%3ETake%20a%20look%20at%20the%20different%20peering%20options%20for%20ExpressRoute%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fexpressroute%2Fexpressroute-circuit-peerings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fexpressroute%2Fexpressroute-circuit-peerings%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-102970%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20PaaS%20to%20Express%20Route%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-102970%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20an%20express%20route%20tunnel%20is%20a%20route%20between%20you%20ISP%20and%20Microsofts%20Datacenter%20target.%3C%2FP%3E%3CP%3EThe%20Expresss%20route%20only%20accepts%20the%20public%20ip%20assigned%20by%20your%20ISP%2C%20this%20allows%20Microsoft%20to%20insure%20all%20traffic%20to%20your%20IP%20is%20routed%20through%20the%20Express%20route%2C%20this%20covers%20all%20services.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hav%20not%20used%20express%20route%20my%20self%2C%20but%20have%20a%20look%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fexpressroute%2Fexpressroute-introduction%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fexpressroute%2Fexpressroute-introduction%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

 

I've been going around the merry-go round reading anything to do with express routes to try and find out the following. If I have a Azure PaaS solution (OMS\Vault etc etc) not o365 how can force these services traffic down the express route circuit, or is this only possible with express route could I use a IPSEC tunnel (not for production ) to do the same thing?

2 Replies

Hi an express route tunnel is a route between you ISP and Microsofts Datacenter target.

The Expresss route only accepts the public ip assigned by your ISP, this allows Microsoft to insure all traffic to your IP is routed through the Express route, this covers all services.

 

I hav not used express route my self, but have a look here https://docs.microsoft.com/en-us/azure/expressroute/expressroute-introduction

Take a look at the different peering options for ExpressRoute:

 

https://docs.microsoft.com/en-us/azure/expressroute/expressroute-circuit-peerings