Weekly briefing
Week 31 · 28 Jul – 3 Aug 2025 UTC · assess the changes, then plan the next dates.
Act on2
-
Cisco · 2 security records
CVE-2025-20281
-
[WORKAROUND] Error code 30094-27 when updating Office
Classic Outlook known issues
Coming up6
-
Patch Tuesday, 12 August 2025
The second Tuesday of the month, when Microsoft releases security updates for Windows, Office, and servers.
-
MC1022529: Microsoft Teams: Updated retention policy for meeting attendance reportsMicrosoft 365 Message Center Archive by Merill Fernando
Same day: Message Center action date: MC1041428: Microsoft Viva Glint: Some language codes will retire from translation services; Message Center action date: MC1092458: Microsoft Exchange Online: New Message Trace will be GA; legacy Message Trace will retire
-
Microsoft Office Excel Remote Code Execution Vulnerability
CVE-2007-0671
Same day: CISA KEV deadline: Microsoft Internet Explorer Resource Management Errors Vulnerability
-
MC1002399: Microsoft Purview: Classic eDiscovery experience will retireMicrosoft 365 Message Center Archive by Merill Fernando
Same day: Message Center action date: MC1062447: Microsoft Fabric: Changes to tenant admin setting that governs the access of service principals to public APIs; Message Center action date: MC1066336: Plan for Change: Updates to required permissions for Microsoft Graph Beta API deviceManagement; Message Center action date: MC1107490: Reminder: Updates to required permissions for Microsoft Graph Beta API deviceManagement; Message Center action date: MC1119406: New Outlook for Windows and Web: Outlook Newsletters – General Availability begins for Targeted Release
Changed1
-
MC922623: Microsoft new Outlook for Windows and Outlook for the web: Changing how to disable/enableMicrosoft 365 Message Center Archive by Merill Fernando
Exchange Online, Microsoft 365 for the web, Microsoft 365 apps
How this list is chosen
Changes from 28 Jul 2025 – 3 Aug 2025 UTC and dates due up to 2 Sep 2025. Dates are the source's own, or labelled as the day ChangeIntel observed a change; never inferred effective dates.
Ranked by kind: exploited vulnerabilities, then up to 7 dates, open known issues, and other notable changes, with at most one entry per feed. Service incidents are on the status board; security baseline downloads, first captures of a document, and metadata-only documentation checks are left out. This is a view of retained evidence, not a reconstruction of everything known at the time.
The briefing is selective. Browse every dated change, review upcoming dates or check the period's coverage.