Microsoft 365 Roadmap ID: 490055
IT administrators will soon be able to run silent test calls in Microsoft Teams to proactively check network readiness and detect potential issues before they affect users. This feature requires a Teams Premium license and applies to Teams for Windows and Mac desktops.
✅ What’s Coming:
IT administrators will soon have the ability to run silent, synthetic Microsoft Teams call simulations to specific subnets. This will enable proactive network readiness checks and allow for the early detection of issues before they impact users.
This feature will help ensure high-quality, seamless communication experiences across the organization.
Important Requirements:
- Requires a Teams Premium license on the user’s devices.
- Available for Teams on Windows desktop and Mac desktop clients.
📅 Rollout Timeline:
- Targeted Release:
Rollout begins mid-July 2025, expected to complete by late July 2025. - General Availability (Worldwide):
Rollout begins mid-August 2025, expected to complete by late August 2025.
🚀 How This Will Affect Your Organization:
- Silent test calls offer proactive monitoring, allowing IT teams to detect and address network issues before they impact end users.
- Integrating silent test calls into your operational routines can improve network reliability and user experience.
How the Silent Test Calls Work:
- Tests run silently in the background on the Teams client at scheduled times.
- Each test runs for 60 seconds.
- Tests can be targeted to specific subnets.
- Tests will only run on desktop clients (Windows and Mac).
- Tests will only run if the device is idle (the user is not in an active Teams call).
- No disruption to the user:
There are no notifications, sounds, or visible changes during the test. - This feature will be available by default for IT admins to configure.
🔧 What You Need to Do to Prepare:
- This rollout will happen automatically by the specified dates; no admin action is required before rollout.
- Consider:
- Reviewing your current configuration to understand how this may impact your environment.
- Notifying your IT teams and users about this change.
- Updating internal processes or documentation if you plan to integrate silent testing into your monitoring strategy.




