Services
Summary
Chrome's rollout of privacy sandboxing will affect Teams experiences, with an updated notice that users can opt-in for this feature. Teams on Chrome may require daily sign-in and have limited functionality. The Teams desktop client is recommended, and administrators can use specific Chrome policies to mitigate impact.
Details
Updated September 30, 2024: Chrome will no longer be rolling out this change to general availability. Users will instead be able to choose whether they would like to enable privacy sandboxing. Read more about their update here: A new path for Privacy Sandbox on the web. Our recommendations below still apply if your users are using privacy sandboxing in Chrome. Thank you for your patience.
Starting in January, Chrome will begin gradually rolling out privacy sandboxing in the web to 1% of their users, with general rollout happening in late 2024. This will impact some Teams experiences in Chrome. The recommendation is to use the Teams desktop client if you are part of the rollout cohort.
When this will happen:
Starting in January 2024 and continuing through the remainder of 2024.
How this will affect your organization:
Teams users who are using Google Chrome with this recent change will start seeing the following experiences:
- The new Teams web app will display a banner and require users to click it every 24 hours to remain signed in. This will impact users in your organization who can't use the Teams desktop app.
- The new Teams web app may include embedded experiences, such as apps, that no longer work. When this happens, Teams will give users the option of opening the embedded experience in a separate browser tab, or using the Teams desktop app.
- Classic Teams will show options to switch to the new Teams web app, and/or to use the desktop app.
- Other affected experiences include Teams chat in Outlook web app and Dynamics 365. The ‘Share to Teams’ dialog found in Outlook and other web apps or sites is also affected.
What you need to do to prepare:
We are providing this information for your awareness. If your organization accesses Teams in the Chrome browser, some of your users may start being affected by this change. The recommendation is to use to the Teams desktop client.
Enterprise administrators can also use the BlockThirdPartyCookies and CookiesAllowedForUrls policies to ensure their users are not impacted, allowing them time to make necessary changes to not rely on this policy or third-party cookies.
URLs should be allowed for Teams:
- *.microsoft.com
- *.microsoftonline.com
- *.teams.skype.com
- *.teams.microsoft.com
- *.sfbassets.com
- *.skypeforbusiness.com
- *.sharepoint.com
- *.onenote.com