Microsoft Teams: Direct Media Connection cmdlet

Microsoft Teams is introducing a new feature in April 2024 called Direct Media Connection. This feature provides an option for admins to involve a relay or media processor between meetings and 1:1 calls. Admins can set Direct Media Connection as a user-level policy as a tenant default or configure it for specific individuals in their tenant. The rollout will happen automatically without any admin action required before the rollout.

Direct Media Connection is a user-level policy that enables admins to choose whether to involve a relay or media processor between meetings and 1:1 calls. When Direct Media Connection is off, a relay or media processor will transfer the media between participants in meetings and calls. When Direct Media Connection is on, there will be an attempt not to include a relay or media processor between the participants in meetings and calls to provide better media quality and lower bandwidth usage.

The feature is set to roll out in early April 2024 and will be available to all environments. The Teams client will check the Direct Media Connection setting at the call setup stage. If the setting is True, the local IP address will be shared with the peers as a direct connection for better media quality, and if the setting is False, the Teams client media library will not share the local IP address to the peers, which will force the media connection to be established through a relay server or a media processor server.

Admins will implement this feature with PowerShell commands. To learn more about this feature and how to add TeamsMediaConnectivityPolicy cmdlets, you can check the public docs link provided in the post.

The post Microsoft Teams: Direct Media Connection cmdlet originally appeared on M365 Admin.