Microsoft has drawn a hard line under its decade-old Microsoft Lens scanning app, setting a definitive retirement timeline that will disable new scans by December 15, 2025. The replacement—the scanning capability inside the Microsoft 365 Copilot mobile app—preserves core OCR functions but leaves behind several staple workflows, including direct OneNote export, business card ingestion, Read Aloud text-to-speech, and Immersive Reader integration. For organizations and power users, the next 90 days demand a careful migration plan to avoid losing locally stored documents and breaking accessibility-dependent routines.

Originally launched as Office Lens in 2015, Lens grew into one of Microsoft’s quiet successes: a free, lightweight mobile scanner that turned photos of whiteboards, receipts, pages, and business cards into clean PDFs, Word, or PowerPoint files with built-in OCR, cropping, and color correction. Over the years it tallied tens of millions of downloads—TechRadar cites over 92 million lifetime installs, though Microsoft itself hasn’t publicly confirmed that figure—earning 4.5+ star ratings on both iOS and Android for its reliability and zero cost.

The Move to Copilot: Consolidation Over Continuity

Microsoft’s decision mirrors a broader push to consolidate point utilities under the Copilot umbrella. By channeling scanning into the Microsoft 365 Copilot app, the company can concentrate development resources on a single AI-enabled surface, eventually layering generative features, multimodal reasoning, and automation on top of document capture. For casual users who only need quick OCR and OneDrive storage, the transition may be nearly seamless. But for those who depended on Lens’s niche conveniences, the migration is less a feature upgrade than a feature gap.

The Official Timeline: Three Hard Dates to Bookmark

Microsoft’s retirement plan is both deliberate and phased, giving IT teams and individuals concrete milestones:

  • September 15, 2025 – Retirement process begins; Microsoft starts the decommissioning phase.
  • Mid-October 2025 – New installs of Microsoft Lens are disabled on Android and iOS. Administratively pushed installations stop working.
  • November 15, 2025 – Microsoft Lens is removed from the Apple App Store and Google Play Store entirely.
  • December 15, 2025 – Creating new scans inside Microsoft Lens is disabled. Existing scans already saved remain viewable within the app.

These dates were issued through Microsoft 365 Message Center advisories and reiterated in a support page; they are firm planning anchors, not loose targets. After December 15, any left-behind local scans that haven’t been exported will be trapped without a direct path to cloud storage.

What Copilot Keeps—and What It Breaks

Microsoft 365 Copilot’s scanning experience retains the fundamental capture pipeline: document detection, basic OCR, automatic cropping/deskew, and saving directly to OneDrive. For cloud-first users, this covers the majority of day-to-day needs.

However, Microsoft explicitly lists several Lens features that are not available in Copilot at launch:

  • Direct saving or export to OneNote, Word, or PowerPoint from within the scan interface.
  • Business card scanning with automatic OneNote contact import.
  • Read Aloud text-to-speech and Immersive Reader accessibility tools.
  • Automatic surfacing of locally stored Lens scans inside Copilot (unless manually migrated and, on Android, often requiring “All Files Access” permissions).

What remains in Copilot is the core: scanning for documents, whiteboards, and receipts, with cloud-saved outputs accessible via Copilot’s “My Creations” or equivalent. That imbalance—core functions preserved, convenience and accessibility workflows severed—is where the real operational pain resides.

The Accessibility Gap: More Than an Inconvenience

For users who rely on Read Aloud or Immersive Reader, the loss of these functions from the scanning app is a critical regression. Microsoft Lens baked assistive tools directly into its viewer; Copilot’s initial scan flow offers no comparable integrated read-aloud or reading mode. In workplaces subject to disability accommodation requirements or legal accessibility policies, that gap is not a minor UX nit—it’s a compliance event. Organizations must now document how they will sustain equivalent accommodations, either through multi-step manual workarounds (scan to OneDrive, then open in Word or OneNote with Immersive Reader) or through third-party tools.

Numbers and Claims: How Big a User Base Is Really Affected?

Several media outlets have quoted download figures for Microsoft Lens. TechRadar reports over 92 million lifetime downloads, and Android store trackers frequently place Lens in the tens of millions of installs. However, those high-precision numbers haven’t been independently verified by Microsoft in its public support documentation. Treat the 92 million figure as directional, not confirmed, until Microsoft publishes an official count. What’s verifiable is the app’s consistently high rating across platforms and its deep embedding in academic, field-service, and small-business workflows.

Practical Migration Guide: What to Do Before December 15

Immediate Individual Steps

  1. Inventory your usage: Identify whether you use Lens for OneNote exports, business-card capture, Immersive Reader, or local-only scanning.
  2. Export local scans: Open Microsoft Lens and ensure any scan stored only on the device is exported to OneDrive, SharePoint, or another managed cloud location. On Android, this may require granting All Files Access to the Copilot app to surface those files later—evaluate against security policies.
  3. Pilot Copilot: Download the Microsoft 365 Copilot app, sign in with your organizational account, and test the Create → Scan workflow. Note any missing steps you previously relied on.
  4. Communicate: Share key dates and step-by-step migration instructions with team members at least twice before each milestone.

For IT Administrators and MDM Teams

  • Update managed app catalogs: Remove Microsoft Lens from recommended or required apps ahead of mid-October 2025 to avoid new install attempts.
  • Align governance policies: Ensure that retention, DLP, and eDiscovery rules cover OneDrive and SharePoint locations where scans will now land. Local-only scans are a discovery blind spot until exported.
  • Address accessibility: Conduct an impact assessment, identify users who depended on Lens’s accessibility features, and document temporary accommodations. If legal accommodation processes are in play, begin them now.
  • Build automations: Use Power Automate to watch a designated OneDrive folder and move new PDFs into OneNote, Word, or SharePoint automatically—partially replicating Lens’s one-step flows. For business-card ingestion, consider third-party contact capture apps or scripting an extract-and-convert pipeline using Azure Cognitive Services or Google Cloud Vision.

Who Wins and Who Loses in This Transition

Immediate winners are the cloud-first, casual users who only ever needed OCR-and-upload: their workflow in Copilot will be nearly identical, and they gain a path to future AI-driven processing (classification, summarization, extraction).

Users at risk include:
- Students, researchers, and knowledge workers who relied on one-tap exports to OneNote for lecture notes, research snapshots, or project documents. Until Copilot gains that direct integration, they face extra steps or broken habits.
- Field and sales teams capturing business cards or receipts on the fly. Without a quick import path, these teams need to adapt processes or adopt third-party alternatives immediately.
- Regulated industries (fintech, healthcare, legal) where document capture is the front door of compliance pipelines. Losing Lens’s simple, reliable capture layer can disrupt KYC onboarding, expense reporting, and receipt ingestion—creating both operational risk and an opportunity for enterprise-grade scanning vendors.

Alternatives: If Copilot Can’t Fill the Gap

If Copilot’s missing features are deal-breakers, consider these replacements, each with their own trade-offs:

  • ABBYY FineReader / ABBYY mobile – Enterprise-grade OCR with table extraction, multi-format export, and high accuracy for structured documents. Well-suited for invoice processing and form extraction, but comes with licensing costs.
  • Adobe Scan / Adobe Acrobat mobile – Mature scanning with strong OCR, PDF editing, and integration into e-sign workflows. Exports to Word, Excel, and PowerPoint are behind a subscription.
  • Smallpdf or other cloud-first PDF tools – Quick OCR plus compression and team collaboration. Simpler than ABBYY but may lack the granular accuracy needed for business cards or complex receipts.
  • Specialized SDKs (ABBYY Cloud OCR, Google Cloud Vision, Azure Form Recognizer) – For organizations that need programmatic, high-accuracy ingestion pipelines at scale. Requires development effort but yields full control over extraction and storage.

Evaluate each alternative against your typical documents (receipts, business cards, multipage forms), test mobile UX, and verify enterprise connectors (OneNote, SharePoint, CRM) before committing.

Governance, Privacy, and Security Considerations

Migrating scans to cloud storage simplifies backup, retention, and eDiscovery—but it also changes where DLP and information-protection policies apply. Double-check that retention labels and eDiscovery holds are extended to the OneDrive/SharePoint locations where Copilot saves scans. Granting Copilot “All Files Access” on Android to surface legacy Lens scans may violate least-privilege policies on managed devices; weigh the risk and prefer cloud migration paths wherever possible. Finally, any third-party scanning app you onboard adds a vendor risk surface—verify encryption in transit and at rest, data residency, and contractual protections to ensure PII doesn’t leak outside approved storage.

Strategic Analysis: Consolidation vs. User Continuity

Microsoft’s product rationalization makes strategic sense. Maintaining a standalone scanner is overhead when the same core capability can be folded into the Copilot platform, where AI features like automatic document classification, summarization, and conversational querying can eventually add value. For millions of users, the switch will be invisible or a net positive.

Yet the trade-offs are tangible. Lens’s strength was its quirky, frictionless conveniences: one tap to send a whiteboard photo to OneNote, one tap to turn a business card into a contact, an integrated read-aloud button for a scanned textbook page. Removing those without clear parity in the replacement creates friction, raises accessibility risks, and imposes a migration burden. The real test will be whether Copilot’s scanning experience rapidly regains those capabilities or whether organizations cement new workflows with third-party tools that may never return.

A 90-Day Action Plan

  • By Early September 2025: Inventory critical Lens-dependent workflows. Identify which users rely on OneNote export, business card capture, or accessibility features.
  • Export all local scans to managed cloud storage (OneDrive/SharePoint). Validate that retention and eDiscovery policies are in place.
  • Pilot Copilot scanning with a small group of frontline and power users. Document gaps and test workarounds (Power Automate flows, manual export steps).
  • August–October: Update helpdesk scripts, internal knowledge articles, and user-facing guidance. Send at least two reminders ahead of each milestone.
  • Map accessibility accommodations now. If legal accommodations are required, establish a temporary process (scan → OneDrive → open in Word with Immersive Reader) and communicate it to affected users.
  • Evaluate third-party alternatives where Copilot cannot meet business requirements. Run a quick OCR accuracy bake-off on your typical document types, and confirm data-residency compliance.

Microsoft Lens’s retirement is a calculated bet that an integrated, AI-first scanning experience will eventually outshine a dedicated utility. For organizations and individuals, the key to weathering that bet is preparation: export your scans, pilot Copilot, and build bridges for the features that didn’t survive the transition. The window is closing—by December 15, the app that millions relied on will stop capturing new memories, and those who haven’t moved will be left staring at a static gallery of old scans.