This is especially true for applications that use any web platform or technology that relies on cross-domain cookie sharing, such as apps that are embedded in other apps.Ĭhrome versions 78 and 79 betas have an improvement that delays the SameSite:Lax attribute enforcement for two minutes. We expect that problems similar to the problems that this article describes will affect your applications. You should thoroughly test all applications by using Chrome Beta version 80 to verify the effect of this change. Check the ' Recommendations' section for some server products that will require updating by customers. If you cannot review permissions when you try to activate a Microsoft Learn sandbox, clear browsing data by navigating to chrome://settings/clearBrowserData.Īll Microsoft Cloud services are updated to comply with the new requirements made by Chrome, but some other applications may still be affected. However, it's equally important that you test your own applications against this change in Chrome behavior and prepare your own websites and web applications as necessary.

This article discusses the guidance from both Microsoft and Google for installing the various updates that are required for products and libraries, and the guidance for testing and preparation. Microsoft is committed to addressing this change in behavior in its products and services before the Chrome 80 release date. For more information, see the ' Recommendations' section. This includes Microsoft cloud services.Įnterprise customers are encouraged to make sure that they're prepared for the change and are ready to implement mitigations by testing their applications (whether custom-developed or purchased). Although the change is intended to discourage malicious cookie tracking and protect web applications, it's also expected to affect many applications and services that are based on open standards. The Stable release of the Google Chrome web browser (build 80, scheduled for release on February 4, 2020) will roll out a change to the default cookie behavior starting the week of February 17. The feature will be enabled on a graduated schedule starting February 17. Chrome 80 will ship on February 4 and have this feature disabled by default. Google is scheduled to release a cookie behavior in Chrome Stable version 80.Ĭhrome has updated their rollout timeline to indicate that this change will be rolled out in Chrome 80 starting the week of February 17. Previously, this article referenced Google Chrome Beta version 79.

How to revert google chrome update