check before: 2023-12-26
Product:
Outlook, Teams
Platform:
Online, Web, World tenant
Status:
Change type:
Admin impact, Updated message, User impact
Links:
Details:
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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2023-12-12
updated:
2024-10-08
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
Microsoft Teams users on Chrome may experience daily sign-ins and functionality issues due to Chrome's new "privacy sandboxing" feature, but these disruptions can be minimized by adjusting Chrome settings or using the Teams desktop app.
Direct effects for Operations**
Daily Sign-In Requirement
Users may be required to sign in to Teams every 24 hours when using Chrome, leading to potential disruptions in workflow.
- roles: End Users, IT Support
- references: https://privacysandbox.com/news/privacy-sandbox-update/, https://chromeenterprise.google/policies/#BlockThirdPartyCookies
Limited Functionality of Teams Web App
Embedded experiences and certain functionalities in the Teams web app may not work, affecting user productivity.
- roles: End Users, Project Managers
- references: https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline, https://chromeenterprise.google/policies/#CookiesAllowedForUrls
Impact on Teams Integration with Other Apps
Integration features like 'Share to Teams' in Outlook and Dynamics 365 may be affected, leading to communication delays.
- roles: End Users, Sales Teams
- references: https://privacysandbox.com/news/privacy-sandbox-update/, https://chromeenterprise.google/policies/#BlockThirdPartyCookies
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-10-08 | MC Messages | Updated January 12, 2024: We have updated the content with additional information.
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. | 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. |
| 2024-10-08 | MC Last Updated | 01/13/2024 00:15:11 | 2024-10-07T18:45:36Z |
| 2024-10-08 | MC 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 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23BlockThirdPartyCookies&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892135422%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GfrNId4GotixSvxS7bZM3FQwU2C3jfmgY8rAXc3ADvA%3D&reserved=0 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23CookiesAllowedForUrls&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892145494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NqAmxM4z%2Fl3NbvSfqzBX2aZC7uQ3eOkFLw%2BmTezJh%2Fk%3D&reserved=0 https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline | 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 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23BlockThirdPartyCookies&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892135422%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GfrNId4GotixSvxS7bZM3FQwU2C3jfmgY8rAXc3ADvA%3D&reserved=0 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23CookiesAllowedForUrls&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892145494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NqAmxM4z%2Fl3NbvSfqzBX2aZC7uQ3eOkFLw%2BmTezJh%2Fk%3D&reserved=0 https://privacysandbox.com/news/privacy-sandbox-update/ https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline |
| 2024-10-08 | MC 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. | |
| 2024-01-13 | MC Messages | 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. | Updated January 12, 2024: We have updated the content with additional information.
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. |
| 2024-01-13 | MC Title | Affected Teams behavior in Chrome due to privacy sandboxing | (Updated) Affected Teams behavior in Chrome due to privacy sandboxing |
| 2024-01-13 | MC Last Updated | 12/12/2023 01:16:20 | 2024-01-13T00:15:11Z |
| 2024-01-13 | MC MessageTagNames | User impact, Admin impact | Updated message, User impact, Admin impact |
| 2024-01-13 | MC 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. https://chromeenterprise.google/policies/#BlockThirdPartyCookies https://chromeenterprise.google/policies/#CookiesAllowedForUrls https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline | 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 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23BlockThirdPartyCookies&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892135422%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GfrNId4GotixSvxS7bZM3FQwU2C3jfmgY8rAXc3ADvA%3D&reserved=0 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromeenterprise.google%2Fpolicies%2F%23CookiesAllowedForUrls&data=05%7C02%7Cnigolc%40microsoft.com%7Caa58d9ba206349067f9308dbf70a3946%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638375397892145494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NqAmxM4z%2Fl3NbvSfqzBX2aZC7uQ3eOkFLw%2BmTezJh%2Fk%3D&reserved=0 https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline |
Last updated 7 months ago
