MC910981 - Microsoft Teams: Microsoft Edge links on MacOS will seamlessly open

Updated December 30, 2024:February 20, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon for Microsoft Teams: When users or admins configure Microsoft Edge as the browser to open web links in Teams, then links in Teams chat will be open in Edge, and Edge launches in the profile that matches the authenticated profile. Users will benefit from a seamless browsing experience that integrates their identity and user data across Microsoft apps.&

This message is associated with Microsoft 365 Roadmap ID 414521.

When this will happen:

General Availability (Worldwide): We will begin rolling out late October 2024 and expect to complete by late JanuaryFebruary 2025 (previously late November)January).

How this will affect your organization:

Before this rollout, users are asked to reauthenticate links in the browser, which slows down users.

By default, there are no changes.

By default, the feature will be on with setting System default browser and Teams links will open in the system's default browser. System default browser refers to the default browser specified on the user's Mac device.

Admins can control the settings and availability of this feature (and override user settings) by policy in the Microsoft 365 Apps admin center:

• If this policy is enabled, admins can go to Choose which browser opens web links and select Microsoft Edge.
• If this policy is disabled or not configured, web links will open in the system default browser.

How admins update the policy in the Microsoft 365 Apps admin center:

After admins configure the policy to open links with Edge in Teams, this banner displays to users:

How users update the browser settings in Teams:

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins and users about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.