Services
Affected Platforms
Summary
Microsoft Teams will soon support silent test calls for IT admins to proactively check network readiness by running 60-second, background call simulations on specific subnets for Windows and Mac desktop clients. This requires Teams Premium and will roll out from September to December 2025 with no user disruption.
Details
Updated October 28, 2025: We have updated the timeline. Thank you for your patience.
Coming soon: IT administrators will be able to run silent, synthetic Microsoft Teams call simulations to specific subnets—enabling proactive network readiness checks and early detection of issues before they affect users. This will ensure high-quality, seamless communication experiences across the organization.
This feature requires a Teams Premium license on your user's devices.
This message applies to Teams for Windows desktop and Teams for Mac desktop.
This message is associated with Microsoft 365 Roadmap ID 490055.
When this will happen:
Targeted Release: We will begin rolling out early September 2025 and expect to complete by mid-September 2025
General Availability (Worldwide): We will begin rolling out mid-September 2025 and expect to complete by early December 2025 (previously late September).
How this will affect your organization:
Silent test calls offer proactive monitoring, allowing IT teams to detect and address network issues before they affect users. By integrating silent test calls into your operational routines, you can proactively detect and resolve potential issues.
- Tests run silently in the background on the Teams client at scheduled times.
- A test runs for 60 seconds.
- Tests are targeted at a specific subnet.
- Test will run only on Desktop clients (Windows and Mac).
- Tests only run if the device is idle (user is not in an active Teams call).
- Users experience no disruption: no notifications, sounds, or visible changes.
This feature will be available by default for admins to configure.
What you need to do to prepare:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation.
Before rollout, we will update this post with new documentation.