ExpressRoute for dedicated connections in Azure - Step-by-Step Execution

Process Flow - ExpressRoute for dedicated connections

Start: Request ExpressRoute

↓

Provision Dedicated Circuit

↓

Connect On-Premises Network

↓

Establish Private Connection

↓

Configure Routing & Policies

↓

Use ExpressRoute for Traffic

↓

Monitor & Maintain Connection

↓

End

This flow shows how a dedicated ExpressRoute connection is requested, provisioned, connected, configured, used, and maintained.

Execution Sample

Azure

1. Request ExpressRoute circuit
2. Connect on-premises router
3. Configure BGP routing
4. Send traffic via ExpressRoute
5. Monitor connection health

This sequence shows the main steps to set up and use an ExpressRoute dedicated connection.

Process Table

Step	Action	State Change	Result
1	Request ExpressRoute circuit	Circuit requested in Azure portal	Circuit pending provisioning
2	Provision Dedicated Circuit	Azure provisions circuit with bandwidth	Circuit ready for connection
3	Connect On-Premises Router	Physical connection established	Link up between on-premises and Azure
4	Configure BGP Routing	BGP sessions established	Routes exchanged between networks
5	Send Traffic via ExpressRoute	Traffic flows over private link	Lower latency and secure connection
6	Monitor Connection Health	Alerts and metrics active	Connection stable and performant
7	End	All steps complete	ExpressRoute dedicated connection operational

💡 All steps completed successfully; dedicated ExpressRoute connection is active and ready for use.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Circuit Status	None	Requested	Provisioned	Connected	Routing Configured	Active	Active
Connection Link	Down	Down	Down	Up	Up	Up	Up
Traffic Flow	None	None	None	None	None	Flowing	Flowing

Key Moments - 3 Insights

Why does the circuit status remain 'Requested' after step 1 and not immediately 'Active'?

Because after requesting, Azure needs time to provision the physical circuit before it becomes active, as shown in execution_table step 2.

What happens if BGP routing is not configured after the physical connection is up?

Traffic cannot flow properly because routes are not exchanged; execution_table step 4 shows routing configuration is essential before traffic flows.

Why is monitoring important after the connection is active?

Monitoring ensures the connection stays healthy and performs well, catching issues early as shown in execution_table step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the circuit status after step 3?

A Requested

B Connected

C Provisioned

D Active

💡 Hint

Check the 'Circuit Status' variable in variable_tracker after Step 3.

At which step does traffic start flowing over ExpressRoute?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Refer to execution_table row where 'Traffic flows over private link' is noted.

If the physical connection link stays 'Down' after step 3, what is the likely impact?

A No traffic will flow over ExpressRoute

B Circuit status will be 'Active'

C Traffic will flow normally

D BGP routing will be established

💡 Hint

Look at variable_tracker for 'Connection Link' status and its effect on 'Traffic Flow'.

Concept Snapshot

ExpressRoute provides a private, dedicated connection between your on-premises network and Azure.
Steps: Request circuit → Provision → Connect router → Configure BGP → Send traffic → Monitor.
Benefits: Lower latency, higher security, reliable bandwidth.
Requires physical connection and routing setup before use.

Full Transcript

ExpressRoute for dedicated connections involves requesting a private circuit from Azure, provisioning it, physically connecting your on-premises network, configuring routing protocols like BGP, sending traffic securely over the private link, and monitoring the connection to ensure stability and performance. Each step changes the state of the circuit and connection link, progressing from requested to active. Traffic only flows after routing is configured and the physical link is up. Monitoring helps maintain connection health.

Practice

1. What is the main benefit of using Azure ExpressRoute for connecting to Azure services?

easy

A. It enables running virtual machines without any network configuration.

B. It allows free internet access from any location worldwide.

C. It provides a private, dedicated connection that is more secure and reliable than the public internet.

D. It automatically backs up all data to Azure Blob Storage.

Solution

1. Step 1: Understand ExpressRoute purpose

   ExpressRoute creates private connections to Azure, avoiding the public internet.

2. Step 2: Identify benefits of private connection

   Private connections improve security, speed, and reliability compared to public internet.

3. Final Answer:

   It provides a private, dedicated connection that is more secure and reliable than the public internet. -> Option C

4. Quick Check:

   ExpressRoute = private, secure connection [OK]

Hint: ExpressRoute means private, not public, connection [OK]

Common Mistakes:

• Confusing ExpressRoute with VPN or public internet
• Thinking it provides free internet access
• Assuming it automatically backs up data

2. Which of the following is the correct step to create an ExpressRoute circuit in Azure Portal?

easy

A. Go to 'Create a resource' > Networking > ExpressRoute, then fill in provider, location, and bandwidth details.

B. Go to 'Create a resource' > Compute > Virtual Machine, then select ExpressRoute option.

C. Go to 'Create a resource' > Storage > Blob Storage, then enable ExpressRoute.

D. Go to 'Create a resource' > Database > SQL Server, then configure ExpressRoute.

Solution

1. Step 1: Identify correct Azure Portal path

   ExpressRoute circuits are created under Networking resources.

2. Step 2: Confirm required details

   Provider, location, and bandwidth are needed to create the circuit.

3. Final Answer:

   Go to 'Create a resource' > Networking > ExpressRoute, then fill in provider, location, and bandwidth details. -> Option A

4. Quick Check:

   ExpressRoute circuit creation = Networking resource [OK]

Hint: ExpressRoute circuits are under Networking, not Compute or Storage [OK]

Common Mistakes:

• Selecting Compute or Storage instead of Networking
• Skipping provider or bandwidth details
• Confusing ExpressRoute with VM or database setup

3. Given this Azure CLI command snippet to create an ExpressRoute circuit:

az network express-route create --name MyCircuit --resource-group MyGroup --location eastus --bandwidth 200 --provider "Contoso" --peering-location "Silicon Valley" --sku-tier Premium --sku-family Metered

What will be the bandwidth of the created ExpressRoute circuit?

medium

A. 200 Mbps

B. 100 Mbps

C. 500 Mbps

D. 1 Gbps

Solution

1. Step 1: Locate bandwidth parameter in command

   The command includes '--bandwidth 200', which sets bandwidth to 200 Mbps.

2. Step 2: Confirm bandwidth unit

   Azure ExpressRoute bandwidth is specified in Mbps, so 200 means 200 Mbps.

3. Final Answer:

   200 Mbps -> Option A

4. Quick Check:

   Bandwidth parameter = 200 Mbps [OK]

Hint: Look for --bandwidth value in CLI command [OK]

Common Mistakes:

• Confusing bandwidth units (Mbps vs Gbps)
• Ignoring the --bandwidth parameter
• Assuming default bandwidth if not specified

4. You tried to create an ExpressRoute circuit but received an error: "Invalid peering location." What is the most likely cause?

medium

A. The resource group name contains invalid characters.

B. The bandwidth value is too high for the selected tier.

C. The Azure subscription has expired.

D. The peering location specified is not supported by the chosen provider.

Solution

1. Step 1: Understand error message meaning

   "Invalid peering location" means the location is not valid for the provider.

2. Step 2: Check provider and location compatibility

   Each provider supports specific peering locations; mismatch causes this error.

3. Final Answer:

   The peering location specified is not supported by the chosen provider. -> Option D

4. Quick Check:

   Invalid peering location = unsupported location by provider [OK]

Hint: Match peering location exactly with provider's supported list [OK]

Common Mistakes:

• Blaming bandwidth or resource group name
• Ignoring provider-location compatibility
• Assuming subscription status causes this error

5. A company needs a dedicated connection to Azure with high bandwidth and global reach. They want to use ExpressRoute with premium features. Which combination of settings should they choose to meet these requirements?

hard

A. SKU tier: Standard, Bandwidth: 500 Mbps, Peering location: Global

B. SKU tier: Premium, Bandwidth: 1 Gbps, Peering location: Global

C. SKU tier: Premium, Bandwidth: 1 Gbps, Peering location: Regional

D. SKU tier: Standard, Bandwidth: 200 Mbps, Peering location: Regional

Solution

1. Step 1: Identify premium features for global reach

   Premium SKU tier enables global connectivity beyond regional limits.

2. Step 2: Choose high bandwidth and global peering

   1 Gbps bandwidth meets high speed; global peering location supports worldwide access.

3. Final Answer:

   SKU tier: Premium, Bandwidth: 1 Gbps, Peering location: Global -> Option B

4. Quick Check:

   Premium + 1 Gbps + Global = high bandwidth and global reach [OK]

Hint: Premium tier + global peering = worldwide high-speed connection [OK]

Common Mistakes:

• Choosing Standard tier for global reach
• Selecting regional peering for global needs
• Underestimating required bandwidth