Office LTSC 2021 End of Support: The 2026 Migration Guide

Office LTSC 2021 reaches end of support on October 13, 2026. After that date, Microsoft stops delivering security updates, bug fixes, and technical support for Word, Excel, PowerPoint, Outlook, Access, Publisher, OneNote, and every other app in the LTSC 2021 suite. There is no extended support phase. There is no paid Extended Security Updates (ESU) program. The software will keep running, but every newly discovered vulnerability will remain permanently unpatched. (learn.microsoft.com)

If you are an IT Director or sysadmin running perpetual-license Office in a government agency, a hospital, a manufacturing plant, or any organization that deliberately avoided the Microsoft 365 subscription model — this article covers exactly what breaks, what your options are (including non-Microsoft alternatives), and how to sequence the migration.

What Happens on October 13, 2026?

Office LTSC 2021 follows Microsoft's Fixed Lifecycle Policy: five years of Mainstream Support, then nothing. Unlike Windows 10 or Windows Server 2012 R2, which offered paid ESU extensions, Office LTSC 2021 goes directly from supported to unsupported with no safety net. (learn.microsoft.com)

Historically, perpetual Office licenses (Office 2010, 2013, 2016) enjoyed a 10-year support lifecycle — five years of mainstream support followed by five years of extended support. Starting with Office 2021, Microsoft eliminated the extended support phase entirely, cutting the total supported lifespan in half. The April 2026 announcements were routine six-month reminders, not a new policy decision.

The full list of products losing support on or around October 13, 2026:

After October 13:

• No security patches. Any CVE filed against Word, Excel, or Outlook goes permanently unpatched. For reference, after Office 2013 reached end of support in April 2023, multiple critical vulnerabilities continued to be discovered in the Office codebase — including CVE-2023-36884 (a remote code execution flaw in Word exploited in the wild by Russian threat actors) and CVE-2023-44487. Organizations still running Office 2013 had no vendor-supplied fix. The same pattern will repeat for LTSC 2021.
• No bug fixes. Compatibility issues with newer operating systems or file formats will not be addressed.
• No technical support. Microsoft will not accept support tickets for LTSC 2021 issues.
• Online help content will be retired. Microsoft has confirmed that most documentation for Office 2021 will be removed or archived.

The technical reality is binary. The software will continue to boot, but it becomes a static, degrading asset. Any integration that relies on updated APIs, modern authentication protocols (e.g., OAuth 2.0 token refreshes), or secure cloud handshakes will break as the surrounding ecosystem evolves. TLS certificate changes, certificate authority rotations, and protocol deprecations at the service level can silently break Outlook connectivity to Exchange Online or OneDrive sync functionality.

The Compliance Risk of Running Unsupported Office Software

The "keep running it" strategy is not viable in regulated industries. The moment Microsoft stops patching Office LTSC 2021, compliance frameworks treat every device running it as a control failure.

Here is how the major frameworks view unsupported software:

• PCI DSS 4.0 — Requirement 6.3.3 mandates that all system components be protected from known vulnerabilities by installing applicable security patches. End-of-life software that no longer receives vendor patches fails this requirement unless compensating controls (e.g., application whitelisting, network microsegmentation, enhanced endpoint detection) are documented and validated by a QSA. The PCI Security Standards Council has stated that unsupported systems may fail patching requirements because vendor security patches may no longer exist. In a breach scenario, running EOL software can be treated as negligence. (pcisecuritystandards.org)
• HIPAA — The Security Rule (§ 164.308(a)(5)(ii)(B)) requires covered entities to maintain security patches and updates as part of their technical safeguards. Running unpatched Office on workstations that process ePHI creates a documentable gap that auditors will flag. OCR enforcement actions have cited failure to patch known vulnerabilities as a basis for penalties — the 2023 settlement with Banner Health ($1.25M) referenced inadequate patch management.
• SOC 2 — The Common Criteria (CC6.1, CC7.1) require that system components are monitored and maintained. Unsupported software is an automatic finding in a SOC 2 Type II audit and may result in a qualified opinion.
• ISO 27001:2022 — Control A.8.8 (formerly A.12.6.1) requires timely identification and remediation of technical vulnerabilities. Software that cannot be patched fails this control by definition. (iso.org)
• NIST SP 800-53 Rev. 5 — Control SI-2 (Flaw Remediation) requires organizations to identify, report, and correct information system flaws in a timely manner. Running software past its vendor-supported lifecycle creates a permanent open finding against this control family.
• FedRAMP / StateRAMP — Federal and state cloud authorization frameworks inherit NIST 800-53 controls. Agencies running unsupported desktop software connected to authorized cloud environments risk impacting the entire authorization boundary.

The financial penalty of a failed audit or a security breach vastly outweighs the licensing and migration costs of moving off legacy software. For a deeper analysis of what happens when you defer this decision, see our breakdown of the risks of the "do nothing" strategy for legacy Microsoft systems.

Path 1: Upgrading to Office LTSC 2024 (The On-Premises Route)

Office LTSC 2024 is the direct perpetual-license successor. It launched on October 1, 2024, and is supported until October 9, 2029 under the same Fixed Lifecycle Policy — five years, no extended support afterward. (support.microsoft.com)

This path is the correct choice — and in some cases the only viable choice — for organizations that meet specific criteria:

• Air-gapped or disconnected environments (manufacturing floors, classified networks, SCADA systems, medical testing equipment)
• Regulatory or sovereignty constraints that prohibit cloud-connected software or data leaving a specific jurisdiction
• Procurement processes that cannot accommodate subscription licensing (common in government and education)
• Environments where continuous feature updates create unacceptable regression risk for validated workflows

Licensing and Cost

Microsoft prices Office LTSC 2024 through Volume Licensing agreements. Published pricing (as of early 2025):

• Office LTSC Standard 2024: ~$250–$300 per device (one-time, Volume Licensing)
• Office LTSC Professional Plus 2024: ~$350–$440 per device (one-time, Volume Licensing)

Actual pricing varies by agreement type (EA, Select Plus, Open Value), organization size, and region. Unlike Microsoft 365, LTSC licenses are device-based: one license per physical device, regardless of how many users share it. There is no per-user option, and the license does not include upgrade rights to future LTSC versions. (support.microsoft.com)

What Changes in LTSC 2024

• Publisher is gone. Microsoft is retiring Publisher entirely in October 2026. LTSC 2024 does not include it. Organizations relying on Publisher need to migrate those workflows to Word, Adobe InDesign, or Canva before the transition. Search for *.pub across desktops, file shares, and SharePoint now.
• ActiveX controls are disabled by default. IT admins can re-enable them via Group Policy (User Configuration > Administrative Templates > Microsoft Office 2016 > Security Settings > Disable All ActiveX), but this signals Microsoft tightening the security baseline on LTSC deployments.
• No Copilot. Microsoft has been explicit: "Microsoft 365 (or Office 365) is also required to subscribe to Microsoft 365 Copilot; as a disconnected product, Office LTSC does not qualify." If your organization's AI strategy involves Copilot, LTSC is incompatible.
• No real-time collaboration. Co-authoring, cloud-backed security, and AI-driven automation in Word, Excel, and PowerPoint are Microsoft 365–only features.
• ODF 1.4 support. Word, Excel, and PowerPoint in LTSC 2024 support saving in OpenDocument Format 1.4 — relevant for government agencies with open-format mandates.
• Teams is not bundled. Teams is available as a separate free download (New Teams client).
• Still Click-to-Run, not MSI. Older MSI-based packaging, detection logic, and software-distribution scripts will need rework even if you stay perpetual.

Deployment Mechanics

The upgrade from LTSC 2021 to LTSC 2024 is relatively straightforward since both use Click-to-Run. Use the Office Deployment Tool (ODT) with a configuration XML:

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

The <RemoveMSI /> tag cleanly uninstalls previous MSI-based Office installations before laying down the Click-to-Run binaries. KMS and MAK activation methods are unchanged. For Intune-managed environments, you can deploy LTSC 2024 as a Microsoft 365 Apps (Windows 10 and later) app type in the Intune admin center, selecting the "Office LTSC Professional Plus 2024" suite and configuring the update channel to PerpetualVL2024.

The Honest Trade-Off

LTSC 2024 extends your supported lifecycle to October 2029. For organizations in genuinely air-gapped environments, with validated regulatory workflows, or with procurement constraints that prohibit subscriptions, this is a rational and defensible choice — not a compromise. The one-time purchase does not include upgrade rights to any future LTSC release. (support.microsoft.com)

For organizations with internet-connected environments and no hard constraints against subscription licensing, the calculus is different. Every LTSC release removes features relative to Microsoft 365, and the 5-year lifecycle means you will face another forced migration in 2029 — a recurring cost that should be weighed against the ongoing subscription cost of Microsoft 365.

Rollback Planning

Before any deployment, create a rollback procedure. For Click-to-Run upgrades, the ODT does not natively support downgrade. If LTSC 2024 breaks a critical workflow:

1. Uninstall LTSC 2024 via setup.exe /uninstall ProPlus2024Volume
2. Reinstall LTSC 2021 from your original Click-to-Run source
3. Reactivate via KMS/MAK

Test your rollback in a lab environment before touching production devices. For Intune-managed devices, ensure the LTSC 2021 package remains available as a deployable app during the transition window.

Path 2: Migrating to Microsoft 365 (The Cloud Route)

Migrating from Office LTSC 2021 to Microsoft 365 Apps is not a version upgrade — it is an architectural shift. The licensing model, update cadence, identity infrastructure, and deployment methodology all change.

Key Architectural Differences

Licensing and Cost

Microsoft 365 plans relevant to LTSC 2021 migrations:

• Microsoft 365 Apps for enterprise: ~$12/user/month (desktop apps only, no Exchange/Teams/SharePoint)
• Microsoft 365 E3: ~$36/user/month (includes Exchange Online, SharePoint, Teams, Intune, Entra ID P1)
• Microsoft 365 E5: ~$57/user/month (adds advanced security, compliance, and analytics)
• Microsoft 365 Business Standard (≤300 users): ~$12.50/user/month
• Microsoft 365 Business Premium (≤300 users): ~$22/user/month (adds Intune and Entra ID P1)
• Microsoft 365 GCC / GCC High: Pricing varies; GCC High typically carries a 30–40% premium over commercial E3/E5

At $36/user/month for E3, a 500-user organization pays $216,000/year — compared to a one-time LTSC 2024 cost of ~$175,000–$220,000 for the same 500 devices. The breakeven point is roughly 12–15 months, after which the subscription becomes more expensive on a pure licensing basis. However, Microsoft 365 bundles Exchange Online, SharePoint Online, Teams, Intune, and Defender — services that would otherwise require separate on-premises infrastructure and licensing.

What the Migration Requires

1. Identity infrastructure. LTSC uses device-based activation. Microsoft 365 requires every user to have a Microsoft Entra ID (formerly Azure AD) account. If you do not already have Entra ID configured — and many LTSC-only shops do not — this is a prerequisite project that needs to complete before any Office deployment. In shared-computer scenarios, synchronized on-prem AD and Entra ID identities reduce activation prompts. Budget 2–4 weeks for Entra ID Connect setup, pilot sync, and validation in a typical environment. (learn.microsoft.com)

2. License selection. Microsoft's recommended plans depend on org size:

   • Enterprise (300+ users): Microsoft 365 E3, E5, or Microsoft 365 Apps for enterprise
   • SMB (<300 users): Microsoft 365 Business Standard, Business Premium, or Microsoft 365 Apps for business

3. Uninstall LTSC before deploying M365 Apps. Microsoft does not support running LTSC and Microsoft 365 Apps side-by-side on the same device. You must uninstall the old version first. The Microsoft Support and Recovery Assistant (SaRA) can automate this, or you can script it via ODT. (learn.microsoft.com)

4. OneDrive and SharePoint Online setup. Moving to Microsoft 365 brings cloud storage into the picture. Users accustomed to saving files locally need a migration path to OneDrive. Deploy the OneDrive sync client, configure Known Folder Move (KFM), and ensure bandwidth can handle the initial sync. Microsoft recommends limiting KFM prompted deployment to 5,000 devices per day and 20,000 devices per week. (learn.microsoft.com)

5. Update channel selection. Microsoft 365 receives continuous updates via servicing channels:

   • Current Channel: Receives updates as soon as they are ready (typically multiple times per month).
   • Monthly Enterprise Channel: One predictable release per month, typically the second Tuesday. Two-month support window per build.
   • Semi-Annual Enterprise Channel: Historically designed for heavily regulated environments, but Microsoft is unifying SAEC into the Monthly Enterprise experience starting with Version 2606 in July 2026. Any servicing plan built around long-lived SAEC assumptions should be revisited now. (learn.microsoft.com)

   This requires active governance — test each update against your macro library, COM add-ins, and third-party integrations before broad deployment. Use the Microsoft 365 Apps readiness dashboard in the admin center to monitor add-in health signals across your tenant.

6. Outlook profile migration. If users have local PST files, those need to be uploaded to Exchange Online mailboxes. PST imports are a common failure point — see the execution section below.

Data Residency and Sovereignty

For government agencies, healthcare organizations, and any entity subject to data residency requirements, the cloud migration path requires explicit attention to where Microsoft stores data:

• Commercial tenants: Data stored in the Microsoft datacenter region selected at tenant creation. Microsoft Advanced Data Residency (ADR) add-on (~$3/user/month) provides contractual guarantees for data-at-rest location for Exchange, SharePoint, OneDrive, and Teams.
• Microsoft 365 GCC: Data stored in US datacenters, FedRAMP Moderate authorized. Suitable for CUI and most state/local government workloads.
• Microsoft 365 GCC High: Data stored in US datacenters with US-person-only admin access, FedRAMP High authorized. Required for ITAR, CJIS, and some DoD workloads.
• Microsoft 365 DoD: Dedicated DoD-only infrastructure, IL5 authorized.
• EU Data Boundary: For organizations subject to GDPR, Microsoft's EU Data Boundary commitment (effective January 2023, expanded in 2024) keeps EU customer data within the EU for core services.

If your LTSC 2021 environment exists specifically because of data sovereignty constraints, verify that the applicable Microsoft 365 cloud boundary meets your regulatory requirements before committing to this path. For some classified or sovereign environments, LTSC 2024 remains the only compliant option.

Deployment Configuration

A minimal Office Deployment Tool configuration for Microsoft 365 Apps:

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

RemoveMSI handles uninstalling older Windows Installer builds during deployment. If you have older Click-to-Run releases, those require explicit removal as well. (learn.microsoft.com)

For Intune-managed devices, the preferred approach is deploying via the Intune admin center:

1. Navigate to Apps > Windows > Add > Microsoft 365 Apps
2. Select the Microsoft 365 Apps for enterprise suite
3. Configure the update channel (Monthly Enterprise recommended)
4. Under Properties, set Remove other versions of Office to Yes
5. Assign to device groups in a staged rollout (pilot → early adopters → broad deployment)

Intune handles the download, installation, and removal of prior versions natively without requiring ODT XML.

Network Bandwidth Considerations

Unlike LTSC 2021, where the Click-to-Run package is deployed once from a local distribution point, Microsoft 365 endpoints continuously pull updates from Microsoft's Content Delivery Network (CDN). A typical Monthly Enterprise Channel update is 200–500 MB per device. For an office with 1,000 devices, that is 200–500 GB of download traffic on patch day. Implement Delivery Optimization (DO) or Microsoft Connected Cache to enable peer-to-peer sharing of update binaries across the local network, reducing WAN consumption by 50–90% in well-configured environments.

Shared and Low-Connectivity Devices

Microsoft 365 Apps support shared computer activation for shared devices (kiosks, RDS/VDI hosts, shared workstations) and extended offline access for up to 180 days for eligible customers with E3/E5 licensing. Both approaches still require a clean Entra identity story, periodic license validation, and manual update handling for long-offline machines. For fully air-gapped networks, LTSC 2024 remains the only viable option. (learn.microsoft.com)

Path 3: Non-Microsoft Alternatives

A complete analysis of options must acknowledge alternatives outside the Microsoft ecosystem:

Google Workspace

• Licensing: Business Starter at $7/user/month, Business Standard at $14/user/month, Business Plus at $22/user/month, Enterprise at custom pricing.
• Strengths: Fully web-native, real-time collaboration built in, no desktop client patching burden, strong in education and media verticals.
• Weaknesses: No native desktop apps (relies on browser or progressive web apps), limited offline capability, poor VBA/macro compatibility (Google Apps Script is a fundamentally different paradigm), OOXML fidelity issues with complex Word/Excel documents, limited adoption in regulated industries due to fewer compliance certifications than Microsoft GCC.
• Migration friction: High. Every Excel macro, Word template, and Outlook workflow needs rethinking. PST import is not native. SharePoint content types have no equivalent.

LibreOffice

• Licensing: Free (open source, MPL 2.0). Enterprise support available via vendors like Collabora (~$3–10/user/year).
• Strengths: Runs on-premises, no subscription, strong ODF support, no vendor lock-in, available on Linux.
• Weaknesses: OOXML rendering fidelity is imperfect for complex documents, no real-time co-authoring in the desktop client (Collabora Online provides web-based co-authoring), limited enterprise management tooling (no Intune-equivalent deployment), no integrated email client (requires Thunderbird or similar), VBA macro compatibility is partial — complex macros will require rewriting.
• Migration friction: Medium for basic document editing workflows. High for organizations with heavy Excel macro estates, Outlook-dependent workflows, or tight SharePoint integration.

When Alternatives Make Sense

Non-Microsoft alternatives are worth evaluating if your organization has minimal macro/add-in dependencies, does not rely on Exchange or SharePoint, and is open to retraining users. For organizations deeply embedded in the Microsoft ecosystem — Active Directory, Exchange, SharePoint, Teams — the migration cost to a non-Microsoft stack typically exceeds the cost of moving to Microsoft 365.

Handling Legacy Dependencies: Macros, Add-ins, and VBA

One of the highest-friction points in an Office LTSC 2021 to Microsoft 365 migration is legacy extensibility. Over years, business units build custom VBA scripts, Excel macros, and third-party COM add-ins to automate their workflows.

Microsoft 365 introduces strict security defaults. VBA macros originating from the internet are blocked by default (controlled via Group Policy: User Configuration > Administrative Templates > Microsoft Office 2016 > Security Settings > Trust Center > VBA Macro Notification Settings, or via Intune's Administrative Templates ADMX profile). Older 32-bit COM add-ins frequently crash the 64-bit architecture of modern Microsoft 365 deployments.

Before initiating a mass deployment, run the Readiness Toolkit for Office add-ins and VBA (downloadable from Microsoft). This tool scans your environment, identifies incompatible macros, and flags add-ins that have not been updated for the cloud-connected architecture. It generates a readiness report categorizing add-ins as "Highly adopted," "Adopted," or "Low/No adoption" with compatibility status for each. Microsoft's App Assure service (available through FastTrack for organizations with 150+ seats) provides free remediation for line-of-business app compatibility — but only if you engage them early enough. App Assure has a published SLA of resolving compatibility issues within 5 business days of receiving a valid submission.

Failing to audit these dependencies guarantees help desk ticket spikes on day one of the rollout.

Document Metadata and Content Types

Another hidden trap involves document metadata. Legacy organizations often rely on custom Document Information Panels (DIP) injected into Word templates. As you migrate files into SharePoint Online, ensuring that legacy metadata maps correctly to modern SharePoint Content Types is a highly technical exercise. If the metadata is stripped during the file transfer, search functionality breaks and compliance retention labels fail to apply. Use the SharePoint Migration Tool (SPMT) or third-party tools like ShareGate to map metadata columns before initiating file transfers.

Decision Framework: LTSC 2024 vs. Microsoft 365 vs. Alternatives

The Compounding 2026 Microsoft EOL Wave

The Office LTSC 2021 end of support does not happen in isolation. The second half of 2026 represents the single densest period of Microsoft product sunsets in the company's history. If your organization runs multiple on-premises Microsoft products, you are facing a compounding migration burden.

For a full breakdown, see our Software End of Life 2026 calendar and the Microsoft 2026 End-of-Support Timeline. If browser-based Office rendering is part of your architecture, our Office Online Server retirement guide covers that separate cliff.

The practical problem is resource contention. Every organization running on-premises Microsoft infrastructure needs migration capacity in the same window. Consultants, deployment engineers, and cloud architects are finite resources.

Treating the Office desktop client as an isolated upgrade is a strategic error. When Outlook 2021 loses support, your on-premises Exchange environment is likely already unsupported. When Word 2021 loses support, the on-premises SharePoint server hosting its files is also hitting the end of the line. Piecemeal migrations lead to broken dependencies, duplicate data silos, and extended downtime.

Migration Timeline Benchmarks

Based on typical enterprise migration patterns, here are realistic timeline estimates:

These timelines assume the Entra ID infrastructure is already in place for M365 migrations. Add 2–6 weeks if Entra ID Connect must be set up from scratch. Add 4–8 weeks if concurrent Exchange Online migration is included. PST remediation alone can add 2–4 weeks for organizations with significant PST sprawl.

Working backward from October 13, 2026: A 1,000-seat Microsoft 365 migration that takes 16–24 weeks should begin no later than April–June 2026 to include buffer for complications. Organizations that start in Q3 2026 face compressed timelines and higher risk.

How to Execute Your Microsoft Migration Without Downtime

The physical installation of Microsoft 365 Apps via Intune or Microsoft Endpoint Configuration Manager (MECM) is the easy part. The real friction lies in the data layer.

Inventory the Ugly Parts First

Do not just count Office installs. Count COM add-ins, macro-heavy Excel models, Project and Visio variants, shared computers, RDS/VDI hosts, local PSTs, and Publisher files. Microsoft's inventory service in the Microsoft 365 Apps admin center can surface older Office builds, installed add-ins, and macro-enabled files. Some Office, Project, and Visio combinations cannot coexist when Click-to-Run versions overlap or when version and install-technology mixes are unsupported. (learn.microsoft.com)

Treat Outlook as a Data Migration Problem

If users have years of PST sprawl, Outlook is a data migration project, not a software reinstall. Some PSTs are 20+ GB. Some are corrupt. Some contain data subject to legal hold. You need to inventory, validate, and plan the ingest before touching a single mailbox.

Microsoft's import service supports network upload or drive shipping, but the constraints matter:

• Import throughput is roughly 24 GB per day via network upload
• Items over 150 MB are skipped
• Nested folders over 300 levels are not supported
• PST files over 20 GB should be split before upload for performance
• Old imported mail can be purged immediately if mailbox retention settings say it has already aged out
• Drive shipping is available for bulk imports over 100 GB (Microsoft provides encrypted hard drives)

(learn.microsoft.com)

When moving off on-premises Exchange alongside your Office upgrade, data velocity becomes the primary bottleneck. Exchange Online enforces strict throttling limits on ingestion APIs (EWS and Microsoft Graph). Manually migrating terabytes of mailboxes can take months if you hit concurrency limits. Engineering a migration plan requires batching users (typically 50–100 users per batch), pre-staging data, and using multi-threaded ingestion scripts to hit a single weekend maintenance window.

Roll File Migration and OneDrive Into the Same Plan

Office client deployment and file migration should be one workstream. Deploy the OneDrive sync client, configure Known Folder Move, and account for the destination-side limits:

• SharePoint and OneDrive cap decoded file paths at 400 characters
• Individual files max at 250 GB
• Microsoft recommends staying under about 300,000 synced files per library or site for performance
• OneDrive storage defaults to 1 TB per user (expandable to 5 TB via admin center, further by support request)

Local file shares with decades of Word and Excel documents must be moved to SharePoint Online. This requires mapping legacy NTFS permissions to modern SharePoint site permissions — a process that typically requires a permissions audit, a new governance model, and new Data Loss Prevention (DLP) policies and sensitivity labels.

Watch the Edge Cases

Legacy Access databases often act as shadow IT. Moving to the cloud requires auditing these databases and determining whether they should be rebuilt in Power Apps, migrated to Dataverse, or moved to Azure SQL. Microsoft Access continues to be included in Microsoft 365 Apps but is on a maintenance-only trajectory with no new features planned.

If this Office move is part of an acquisition, divestiture, or tenant split, do not assume Microsoft-native cross-tenant tooling behaves like a classic staged migration. Microsoft's native OneDrive cross-tenant move is one-and-done: no incremental or delta passes, blocked by legal holds, fails if OneDrive exceeds 5 TB or 1 million items, not supported for GCC High or DoD, and requires a separate migration add-on license. (learn.microsoft.com)

Silent deployments with FORCEAPPSHUTDOWN during maintenance windows are the standard approach for the client rollout itself, but you need to coordinate this across every device in the fleet. If you deploy Microsoft 365 Apps while users have documents open, the process will fail or produce a broken state. Schedule deployments during off-hours and use Intune's deployment scheduling or MECM maintenance windows to enforce this.

Rollback Plan for Microsoft 365 Deployments

If the M365 deployment fails mid-rollout:

1. Keep the LTSC 2021 ODT source package available on a network share or in your Intune app library for the duration of the rollout
2. If a device fails, uninstall M365 Apps via setup.exe /uninstall O365ProPlusRetail or SaRA
3. Reinstall LTSC 2021 from the preserved source
4. Do not delete KMS/MAK activation records until the full rollout is validated
5. Set a rollback decision gate: if >5% of pilot devices experience critical issues, halt the broad deployment and triage

FastTrack vs. Execution Partner

For organizations with 150 or more licenses, Microsoft's FastTrack service provides free remote guidance for the migration to Microsoft 365. Tenants with 500+ seats can get help migrating data and email. (microsoft.com)

But FastTrack is advisory. It provides guidance, architecture documentation, and best practices. FastTrack will tell you how to map your data, but it will not write the scripts, handle the API rate limits, resolve corrupt PSTs, or manage a coordinated Exchange + SharePoint + Office cutover. If your real blockers are PST triage, long-path remediation, SharePoint information architecture changes, legacy add-ins, or hybrid identity cleanup, you need an execution layer, not a guidance layer.

Read more about that distinction in our FastTrack vs. migration partner guide.

What You Should Do This Week

If you have not started, here is the triage sequence:

1. Inventory. Run a scan of every device to identify Office versions, Windows versions, add-ins, Visio and Project installs, shared-computer cases, PST archives, and Publisher files. Microsoft's Readiness Toolkit can identify macro compatibility issues in the same pass.
2. Decide on your path. LTSC 2024 or Microsoft 365, segmented by user group. Some organizations will legitimately need both — LTSC 2024 for air-gapped devices and Microsoft 365 for connected users. Do not defer this decision past June 2026 — deployment lead times for Entra ID setup, licensing procurement, and staged rollouts will eat the remaining calendar.
3. Pilot identity, licensing, and deployment. Test Entra ID, license assignment, deployment tooling, update channels, and coexistence rules for Visio, Project, and add-ins with a small pilot ring (5–10% of users) before touching the broad user base.
4. Run data discovery. PSTs, OneDrive known folders, long SharePoint paths, retention edge cases, Publisher file conversion, and any tenant-to-tenant file moves need to be scoped as part of the same migration workstream.
5. Identify your full EOL exposure. Office LTSC 2021 is probably not the only Microsoft product on your EOL list. Map everything reaching end of support in 2026 and plan one coordinated migration rather than five independent projects.
6. Engage resources now. Whether that is Microsoft FastTrack (advisory), an internal deployment team, or a migration partner (execution), the window is closing. Consultant availability in Q3 2026 will be scarce given the volume of concurrent Microsoft EOL migrations across the market.

The October 13 deadline is fixed. Microsoft has been explicit: there will be no extension and no ESU program.

Working with ClonePartner

At ClonePartner, we handle the full Microsoft migration stack simultaneously — mailbox migrations, SharePoint document moves, OneDrive rollouts, and Office deployments in one coordinated motion. We execute the technical work, not just advise.

Having completed over 1,500 migrations, we have built tooling specifically designed to work within Microsoft's API throttling limits for large-scale data moves. We specialize in regulated industries — healthcare, finance, and government — where data integrity and compliance continuity during migration are non-negotiable requirements.