check before: 2023-12-26
Product:
Outlook, Teams
Platform:
Online, Web, World tenant
Status:
Change type:
Admin impact, Updated message, User impact
Links:
Details:
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.
Change Category:
XXXXXXX ...
Scope:
XXXXXXX ...
Release Phase:
Created:
2023-12-12
updated:
2024-08-10
Task Type
XXXXXXX ...
Docu to Check
XXXXXXX ...
MS How does it affect me
XXXXXXX ...
MS Preperations
XXXXXXX ...
MS Urgency
XXXXXXX ...
MS workload name
XXXXXXX ...
Direct effects for Operations**
- Impact on IT Operations
- Increased support tickets and user inquiries related to Teams functionality in Chrome.
- Roles impacted: IT Support Staff, Helpdesk Technicians
- Potential need for additional training sessions for users on how to navigate the new Teams web app experience.
- Roles impacted: IT Trainers, Team Leaders
- Monitoring and adjustments to security policies regarding third-party cookies may be required to ensure compliance and functionality.
- Roles impacted: IT Security Administrators, Compliance Officers
- Impact on IT Services
- Disruption of embedded experiences in Teams, leading to decreased productivity for users relying on these features.
- Roles impacted: End Users, Project Managers
- Changes in the integration of Teams with Outlook and Dynamics 365, which may affect workflows and communication.
- Roles impacted: Business Analysts, Sales Teams
- Requirement for users to switch to the Teams desktop app may lead to inconsistencies in user experience across the organization.
- Roles impacted: All Teams Users, IT Administrators
- Impact on IT Users
- Frequent sign-in prompts every 24 hours may frustrate users and lead to decreased engagement with Teams.
- Roles impacted: All Teams Users, Remote Workers
- Users unable to access the Teams desktop app may experience significant disruptions in their daily tasks.
- Roles impacted: Field Employees, Customer Service Representatives
- Limited functionality in the Teams web app could hinder collaboration and communication efforts.
- Roles impacted: Team Members, Project Collaborators
References:
- [Privacy Sandbox Timeline](https://privacysandbox.com/open-web/the-privacy-sandbox-timeline)
- [Chrome Enterprise Policies](https://chromeenterprise.google/policies/BlockThirdPartyCookies)
- [Microsoft Teams Documentation](https://docs.microsoft.com/en-us/microsoftteams/)
Opportunities**
XXXXXXX ...
Potentional Risks**
XXXXXXX ...
** AI generated content. This information is not reliable.
the free basic plan is required to see all 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-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 1 month ago
