Share via

Microsoft team sdwan

Handian Sudianto 7,241 Reputation points
2025-10-06T06:17:14.3433333+00:00

Anyone here using sdwan to steering traffic to microsoft teams?

Currently I'm configure the fortigate sdwan for microsoft teams by monitoring to the teams.microsoft.com with parameter below :

Larency : <=100ms

Jitter : <=8ms

Packet Loss : <=3%

Check Interval : 1000ms

Failure before inactive : 5

Restore link after : 5

With above configuration sometime we facing poor performance even all above parameter is in good condition.

If we monitor to the teams.microsoft.com this will represent connection to whole of microsoft team ?

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments No comments

Answer accepted by question author

Steven-N 25,305 Reputation points Microsoft External Staff Moderator
2025-10-06T07:30:32.1533333+00:00

Hi Handian Sudianto

Thanks for reaching out to Microsoft Q&A forum

Based on your description, I understand that you're using FortiGate SD-WAN to steer traffic to Microsoft Teams by monitoring teams.microsoft.com with specific SLA parameters (latency ≤100ms, jitter ≤8ms, packet loss ≤3%,..). Despite these metrics being within acceptable thresholds, you're still experiencing inconsistent performance.

As far as I know, monitoring only teams.microsoft.com does not represent the full connection to Microsoft Teams. While it's a key domain for the main web interface and some signaling, Teams relies on a broader set of endpoints across Microsoft 365 services for full functionality. This includes subdomains like .teams.microsoft.com, as well as other domains for media, collaboration, and backend services. Real-time audio/video/screen sharing (the most performance-sensitive parts) often route through dedicated media relay IP ranges (e.g., 52.112.0.0/14, 52.122.0.0/15, and IPv6 equivalents) on UDP ports 3478–3481, which aren't covered by probing a single HTTP/HTTPS endpoint like teams.microsoft.com.

Additionally, if your SLA probe (likely an HTTP GET or ping) shows good metrics but users still experience poor performance, it's possible the probe isn't capturing issues on alternate paths used for media or other traffic. Different components can route to distinct Azure regions or front doors, where latency, jitter, or loss might vary. Microsoft categorizes these endpoints into Optimize (for real-time media), Allow (for core functionality), and Default (for supporting services), and recommends optimize networks accordingly for SD-WAN.

Link references:

https://learn.microsoft.com/en-us/microsoftteams/prepare-network

https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide

Based on my personal experience and Microsoft’s official documentation, I’ve shared all the information I currently have. However, as a forum moderator, I regret to inform you that I’m unable to provide a definitive solution to this issue due to limitations in resource access and testing environment.

Therefore, I kindly suggest that you seek further assistance directly from Microsoft Support via the following link: https://serviceshub.microsoft.com/supportforbusiness

I sincerely apologize if this redirection causes any inconvenience, but at this point, it seems to be the most viable way for you to receive the support needed for this issue.

Thank you very much for your understanding. If there’s anything else I can assist you with, please feel free to leave a comment and I’ll do my best to help.


Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.