Weekly briefing
Week 35 · 24 Aug – 30 Aug 2026 UTC · assess the changes, then plan the next dates.
What this period includes
232 source records · 24 Aug – 30 Aug UTCThese counts cover retained dated evidence after your saved view and topic filters. Zero means no matching record in this period; it does not prove that a product had no changes.
| Area | Records | Evidence in this period | Dates in the next 30 days |
|---|---|---|---|
| Security | 25 | Added to CISA KEV · CISA KEV deadline · Message Center · Plan for change · Oracle · exploited, added to CISA KEV · Published vulnerability · Roadmap entry · Security advisory · Security news | 4 |
| Windows | 10 | Preview release · Product news · Windows news | — |
| Microsoft 365 | 99 | Message Center · Plan for change · Message Center · Stay informed · New version · Partner announcement · Product change · Product news · Roadmap entry | 8 |
| Identity & APIs | 13 | Message Center · Plan for change · Message Center · Stay informed · Product news | — |
| Azure | 18 | Azure update · Product news | — |
| Admin tools | 14 | New version · Product change · Product news · Service incident · Tool release | — |
| Other vendors | 38 | Product news · Service incident | — |
| Lifecycle | 0 | No retained dated records | 16 |
| Community | 15 | Community post | — |
Beyond feeds. The shared change model also includes public Message Center notices, service incidents, observed documentation and role changes, network ranges, Group Policy comparisons and lifecycle dates when those inputs supply dated evidence. Community posts and baseline downloads are available in the full change list.
History starts with evidence. A first role, document or policy capture establishes a baseline. Later comparisons produce change records; a baseline does not mean every entry was newly introduced. Month-only dates retain their stated precision.
Inspect source health and collection limits · Message Center coverage · Role catalogs and history · Documentation history