Microsoft AZ-700: Design an ExpressRoute Deployment

Reading Time: 2 minutes

Notes from MS Learn AZ-700 Module 3: Design and Implement Azure ExpressRoute – Unit 3: Design an ExpressRoute Deployment

ExpressRoute used to connect on-prem with Azure. Plan decisions prior to deployment of an ExpressRoute Circuit

  • ExpressRoute Circuit SKUs
    • Three SKUs have different charges
      • Local SKU
        • Automatically charged Unlimited Data Plan
      • Standard SKU
        • Select Between Metered or Unlimited Data Plan
          • Ingress are free except when using Global Reach
      • Premium SKU
        • Select Between Metered or Unlimited Data Plan
          • Ingress are free except when using Global Reach
    • Use Azure Pricing Calculator to estimate costs
  • Choose a Peering Location
    • Azure Region
      • Global DCs housing Azure computer/network/storage resources
      • Resource Location determins Azure DC or availability zone created in
    • ExpressRoute Location (Peering Location)
      • May be called Peering Location or Meet-me-location
      • Colo where MS Enterprise Edge (MSEE) devices live
      • Entry point to MS network – globally distributed allowing connectivity to MS network around the world
      • Where ExpressRoute partners and ExpressRoute Direct customers cross-connect to MS network
    • Azure regions to ExpressRoute location in geopolitical region
    • ExpressRoute Connectivity Provider
    • Connectivity through Exchange providers
      • If connectivity provider not listed in above, still able to create connection
      • Several providers already connected to Eth exchanges
    • Connectivity through satellite operators
      • Remote and no fiber
      • Want to explore other options
      • Other options
        • Other service providers
        • DC providers
        • National Research and Education Networks (NERN)
        • System integrators
  • Choose the Right ExpressRoute Circuit and Billing Model
    • MS various Express Route options based on desired bandwidth. Evaluate current usage as a starting point
    • Deterring ExpressRoute based on requirements: keep in mind budge/SLAs
    • Choose appropriate SKU and if applicable Metered vs Unlimited within the SKU
    • Consider ExpressRoute Direct
      • Connects network to closet MS Edge which connects to MS Global Network
      • Usage of Global MS Network charged on top of ExpressRoute Direct
    • Express Route pricing for metered and unlimited bandwidth details
    • Available in range of bandwidths – check with provider for what they support
  • Choose a billing model
    • Unlimited
      • Billing based monthly
      • All Inbound/Outbound included
    • Metered
      • Billing based on monthly fee. Inbound free, Outbound per GB
      • Rates vary by region
    • ExpressRoute Premium add-on
      • Additional Capabilities
        • Increased route limits for Azure public/private peering from 4k to 10k routes
        • Global connectivity for services. Circuit in any region (exclude national clouds) has access to resource in any other region
        • Increased VNet links per ExpressRoute circuit from 10 based on bandwidth
Share this article:

Permanent link to this article: https://www.packetpilot.com/microsoft-az-700-design-an-expressroute-deployment/

Leave a Reply

Your email address will not be published.