Microsoft 365 December 2025 Changes: The Essential (and Thorough) Admin Roundup You Can’t Skip

Thrilling Microsoft 365 December 2025 Update: Security, Cleanup, and Copilot Prep for 2026

User avatar placeholder
Written by Dave W. Shanahan

December 2, 2025

Microsoft 365 is closing out 2025 with one of its most impactful update waves of the year, turning many of November’s Ignite announcements into real-world changes that admins will feel in day‑to‑day operations. December 2025 is very much a “catch up before year‑end” month, blending retirements, new security and compliance capabilities, and a few breaking changes that IT teams must address to avoid surprises going into 2026. This is not just another minor service update; it is the point where Microsoft starts to standardize experiences, simplify reporting, and clear the decks for a more Copilot‑heavy roadmap next year.

For Microsoft 365 December 2025 specifically, you are looking at roughly 6 retirements, 10 new features, 7 enhancements, 3 existing functionality changes, and 2 action-required items that IT teams should review in their next change window. Think of this as the “catch up before year-end” set of updates that tidy up older experiences and push newer Copilot- and compliance-aware capabilities to the front.​

Microsoft 365 December 2025 Update at a glance

If November was about announcements and roadmaps, December is where those ideas land as concrete service changes across Microsoft 365 tenants. You are looking at roughly six retirements, ten new features, seven enhancements, three functionality changes, and two “action‑required” items that admins should prioritize in their next change window. The overall theme is cleaning up legacy features, tightening security and auditing, and pushing newer Copilot‑ and compliance‑aware experiences to the front. For most organizations, this will mean a mix of user communication, script refactoring, and policy tuning rather than large‑scale migrations.

From a planning perspective, it helps to treat this bundle of changes as a year‑end hygiene and modernization phase. If you have been experimenting with Copilot, Insider Risk, or Microsoft 365 Backup throughout 2025, December’s updates give you more control and visibility. If you have left older cmdlets, Android devices, or niche features running on autopilot, this is the month to bring them under control before they break or quietly disappear.

Microsoft 365 December 2025: Security and Auditing

Microsoft 365 December 2025 Changes: The Essential (and Thorough) Admin Roundup You Can’t Skip

Three items stand out this month as “high-impact” from a security and compliance perspective: tenant-owned domain impersonation in Teams, mailbox audit cmdlet retirement, and more precise identity alerts in Defender XDR.​

  • Tenant-owned Team impersonation in Teams extends existing brand impersonation detection so Microsoft 365 can spot attempts to spoof domains owned by your tenant, not just public brand domains. This gives security and compliance teams better tooling against phishing and lookalike attacks that abuse internal domains in chats, meetings, or invitations.​

  • The Search-MailboxAuditLog and New-MailboxAuditLogSearch cmdlets are being retired by late December 2025, with Search-UnifiedAuditLog now the supported way to query audit records across Microsoft 365. Admins who still rely on the older cmdlets in scripts or runbooks need to refactor those workflows to Unified Audit Log queries to avoid failures when the retirement hits.​

  • Defender XDR is adding finer-grained control for Entra ID Protection alert ingestion, letting you choose whether to ingest only high-risk detections, high plus medium risk, or all signal types. This enables SOC and SecOps teams to tune noise levels and focus on the highest-value identity threats, especially in larger tenants where alert volume can be overwhelming.​

Security and auditing take center stage

Three security and compliance updates stand out above the rest: tenant‑owned domain impersonation detection in Teams, the retirement of legacy mailbox audit cmdlets, and more granular identity alert ingestion in Defender XDR. Together they signal a shift toward more precise, tenant‑wide visibility and fewer siloed tools that only cover one workload at a time.

Tenant‑owned domain impersonation in Teams extends Microsoft’s brand impersonation protections so they can now detect attempts to spoof domains that belong to your tenant, not just public consumer brands. That matters for phishing and social engineering scenarios where attackers try to mimic internal users, meeting invites, or system messages using lookalike addresses and naming. Security and compliance teams should verify that their threat protection policies and user training materials highlight Teams as a channel where impersonation attacks can now be detected and investigated.

On the auditing front, the Search‑MailboxAuditLog and New‑MailboxAuditLogSearch cmdlets are being retired by late December 2025 in favor of the unified Search‑UnifiedAuditLog experience. That means any scripts, SOAR runbooks, or manual workflows that still rely on the older Exchange‑specific cmdlets need to be refactored or they will fail once the retirement completes. Moving to the Unified Audit Log centralizes your query experience across Exchange, SharePoint, Teams, Entra ID, and other services, but it also means updating documentation, access controls, and any downstream tooling that parses audit exports.

Defender XDR is also getting finer‑grained controls for Entra ID Protection alert ingestion. Instead of an all‑or‑nothing feed, SOC teams will be able to choose whether they ingest only high‑risk identity detections, high plus medium, or all available signal types. This is especially useful for large tenants where identity‑focused alerts can overwhelm analysts or SIEM storage if they are not filtered. Tuning these settings thoughtfully can help you reduce noise while still surfacing the identity risks that matter most to your environment.

Retirements that will change user habits

December brings six notable retirements that touch user experience, automation, and device support, with impacts that show up most clearly in Places, Copilot for Excel, Teams devices, PowerPoint, and Viva. Some of these are soft landings with clear replacements, while others will require a bit more change management.

Favorite Contacts in Microsoft Places is being retired in favor of the more consistent Frequent Contacts model used across Microsoft 365. Users will lose the ability to manually curate favorites in Places, and admins will lose the related PowerShell controls. That means any internal guides that reference Places favorites should be updated, and users should be coached to rely on frequent contact behavior instead of manual lists.

In Copilot for Excel, the App Skills feature is going away as Microsoft pivots toward richer agent experiences and Agent Mode for in‑workbook intelligence. Organizations that built workflows or training around App Skills will need to evaluate Copilot Chat and newer spreadsheet agents as the long‑term replacement. This is also a good moment to revisit how your users invoke Copilot in Excel and whether they understand the difference between generic chat and workbook‑aware agents.

On the device management side, the TeamworkDevice (beta) Graph API used for managing Windows‑based room devices is being retired, so customers should plan to move to newer generally available APIs for Teams Rooms and meeting devices. At the same time, Teams support for Android 8 devices ends fully by late December 2025, including security updates and bug fixes. Any organization still running older Android‑based phones or room panels for Teams needs a short‑term plan for upgrades or replacements to avoid being stuck on unsupported hardware.

PowerPoint’s Reuse Slides feature on Windows and Mac is also being discontinued, nudging users toward modern content reuse patterns based on SharePoint, OneDrive, and Loop. For many, this will reinforce the idea that “single source of truth” lives in shared libraries and collaborative workspaces instead of individual decks. Finally, in Viva Connections for Education tenants, the Assignments and Courses ACEs and their associated dashboard web parts are retiring, so schools should confirm their home experiences no longer depend on those components.

New features focused on lifecycle and governance

On the positive side of the ledger, December’s new features lean heavily into data lifecycle management, security, and productivity in places where Copilot and data governance intersect. These changes are less about flashy UI and more about giving admins the tools to manage the sprawl that Copilot and cloud collaboration naturally create.

Purview Data Lifecycle Management is introducing Priority Cleanup policies for OneDrive and SharePoint, giving admins a secure way to delete content even when retention or legal holds are in place. This is aimed at scenarios like cleaning up Copilot artifacts, Teams recordings, or sensitive project libraries where data technically needs to go but approvals and audit trails still matter. Used carefully, Priority Cleanup can help reduce clutter and risk without undermining your compliance obligations.

Teams presence is becoming more accurate by looking beyond just the state of the Teams tab and into overall device activity. That should reduce the classic “I’m working but Teams says I’m away” complaints and make presence more trustworthy as a signal for availability, especially in hybrid environments. Teams will also use device connection to corporate Wi‑Fi to automatically detect and set user work locations, helping support hybrid work policies and location‑aware experiences without extra manual effort.

On the compliance and investigations side, Data Security Investigations are gaining better cost visibility with lightweight estimators and usage dashboards, so admins and compliance officers can better forecast spend for large investigations. Purview Information Rights Management is integrating with Data Security Investigations, allowing pre‑scoped investigations to be launched directly from IRM cases when suspicious activity occurs. Backup‑related events such as policy updates, backup triggers, and restore actions will now be written to monitoring logs, improving observability for Microsoft 365 Backup.

User‑facing protections are tightening too. DLP email notifications will start offering self‑service corrective actions, letting users stop sharing or delete files directly from the notification when they violate a policy. The new Outlook for Windows will support direct import of .pst files into user mailboxes, simplifying cleanup of legacy PST archives. A ChatGPT Enterprise connector is arriving in the Purview Compliance Portal so prompts and responses can be audited and placed under retention, and Purview eDiscovery (Premium) will support importing non‑Microsoft 365 data sources for consolidated legal review.

Labeling, risk, and backup refinements

Beyond completely new features, December includes a set of refinements aimed at organizations that rely heavily on classification, risk signaling, and backup. These changes are subtle but important for tenants that live and die by labels and policies.

Parent sensitivity labels are being replaced with label groupings, so users always select an actual label while admins can still organize those labels into logical hierarchies. This should reduce confusion where users previously selected top‑level parent labels that did not enforce any real policy, leading to inconsistent protection. Organizational Messages are expanding to Entra ID hybrid‑joined devices, increasing the reach of IT communications and adoption campaigns beyond cloud‑only endpoints.

Purview Insider Risk Management is also getting a scale‑up, with higher limits for variants per indicator, total variant counts, and detection group capacities. That will help large or complex organizations model more nuanced risk policies without hitting artificial limits. IRM policies will now support multiple DLP policies as triggers, allowing teams to correlate signals instead of relying on a single condition to fire an insider risk alert.

In the infrastructure and records space, Exchange Online GCC High and DoD environments are gaining inbound SMTP DANE with DNSSEC to improve email integrity and resilience, and Microsoft 365 Backup is starting to roll out to GCC environments for more regulated tenants. Microsoft Planner is getting Data Lifecycle Management support, bringing retention policies to Planner tasks and related content so project data can be kept in step with your broader records strategy.

Functionality changes and action‑required items

Three functional changes in December will affect how admins read telemetry, manage firewalls, and interpret Copilot agent usage across SharePoint. The existing Teams app usage report is being replaced with an Integrated Apps usage report that surfaces usage for Teams, Outlook, Microsoft 365 apps, and Copilot extensions in a single, richer view. Anyone exporting or automating around the old report should validate their scripts and dashboards to ensure they still work once the new report becomes the default.

Microsoft Intune network endpoints are moving behind Azure Front Door IP ranges, which matters for tenants with strict firewall allowlists or those still relying on Basic Mobility and Security. Network teams will need to refresh their firewall rules using the latest documented IPs and thoroughly test device enrollment, policy deployment, and app delivery after the change. SharePoint agent usage reporting is also shifting from per‑site reporting to a tenant‑wide report, simplifying central analysis but changing where admins go to drill into agent activity, especially for early Copilot agent pilots.

Two items in December explicitly require action before mid‑month. Managed connectors for syncing UKG and Blue Yonder data into Teams Shifts are retiring on December 7, 2025, so any organization using them must transition to custom integrations or alternative HR/time‑tracking flows. Then, on December 8, 2025, the Visio Data Visualizer add‑in is being removed from Excel, meaning admins should disable the add‑in, notify users, and instruct teams to save diagrams as .vsdx files for direct use in Visio.

How admins should prepare for 2026

The best way to handle these Microsoft 365 December 2025 changes is to treat them as a structured cleanup and preparation effort ahead of a more Copilot‑centric 2026. Start by reviewing scripts and automations for any dependence on Search‑MailboxAuditLog and New‑MailboxAuditLogSearch, and move those workflows to Search‑UnifiedAuditLog while you still have a grace window. In parallel, inventory Android 8 devices running Teams and plan upgrades or replacements before end‑of‑support hits at the end of the month.

Security and compliance stakeholders should meet to configure Priority Cleanup policies, updated Insider Risk limits, and Defender XDR alert ingestion so they align with your organization’s risk posture and appetite for alert volume. Communication is just as important: front‑line users and champions should hear about Favorite Contacts retirement, Reuse Slides removal, the Copilot for Excel App Skills change, and Visio Data Visualizer deprecation with clear alternatives and timelines. Handled proactively, this December wave helps standardize user experiences, consolidate reporting, and put your tenant in a strong position for the deeper Copilot and data governance capabilities Microsoft has planned for 2026.

See the Microsoft 365 Roadmap


Discover more from Microsoft News Now

Subscribe to get the latest posts sent to your email.

Image placeholder

I'm Dave W. Shanahan, a Microsoft enthusiast with a passion for Windows 11, Xbox, Microsoft 365 Copilot, Azure, and more. After OnMSFT.com closed, I started MSFTNewsNow.com to keep the world updated on Microsoft news. Based in Massachusetts, you can find me on Twitter @Dav3Shanahan or email me at davewshanahan@gmail.com.