You have a Microsoft Teams Phone deployment that uses Direct Routing. The deployment has the following configurations: - Direct Routing Session Border Controller (SBC) public IP subnet…

Question

Options

• A52.112.0.0/14
• B198.51.100.0/24
• C203.0.113.0/24
• D192.168.0.0/24

• A
  3% (2)
• B
  13% (8)
• C
  80% (51)
• D
  5% (3)

Explanation

Option C (203.0.113.0/24) is correct because Trusted IP addresses in Teams represent the external (internet-facing) IP addresses of your corporate network. Teams compares a client's external IP against this list to determine if the user is on-premises, which then triggers location-based emergency call routing policies.

Why the distractors are wrong:

• A (52.112.0.0/14) is a Microsoft-owned IP range used by Teams infrastructure - it's not your network.
• B (198.51.100.0/24) is the SBC's public IP subnet. The SBC handles call routing but is not a Teams client network, so adding it to Trusted IPs doesn't help Teams detect client location.
• D (192.168.0.0/24) is the internal/private IP range. Trusted IPs must be public addresses because Teams determines location by the external IP a client appears to originate from - private RFC1918 addresses are never seen externally.

Memory tip: Think of Trusted IPs as the "front door" of your corporate network - the external IP your clients show to the internet when they leave the building. Internal IPs are behind that door, and the SBC is a separate door for PSTN traffic entirely.

No community discussion yet for this question.