Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw
Seen 9 Jul 2025late June 2025 → December 2025
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, with source markup removed
Updated July 9, 2025: We have updated the timeline below. Thank you for your patience. At Microsoft Defender for Office 365, we are committed to providing seamless and efficient SOC workflows. One of the key areas of feedback from our users has been the latency experienced when loading certain pages within the Defender portal. To address this, our engineering team is undertaking a long-term investment initiative aimed at significantly improving page load times. When this will happen: Phase 1 | General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by December 2025 (previously late June). How this will affect your organization: Key areas of focus To enhance page load performance, we are focusing on several strategic improvements, including: Identifying areas for performance optimization: Conducting in-depth analysis to pinpoint specific bottlenecks in page load times, including network latency, backend processing delays, and inefficient data retrieval mechanisms. Refining page design and structure: Optimizing UI/UX elements, streamlining heavy components, and implementing efficient rendering techniques to ensure smoother and faster loading experiences. Developing shared modules: Building reusable components that multiple pages can leverage, reducing redundant processing and improving overall efficiency in data fetching, rendering, and caching mechanisms. Enhancing data processing and retrieval mechanisms: Optimizing database queries, API calls, and caching strategies to reduce the time required to fetch and display data on key pages. Implementing progressive improvements: Rolling out optimizations in a phased manner, starting with high-impact areas while continuously monitoring and fine-tuning performance based on real-time feedback. Phase 1: Experiences targeted for improvement In Phase 1 of this project, we are prioritizing enhancements for these experiences: Submission Quarantine Threat Explorer Email Entity Policy Configuration Improvements will be introduced incrementally in a staged manner throughout the rollout period, beginning with the Submission page in late March 2025. After Phase 1, our teams will be continuously monitoring the latencies and investing in further improvements to ensure seamless security operations experience to end users. Impact on users There will be no disruptions or downtimes during the rollout. User workflows will remain unaffected while the enhancements are implemented. This change will be available by default. What you need to do to prepare: This migration will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.
What changed
Between archive captures, newest first
TagsFeature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact
Updated July 9, 2025: We have updated the timeline below. Thank you for your patience. At Microsoft Defender for Office 365, we are committed to providing seamless … will begin rolling out late March 2025 and expect to complete by December 2025 (previously late June 2025.June). How this will affect your organization: Key areas of focus To enhance …
· first version seen
Linked documentation
Microsoft pages the notice links to
The notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you
Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.