Microsoft Lens will stop accepting new scans on December 15, 2025, and the mobile scanning app that tens of millions of users have relied on for nearly a decade will vanish from app stores a month earlier, Microsoft has confirmed. The company is consolidating Lens into the Microsoft 365 Copilot app, where core scanning and OCR functions live on inside a new “Create → Scan” flow. The move preserves the basics—capture, auto-crop, cloud save—but drops several features that have made Lens a linchpin in workplaces, classrooms, and accessibility workflows, including direct OneNote and Office exports, business-card import, and integrated Immersive Reader support. The phased retirement begins September 15, 2025, giving organizations roughly six months to plan a migration that, for many, will require new workflows, third-party tools, or automation workarounds.

A Phased Shutdown on a Fixed Schedule

Microsoft has published a detailed retirement timetable, and it leaves no room for procrastination. The process kicks off on September 15, 2025, when the company begins decommissioning work. By mid-October, new installs of Microsoft Lens will be blocked, meaning managed app catalogs must be updated and users should already have alternatives in place. On November 15, the app will be removed from both the Apple App Store and Google Play. The final and hardest deadline is December 15, 2025: creating new scans inside Microsoft Lens will be disabled. After that date, the app remains a read-only archive—users can view existing scans as long as the binary stays on their device, but no new captures are possible.

These dates are not suggestions. Microsoft’s internal advisory frames them as migration milestones, and administrators who treat them as soft guidance risk data loss and user disruption. The message is clear: export any locally stored scans before December 15, and have a replacement scanning workflow ready by mid-October at the latest.

What Moves to Copilot—and What Stays Behind

The migration path runs through the Microsoft 365 Copilot app, available on iOS and Android even without a paid Microsoft 365 subscription. Inside the app, tapping the menu icon and selecting Create → Scan launches a scanner that preserves the core capture functions most users depend on: document, receipt, and whiteboard scanning with optical character recognition (OCR), auto-cropping, deskewing, and basic image cleanup. Scans can be saved to OneDrive and accessed later through Copilot’s “My Creations” hub.

For cloud-first users who already store scans in OneDrive, Copilot covers the day-to-day basics. But Microsoft explicitly lists several Lens conveniences that are absent at launch:

  • No direct save or export to OneNote, Word, or PowerPoint from the scan UI
  • No business-card scan → OneNote contact import flow (the one-tap business-card convenience is gone)
  • No integrated Read-aloud or Immersive Reader support
  • Local file access caveats: cloud-saved Lens captures appear in Copilot’s My Creations, but locally stored scans on devices may not surface automatically. On Android, Copilot may require broad “All Files Access” permission to find them; on iOS, sandboxing limits automatic migration.

These gaps are material. Educators who used Lens to scan pages and then read them aloud with Immersive Reader face an accessibility regression. Business teams that relied on one-tap business-card capture into OneNote lose a frictionless networking tool. Anyone whose workflow depended on shooting a whiteboard straight into a Word document or PowerPoint deck must now adopt a two-step process: scan to OneDrive, then manually import.

Immediate Consequences for Users and IT

For individual users

You can continue using Microsoft Lens to view old scans as long as the app stays installed, but you must export important locally stored scans before December 15, 2025. After that, the Copilot scanner is available to anyone with the Microsoft 365 Copilot app, but expect extra steps for scenarios that were previously single-tap. If you rely on business-card import, you either find a third-party app or build a Power Automate flow that scoops new OneDrive scans into your contacts list.

For organizations and administrators

Microsoft’s Message Center advisory says no mandatory admin action is required, but that is misleading. The retirement is a migration project. IT teams must inventory Lens usage, identify who depends on the now-missing features, export locally stored scans, update internal documentation, and train users on new workflows. Device management policies need an overhaul: blocklists and app catalogs must remove Lens and, where applicable, add the Copilot app as an allowed or managed application. If your Android estate requires Copilot to surface local Lens content, you must weigh the security implications of granting “All Files Access”—a permission that conflicts with many enterprise mobile threat defense baselines. Most organizations will be better served by forcing a cloud-first export strategy rather than opening that door.

Accessibility Regressions and Compliance Risks

Lens’s retirement narrows the accessibility surface for scanning. Immersive Reader and Read-aloud were built directly into the Lens experience, offering dyslexic and visually impaired users a seamless way to have scanned text spoken aloud or displayed in a distraction-free format. Copilot’s scanner offers no equivalent today. Until Microsoft restores parity, accessibility-dependent users need a fallback. That might mean keeping Lens installed on a dedicated device past December 15 as a viewer, or adopting a third-party scanner that supports text-to-speech.

The consolidation also tightens the link to cloud storage. Lens allowed users to keep scans purely local, but Copilot’s scanner encourages OneDrive sync. That is often desirable for backup and cross-device access, yet it introduces data governance considerations. Sensitive scans that previously stayed on-device will now flow through OneDrive and SharePoint, making them subject to data loss prevention (DLP) policies, retention rules, and eDiscovery. Organizations must audit where such scans are stored, apply appropriate policies, and log migration activity. Local-only scans that never leave the device remain brittle—if the app is deleted or the device factory-reset after December 15, they are gone.

Alternatives: Scanning Apps That Can Replace Lens Now

If Copilot’s gaps are dealbreakers for your workflows, several third-party apps can fill the void. None replicate every Lens feature simultaneously, so choose based on your top priorities.

  • Adobe Scan / Adobe Acrobat mobile: Robust OCR, multiple export formats, strong PDF processing, and annotation tools. Best for users who need consistent PDF quality and professional-grade exports. The trade-off: an external vendor and Adobe’s own licensing model.
  • Google PhotoScan / Google Drive scanner: Straightforward capture tied to Google Drive. Widely available and simple for cloud users, but poorly suited for Microsoft-centric organizations that need OneNote integration.
  • TurboScan / Tiny Scanner: Lightweight, fast, one-tap PDF generation. Excellent for receipts and quick document capture. They lack enterprise connectors and accessibility features, making them a better fit for individual users than regulated teams.
  • OneDrive built-in scanner: If you already store scans in OneDrive, the built-in scanner keeps everything inside Microsoft’s cloud without needing the Copilot app. Still, it does not solve the missing direct-export problem.

Each alternative introduces its own vendor-management and compliance angle. Evaluate against organizational data-handling policies before deploying.

A Practical Migration Plan: 8 Steps to Avoid Disruption

Use this checklist to move from Lens to Copilot—or your chosen alternative—with minimal friction.

  1. Inventory Lens usage now. Identify who uses the app and for what: OneNote exports, business-card import, receipt capture, accessibility reading, whiteboard snaps.
  2. Export locally stored scans before Dec 15, 2025. Push device-local scans to OneDrive or another managed repository. Audit the exported content to confirm no sensitive data was left behind.
  3. Test Copilot’s Create → Scan flow immediately. Install the Microsoft 365 Copilot app, rehearse the scan-to-OneDrive pipeline, and identify where one-tap exports are missing.
  4. Implement stopgap automations. Use Power Automate to move new OneDrive scans into OneNote or Word if direct saves are essential. For example, a flow can watch a folder and auto-import each scan into a designated OneNote section.
  5. Address accessibility workflows. Work with accessibility teams to test Copilot’s scanner with screen readers and text-to-speech. If it falls short, provision a third-party scanner with Read-aloud support or hold back Lens on dedicated devices.
  6. Update policies and training. Refresh helpdesk scripts, internal documentation, and user guides. Communicate the timeline repeatedly: at least two reminders before each key date (Sept 15, mid-Oct, Nov 15, Dec 15).
  7. Decide on Android file permissions. If local Lens content must surface in Copilot, weigh the risk of granting “All Files Access” versus migrating everything to OneDrive first. In most enterprises, cloud migration is the safer governance choice.
  8. Maintain a fallback window. Keep Lens installed on a few critical devices as a read-only archive until December 15, and train users to export what they need before that date.

How to Use Copilot’s Scanner Today

Getting started takes under a minute:

  • Download and install the Microsoft 365 Copilot app from your device’s app store.
  • Open the app, tap the three-line menu icon (top left), choose Create, then Scan.
  • Frame the page, tap the shutter, adjust crop and rotation on the preview, and tap the checkmark to save.
  • Choose to save locally or sync to OneDrive. OneDrive sync lets you access scans across devices and surface them in Copilot’s My Creations.

Remember: this flow currently does not offer one-tap export to OneNote, Word, or PowerPoint, nor business-card import. Plan to use OneDrive as an intermediate stop if you need those outputs.

Strategic Takeaways: A Consolidation with Immediate Trade-offs

Microsoft’s decision to fold Lens into Copilot is a textbook product-consolidation play. It reduces maintenance overhead, concentrates engineering resources on a single scanning surface, and positions capture as a step inside AI-first workflows. In the future, a scanned page could be instantly summarized, turned into an action item, or queried through generative prompts—all from within the Copilot app. That vision carries real productivity potential.

But the immediate cost is operational. Until Microsoft restores direct Office exports, business-card import, and immersive reading, many users will experience the transition as a downgrade. The company has not published a timeline for parity, and no commitments exist beyond a vague promise of future investment. Admins should treat feature restoration as possible, not guaranteed, and plan accordingly.

For the majority of cloud-first users who simply need to digitize a receipt or whiteboard, Copilot’s scanner will likely suffice. For power users, educators, and regulated environments, this is a migration project that demands attention now. Inventory usage, export local scans, validate Copilot or a third-party tool against your compliance and accessibility requirements, and be ready to deploy automations where direct saves used to live. The December 15 deadline for new scans is the single most important anchor: treat it as the moment your migration must be complete or safeguarded.

Microsoft’s consolidation makes sense for long-term product focus, but it is not a zero-friction swap. The pragmatic move is to migrate deliberately, protect what worked, and use the next six months to ensure that December 16, 2025, does not find your users stranded without the scanning muscle they count on.