MDAG for Office Retirement: Phase Timelines and Protected View

Microsoft is removing Microsoft Defender Application Guard (MDAG) for Office from Microsoft 365 desktop apps, with the feature scheduled for phased removal beginning in early 2026 and complete removal by December 2027—documents that once opened inside a Hyper‑V backed, containerized Application Guard environment will instead open in Protected View, and administrators are being asked to rely on Attack Surface Reduction (ASR) rules and Windows Defender Application Control (WDAC) to preserve security.

Background​

Microsoft Defender Application Guard for Office was introduced to address a persistent risk vector: untrusted Office files carrying code or exploits that could compromise a Windows host. MDAG worked by launching Word, Excel, or PowerPoint files inside an isolated Hyper‑V container, separating the file’s runtime from the host OS and limiting what the document could access. That isolation offered a strong, near‑hardware level boundary for high‑risk attachments and downloads.
Over recent years Microsoft has adjusted its security portfolio and is now consolidating protection approaches. The vendor announced a phased removal of MDAG from Office applications, beginning with Office version 2602 and completing with Office version 2612. Files that would previously have opened inside MDAG will instead open in Protected View, the existing read‑only safeguard that disables editing and macros until a user explicitly trusts the document.
This change is part of a broader alignment with Windows lifecycle and support timelines and sits alongside guidance to enable Defender for Endpoint ASR rules and WDAC as enterprise controls to compensate for the loss of MDAG’s container‑based defense.

---

What Microsoft is changing — the timeline and the mechanics​

Microsoft has broken the removal into two phases tied to Office release versions and update channels.

• Phase 1 — removal begins with Office version 2602:
• Current Channel: early February 2026
• Monthly Enterprise Channel: April 2026
• Semi‑Annual Enterprise Channel: July 2026
• Phase 2 — full removal with Office version 2612:
• Current Channel: early December 2026
• Monthly Enterprise Channel: February 2027
• Semi‑Annual Enterprise Channel: July 2027

Operationally, Phase 1 will disable Application Guard behavior for Office files and may allow support exceptions during the transition window. Phase 2 will fully remove MDAG from Office installs with no workaround. No administrative action is required to trigger the removal; Microsoft will push the change through Office updates on the stated schedule.
Microsoft’s guidance to enterprise administrators is clear: ensure ASR rules in Microsoft Defender for Endpoint are enabled and deploy WDAC policies to keep unwanted code from running. Administrators should also update helpdesk guidance and endpoint hardening documentation to reflect the change, because the practical behavior for end users (files opening read‑only in Protected View) will differ from the fully isolated experience MDAG delivered.

---

Why Microsoft is retiring Application Guard for Office​

Several factors underpin Microsoft’s decision:

• Product lifecycle alignment. The retirement aligns with Windows servicing and support schedules, particularly the phasing out of older Windows 11 feature releases and the APIs relied upon by MDAG.
• Simplification of security posture. Microsoft is consolidating defenses around a smaller set of manageable controls—Protected View, ASR, WDAC, and Defender for Endpoint—rather than maintaining a separate heavy‑weight isolation feature for Office.
• Maintenance and API dependencies. MDAG relied on Windows isolation APIs and Hyper‑V features that Microsoft has been deprecating or reworking; supporting MDAG across a fragmented Windows install base created engineering and support overhead.
• Cost/benefit for broad customer base. MDAG provided strong isolation but only to specific licensing and platform combinations. Microsoft appears to be prioritizing security controls that reach a broader set of customers through Defender for Endpoint and platform controls.

Those reasons are reasonable from an engineering and lifecycle perspective. However, they create a functional gap for organizations that relied on container‑level isolation for untrusted Office content.

---

Technical comparison: MDAG isolation vs Protected View​

Understanding the difference between these two behaviors is crucial for evaluating risk and mitigation strategies.

Microsoft Defender Application Guard (MDAG)​

• Ran Office files inside a Hyper‑V‑backed container.
• Isolated the Office process from user profile and system resources; network and file system access could be restricted.
• Allowed safer file viewing with more aggressive containment of potential exploit activity.
• Could protect against a wider range of post‑exploit actions because the Office process ran in a separate security boundary.

Protected View​

• Opens files in read‑only mode inside the same user session and process space (no separate Hyper‑V container).
• Macros and editing are disabled until a user explicitly enables them or trusts the file.
• Blocks many common file‑based attack vectors but does not provide the same execution isolation as MDAG.
• Easier to understand for end users (open read‑only, click ‘Enable Editing’ to trust) but more reliant on user behavior.

Key takeaway: Protected View reduces immediate attack surface by disabling active content, but it is not a substitute for a true container boundary. That difference matters for highly sensitive environments or where threat actors use sophisticated, zero‑day exploits that can escalate within a user session.

---

Immediate actions Microsoft recommends — and practical steps for admins​

Microsoft recommends enabling Attack Surface Reduction (ASR) rules in Defender for Endpoint and deploying Windows Defender Application Control (WDAC) policies. Those are sensible starting points, but they must be implemented carefully to avoid operational disruption.

• Enable core Attack Surface Reduction rules:
• Block macros from the internet.
• Block Office applications creating child processes.
• Block Office applications from creating executable content.
• Prevent Office from spawning or executing potentially risky code paths.
• Implement Windows Defender Application Control (WDAC):
• Create a policy that whitelists signed and trusted binaries.
• Use a phased approach—audit mode first, then enforced—so you can tune allow lists.
• Consider integration with enterprise signing or code‑signing processes for internal tools.
• Harden Office and endpoint configurations:
• Ensure Protected View is enabled for files from the web and other untrusted sources.
• Disable legacy protocols and block known risky file types where possible.
• Use Intune or Group Policy to centrally manage Protected View and macro handling.
• Operational readiness:
• Inventory where MDAG is actively used today and identify user groups and machines that rely on it.
• Run WDAC policies and ASR in audit mode to produce telemetry without blocking production workloads.
• Update helpdesk scripts and documentation explaining the Protected View change to reduce support calls.
• Train users on the meaning of Protected View and safe handling of files that require enabling editing.

---

Recommended migration plan — a phased, test‑driven approach​

• Assess: Discover all devices and users that rely on MDAG, using endpoint telemetry and group policies.
• Pilot: Select a small number of business units to pilot ASR rules and WDAC policies, running in audit mode for 2–4 weeks.
• Harden: Tune ASR and WDAC based on telemetry; address false positives and necessary allow‑lists.
• Educate: Provide clear user guidance on Protected View behavior and the risk model for macros and external content.
• Enforce: Move WDAC and ASR to enforced mode only after confidence in policy coverage.
• Rollout: Coordinate the Office update rollout per channel timing. Ensure helpdesk staffing aligns with the Phase 1/Phase 2 schedule.
• Validate: Post‑deployment, verify telemetry (blocks, ASR events, application control denies) and adapt.

This staged plan minimizes business disruption while restoring a comparable level of protection.

---

Benefits of the change — what organizations gain​

• Simplified security model. Fewer moving parts to manage when MDAG is removed and organizations focus on ASR, WDAC, and Protected View.
• Broader reach. ASR and WDAC apply across many devices and don’t require the Hyper‑V or platform prerequisites MDAG did.
• Reduced support surface. Removing a deprecated feature reduces the need for specialized troubleshooting and lowers attack complexity stemming from stale APIs.
• Predictable behavior. Protected View is a long‑standing Office feature with well‑known behavior for users and admins.

---

Risks and limitations — where protection weakens​

• No container boundary. Protected View does not isolate the Office runtime in a separate Hyper‑V container; advanced post‑exploit techniques could still be effective within a user’s session.
• User decision dependency. Protected View relies on users to not enable editing or macros unless they truly trust the file—social engineering can circumvent this.
• Potential gaps in ASR/WDAC coverage. Misconfiguration, lack of tuning, or incomplete allow lists can create operational friction or leave blind spots.
• Legacy and specialized workflows. Some applications or add‑ins depended on MDAG behavior; those workflows may break or require re‑engineering.

Where a strict sandbox boundary was required (for example, in hostile environments with high‑value targets), losing MDAG’s isolation may represent a substantive downgrade unless compensated by other controls like hardware‑enforced vTPM policies or full VM‑based sandboxes.

---

Edge cases and special considerations​

• Virtual Desktop Infrastructure (VDI) and shared environments may require different WDAC and ASR tuning compared to physical desktops.
• If any line‑of‑business applications relied on MDAG APIs or isolation semantics, testing is essential—replacing MDAG may require app rewrites or additional host‑based controls.
• Macros: Organizations that legitimately use macros should adopt strict digital signing practices and control macro enablement through Group Policy and Intune.
• Offline or disconnected devices: ASR telemetry and WDAC enforcement benefit from cloud telemetry; offline devices should be given special attention to ensure policies are up to date and signed binaries are available.

---

Alternatives and complementary technologies​

MDAG was one containment option; several other Microsoft and third‑party mechanisms can be combined to approximate or extend protection.

• Windows Sandbox: Good for interactive inspection of untrusted binaries and files in an ephemeral environment; not a direct Office integration but useful for analysts.
• Virtual Machines or isolated review workstations: For very high‑risk files, using a dedicated VM that can be quickly reset offers a stronger isolation guarantee.
• Browser and cloud‑based file viewing: Viewing Office files through cloud services (Office for web) or secure browser isolation can offload risk from endpoints.
• Third‑party file sandboxing and detonation services: Some security vendors provide automated file detonation with behavioral analysis that can be integrated into mail or file gateways.
• Microsoft Defender for Endpoint features: Endpoint detection and response (EDR), exploit protection, and threat and vulnerability management remain essential layers.

Each alternative introduces tradeoffs in user experience, cost, and operational complexity.

---

Practical recommendations for Windows and Microsoft 365 admins​

• Start immediately: begin inventory and telemetry collection to identify MDAG users and scenarios.
• Prepare for the Office release cadence: map the Microsoft Office channel timelines to enterprise update rings and coordinate deployment windows accordingly.
• Use ASR and WDAC together: ASR reduces attack surface and blocks risky behaviors, while WDAC prevents unauthorized code execution. Both are stronger when tuned in combination.
• Adopt an evidence‑based rollout: use audit modes, refine policies from telemetry, then enforce.
• Improve macro hygiene: require signed macros, use AppLocker/WDAC to restrict what unsigned macros can perform, and disable VBA where not needed.
• Update documentation and service‑desk scripts: reduce confusion for users encountering Protected View and explain the safe process to request access for trusted documents.
• Consider long‑term architectural changes: where isolation is business‑critical, evaluate VMs, dedicated review systems, or cloud viewing to replace MDAG’s guarantees.

---

Strategic implications and what this means for enterprise security​

The removal of MDAG points to a broader security design shift: Microsoft continues consolidating protections into cross‑platform, centrally manageable capabilities rather than maintaining feature‑specific isolation for particular client apps. For many organizations, that will be an overall positive—simpler policies, fewer compatibility constraints, and wider availability of protections. For others, especially those who use MDAG as a key sandboxing control in high‑risk environments, this retirement forces a strategic reappraisal.
Enterprises must move from a posture of relying on a single feature to a layered approach. That includes prevention (ASR, WDAC), detection and response (Defender EDR), and operational controls (user behavior training, signed macros). Where necessary, organizations should also consider dedicated sandbox environments or alternative isolation technologies to maintain the highest levels of protection.

---

Risk scenarios that require immediate attention​

• Financial services, government, healthcare, and critical infrastructure teams that accepted files from external partners and used MDAG as a primary isolation control should treat this change as high priority.
• Organizations using third‑party integrations or macros frequently distributed via email must lock down macro signing and restrict macro execution to signed and vetted publishers.
• Teams with legacy systems or specialized add‑ins should run compatibility tests; MDAG removal can break automation or workflows that assumed containerized file handling.

If these scenarios match the organization’s profile, accelerate pilot and WDAC/ASR enforcement now rather than later.

---

Longer‑term outlook and evolving security posture​

The broader trend is toward centralized, cross‑platform security controls that can be managed at scale. Expect Microsoft to continue investing in Defender for Endpoint, ASR rule sets, cloud‑delivered protections, and improved Office hardening features. At the same time, container and virtualization technologies remain central to isolating untrusted workloads; enterprises will need to choose where those boundaries are enforced—at the Office app layer, the OS, or at a virtual machine boundary.
Security teams should view this as an opportunity to modernize endpoint defenses, reduce reliance on single‑feature containment, and increase focus on telemetry, response, and policy automation.

---

Conclusion​

The retirement of Microsoft Defender Application Guard for Office marks the end of a distinctive, container‑based Office protection that provided a powerful isolation boundary for untrusted documents. Microsoft’s planned removal—phased between early 2026 and mid‑2027—will replace MDAG behavior with Protected View and urges administrators to rely on Attack Surface Reduction rules and Windows Defender Application Control to retain strong protections.
For many organizations, the impact will be manageable if they adopt ASR, WDAC, and robust policy‑driven controls. For high‑risk environments where a container boundary is non‑negotiable, the change demands an urgent reassessment of isolation strategies, potentially investing in VMs, sandbox solutions, or other architectural mitigations.
Actionable next steps for administrators:

• Inventory current MDAG usage and impacted user groups.
• Pilot ASR and WDAC in audit mode and tune from telemetry.
• Educate users on Protected View and update helpdesk guidance.
• Implement WDAC and ASR in enforced mode only after rigorous testing.
• Consider supplemental isolation (VMs, sandboxing) for highest‑risk scenarios.

This is a strategic inflection point: the retirement simplifies Microsoft’s Office security surface but transfers responsibility to organizations to put in place layered, modern defenses that match their risk profiles. The clock is set by Office release channels—begin planning now to avoid being caught mid‑transition when MDAG behavior disappears from deployed endpoints.

---

Source: Windows Report Microsoft to Retire Defender Application Guard for Office by 2027

 

[ChatGPT]

Microsoft is retiring PowerPoint’s decade‑old Reuse Slides tool from the desktop ribbon — a change that will remove the right‑hand reuse pane Windows and Mac users have relied on for selective slide import — even as the company pushes Copilot features deeper into PowerPoint’s workflow. The removal is listed in Microsoft’s admin communications and will be rolled out as part of a retirement timetable that Microsoft says begins in late 2025 and completes in January 2026; Microsoft also explicitly warns administrators that the option cannot be re‑enabled once it’s removed.

---

Background​

PowerPoint’s Reuse Slides feature has long provided a convenient, in‑app pane for pulling single slides or entire slidesets from other .ppt/.pptx files, with a checkbox to Keep source formatting so imported material can retain corporate templates, footers, and animations. That dedicated pane eliminated the need to open both presentations and to copy/paste manually for many users — a time‑saving convenience for agencies, internal comms teams, and anyone assembling decks from a library of prior work. Third‑party guides continue to describe the tool’s mechanics because it has been an entrenched part of many users’ workflows. At the same time, Microsoft’s ramp‑up of Copilot features in PowerPoint (slide generation from Word documents, one‑click draft slides, and AI‑assisted layout and speaker notes) has reshaped how the company frames productivity gains in presentations. Administrators are being asked to balance retiring legacy UI elements that duplicate functionality against supporting new AI workflows that change where and how slide content is created.

---

What Microsoft has announced — dates, scope, and the “no rollback” warning​

• Microsoft’s Microsoft 365 message notes and admin advisories indicate the Reuse Slides UI will be removed from PowerPoint for Windows and Mac desktops as the feature is retired. The message explains the change is intended to reduce redundancy in the product and directs admins to update documentation and identify alternatives.
• Microsoft’s published timetable states the retirement will begin in December 2025 and is expected to complete in January 2026 for the Windows and macOS desktop apps; administrators are warned there will be no option to re‑enable the feature once it is removed.
• Earlier communications and community reports show some timeline variation in public coverage — including reporting that the Reuse Slides button was slated for deprecation as early as July 2025 — which appears to reflect staged announcements and updates from Microsoft’s Message Center over 2025. Readers should treat earlier single‑date headlines as superseded by the later admin advisory unless their tenant received an earlier removal. Where there are conflicting dates in public reporting, the most recent Microsoft message center posting should be considered authoritative for rollout timing.

This combination of an admin‑level message and vendor rationale makes the retirement official: the feature is being removed from the Ribbon and the product team is not providing an on/off toggle for customers.

---

What Reuse Slides did, and why people will miss it​

The Reuse Slides pane offered several practical benefits that made it sticky in enterprise workflows:

• Selective import with formatting control — users could pick particular slides and choose whether to Keep source formatting so the slide inserted with original template rules.
• Sidebar workflow — because the action opened a right‑hand pane inside PowerPoint, it was possible to browse files (local, SharePoint or OneDrive) and import slides without switching apps.
• Preservation of animations and media — in most cases dragging or using Reuse preserved animations, transitions, and embedded media better than naive copy/paste.
• A predictable UI for templates and corporate branding — teams could maintain logo placement and footers when pulling into an existing template or inserting slides that kept their original look.

These are precisely the characteristics users are pointing to when they say the downtime in muscle memory and the small feature polish matter — especially for repetitive tasks like assembling proposals or combining decks. Third‑party commentators and trainers have emphasized how the pane simplified reuse across file stores and saved a few minutes per slide that add up across teams.

---

Why Microsoft says it’s removing Reuse Slides​

Microsoft frames the retirement as a product simplification: the company argues the feature is redundant because users can already copy/paste slides or duplicate presentations, and newer workflows such as co‑authoring, SharePoint/OneDrive slide sharing, and Copilot‑based slide creation provide alternatives. The admin guidance explicitly recommends updating documentation and suggests alternative methods to reuse slides. Administrators are told no action is required to effect the change — the retirement is automatic. It’s worth noting that product teams often remove low‑usage or duplicative UI elements to reduce maintenance overhead and focus development resources on features with broader adoption, such as Copilot. That is Microsoft’s stated rationale here.

---

Reconciling conflicting timelines in public reporting​

Multiple community sites and Microsoft Message Center entries recorded different rollout dates across 2025. An earlier Message Center item (MC1111178) and third‑party commentary reported removal or deprecation around July 31, 2025; a later message (MC1179161) clarified retirement activity would start in December 2025 and complete January 2026 for the desktop apps. That suggests Microsoft updated its internal rollout plan and the administrator guidance was refreshed accordingly. Readers and IT teams should rely on the most recent Message Center post published to their tenant and the October 24, 2025 advisory for the latest schedule. If your tenant’s Message Center shows a different Message ID and date, treat that tenant‑specific posting as the authoritative timeline.

---

Practical alternatives — what to use instead of Reuse Slides​

For most users and many organizations, the following techniques will replicate the practical effect of Reuse Slides. Each method has tradeoffs; choose based on how much template fidelity, control, and governance you require.

1) Drag and drop / Copy‑paste between open presentations (good balance)​

• Open both the source and destination presentations.
• Arrange windows side‑by‑side (Windows Snap / macOS Window > Tile) or use multiple monitors.
• Select slides in the source (use Ctrl/Cmd + click or Shift + click for ranges).
• Drag them into the destination Slides pane or copy/paste and choose Keep Source Formatting from the paste options.

This retains animations and media in most cases and is the closest 1:1 replacement for the sidebar flow, but it requires the source file to be opened. Many experienced users already rely on this approach.

2) Duplicate the whole presentation with “New Window” or Save As (best for full clones)​

• On Windows: open the presentation, go to View → New Window, then Save As to a new filename. You’ll have a replica you can edit without disturbing the original.
• On macOS: the menu topology differs; use the Window menu or Save As to duplicate the file (macOS PowerPoint places windowing items in the top system menu bar). Some Mac builds expose the command outside the Ribbon. Check the app’s Window menu if you can’t find it in Ribbon commands.

This is ideal if you want an exact copy of the entire deck and then change content.

3) Insert → Slides from → (SharePoint / OneDrive / Slide Libraries) — for central shared slides​

Organizations that maintain a slide catalogue should use SharePoint/OneDrive co‑authoring and Slides from options or modern slide‑library patterns. Legacy Slide Libraries still exist in old SharePoint versions, but Microsoft now recommends sharing + co‑authoring for slide reuse in modern environments. If you rely on centrally curated slide assets, standardize on shared libraries or templates stored in OneDrive/SharePoint.

4) Copilot and “Create presentation from file” — an AI‑driven replacement for some scenarios​

For scenarios where the source is narrative (a Word document, PDF, or long report), Copilot’s Add a slide / Create presentation from file capabilities can auto‑generate slides and speaker notes from document headings and content. This does not preserve exact pixel‑perfect branding or layout by default, but it can produce a usable draft that teams refine. Copilot features are gated by licensing and app build; not every user will see the full capability depending on their tenant license and client build. For draft generation from narrative sources, Copilot can be faster than manual reuse.

---

Step‑by‑step: a recommended everyday replacement workflow​

If you used Reuse Slides daily, try this three‑step process to get close to the same experience:

• Open the destination deck and the source deck(s).
• Use your OS windowing (Windows Snap or macOS Tile) to place the destination on one side and the source on the other.
• Select the specific slides in the source and either drag them into the destination Slides pane or right‑click → Copy, then in the destination right‑click → Paste → Keep Source Formatting.

This preserves animations and formatting in most tested cases and is simple to teach to staff. If you need to clone an entire deck, open the source and use View → New Window and then Save As to create a working copy.

---

Enterprise impact — what IT should do now​

Microsoft’s advisory to admins is precise: update documentation and communicate the change. Beyond that, IT and training teams should take these steps.

• Communicate early and clearly. Announce the change, the effective window (December 2025 → January 2026 rollout), and the alternatives chosen by your org. Include screenshots and short how‑tos showing drag/drop and New Window duplication.
• Update onboarding and training materials. Replace any internal guides or training modules that reference Reuse Slides with the new standard operating procedure.
• Inventory processes that rely on Reuse Slides. Engage teams (sales, proposals, internal comms) to find critical workflows; if a workflow absolutely depends on the exact behavior of Reuse Slides, document the gap and design a mitigation path (e.g., shared slide library, automation, or an add‑in).
• Pilot Copilot for draft generation where appropriate. For teams that convert long reports into decks, test Copilot’s slide‑from‑file feature during a controlled pilot — but ensure governance and human‑in‑the‑loop verification for facts and brand compliance. Note licensing implications when scaling.
• Set governance guardrails. If teams move to Copilot, apply DLP, sensitivity labels, and Purview rules to prevent sensitive documents being sent to cloud processing where organizational policies prohibit it. Copilot interactions can be logged; plan audit and retention accordingly.

---

Risks and limitations of the alternatives​

• Copy/paste and drag‑drop are manual: they require the source deck to be open and add small friction versus the in‑pane browse flow.
• Duplicating entire presentations can fragment versions: maintain naming conventions and versioning policies to avoid accidental edits to the canonical deck.
• Slide Libraries in old SharePoint are legacy: they’re not a turnkey migration path for every organization and Microsoft points teams toward co‑authoring and modern file sharing instead.
• Copilot is not a formatting magic wand: it generates drafts well but does not guarantee pixel‑perfect template fidelity; it also carries governance and licensing considerations that must be managed.

Where public reporting disagrees on exact retirement dates, administrators must trust the Message Center notices targeted to their tenant and avoid relying on third‑party roundups that may be out of date. The most load‑bearing facts — that Microsoft will retire the feature, the general timeframe, and the recommendation to update documentation — are clearly present in Microsoft’s admin communication.

---

Quick checklist for end users and power users​

• If you use Reuse Slides for selective imports: practice the drag‑and‑drop or copy/paste flow now; make a short cheat‑sheet for your colleagues.
• If you use Reuse Slides to import entire presentations: start using New Window + Save As.
• If you rely on a slide library or centralized assets: migrate to OneDrive/SharePoint shared templates and quality‑control the library.
• If you’re an admin: post a tenant notice, schedule a training drop‑in, and update helpdesk scripts.

---

Final assessment — practical reality vs. user friction​

From a product management perspective, removing a low‑usage, partly redundant UI item makes sense: it reduces surface area for maintenance and encourages adoption of newer workflows. From a user perspective, the loss is real: Reuse Slides was a small, muscle‑memory convenience that smoothed everyday tasks. For many teams the operational cost will be limited — alternative workflows exist and can be taught quickly — but for high‑volume reuse scenarios (consultancies, proposal teams, agency environments) the change raises friction and may merit investment in shared slide libraries, training, or light automation (add‑ins, templates).
Copilot’s growth inside PowerPoint addresses some reuse pain points — particularly converting narrative into slides — but it does not replicate the exact preservation and selective import controls the Reuse Slides pane provided. The sensible path for organizations is to adopt a mixed approach: teach manual alternatives now, pilot Copilot where it adds value, and move centralized slide assets into modern shared libraries for governance and discoverability.

---

Removing a familiar tool will always produce grumbles; the practical response is straightforward: pick a fall‑back, document it for colleagues, and treat the retirement as an opportunity to standardize slide libraries and to pilot the new AI drafting features under tight governance. The end result for most organizations should be similar slide outcomes with a modest bump in process change — but teams that prepare now will lose less productivity when the pane disappears from the Ribbon between December 2025 and January 2026.

---

Source: Windows Latest Microsoft PowerPoint is removing "Reuse slides" on Windows & macOS, as it continues to add Copilot features