Microsoft’s long-standing document scanning app, Microsoft Lens, is heading for retirement in a phased rollout that begins September 15, 2025, and will leave users unable to create new scans after December 15, 2025. The tech giant is steering its mobile users toward the scanning feature inside the Microsoft 365 Copilot app, but that solution arrives with immediate gaps: direct exports to OneNote, Word, and PowerPoint are nowhere to be found, and the Immersive Reader and text-to-speech accessibility tools that millions relied on are absent at launch.

According to a Microsoft Support document, “The Microsoft Lens app will be retired from iOS and Android devices starting September 15, 2025. After November 15, Microsoft Lens will no longer be supported. Users can continue to use the scanning capability in the app until December 15, 2025. After that date, creating new scans in the Lens app will no longer be possible. However, users can continue to access their previous scans as long as the app remains installed on their device.”

The Retirement Timeline

The phase-out unfolds across multiple dates:

  • September 15, 2025: Retirement process begins. Microsoft will start winding down the app, though existing users can still create new scans.
  • Mid-October 2025: New app installations are disabled, preventing new users from downloading Lens.
  • November 15, 2025: Microsoft Lens is removed from the Apple App Store and Google Play Store entirely. Support officially ends.
  • December 15, 2025: The final cutoff — users can no longer create new scans within the Lens app. Previously saved scans remain accessible as long as the app stays installed, but no new captures are possible.

This timeline gives users and organizations a roughly three-month runway to migrate to Copilot or alternative tools. Microsoft’s messaging is clear: transition to the Microsoft 365 Copilot mobile app for scanning. Inside Copilot, users can access existing Lens-created scans via the Create > My Creations path, and future scans should be performed using the Create > Scan workflow.

What Copilot Offers — and What It Doesn’t

The Copilot app covers the core scanning use cases: basic document capture, OCR (optical character recognition), automatic cropping and cleaning, and saving scans to OneDrive. But several features that made Microsoft Lens so popular are missing at launch.

Features available in Microsoft 365 Copilot for scanning:
- Basic document capture with auto-cropping and shadow removal
- OCR to extract text from images
- Saving scans directly to OneDrive
- Accessing past scans from Lens under “My Creations”

Microsoft Lens features not yet in Copilot:
- Saving scans directly to OneNote, Word, or PowerPoint
- Business card scanning with automatic save to OneNote contacts
- Read-out-loud text-to-speech and Immersive Reader integration

These gaps hit everyday productivity workflows hard. For example, educators and students who frequently scanned whiteboards or notes directly into OneNote must now use a two‑step process — scan to OneDrive, then manually import into OneNote. Business card scanning, which seamlessly created contacts in OneNote, is completely absent. And the accessibility features that aided users with visual impairments or reading disabilities are simply gone, replaced by nothing equivalent in Copilot.

Why Microsoft Is Making the Move

The retirement fits a broader pattern of consolidation under the Copilot brand. Microsoft is moving away from standalone productivity utilities and funneling users into a single AI‑powered hub. By embedding scanning within the Microsoft 365 Copilot app, the company can focus development resources on one application, reduce maintenance overhead, and enrich the Copilot ecosystem with future AI enhancements — such as conversational or multimodal AI applied to scanned content.

From a product strategy standpoint, it makes sense. But the short‑term cost is real user friction. Long‑time Lens users, who gave the app some of Microsoft’s highest mobile ratings, suddenly face choppier workflows and lost features. As independent outlets like Thurrott.com note, the move turns a simple, beloved utility into a component of a much larger app, with an uncertain timeline for restoring the missing conveniences.

Impact on Users: OneNote and Accessibility at Risk

Two groups are particularly affected: OneNote‑centric workers and users dependent on accessibility features.

OneNote workflows disrupted: For years, Lens offered a one‑tap path to scan a document, whiteboard, or receipt directly into a OneNote notebook. With that gone, users must either scan to OneDrive and then insert into OneNote manually, or adopt a third‑party app that still supports the direct pipeline. The extra clicks matter in fast‑paced environments like classrooms, field service, and meetings.

Accessibility broken: Lens included built‑in Immersive Reader and read‑aloud capabilities, making it a vital tool for people with dyslexia, low vision, or other reading challenges. Copilot’s scanner does not offer these features at launch. For organizations obligated to provide accessible tools, this gap could become a legal and ethical pain point unless Microsoft adds them quickly.

Local scan headaches: On iOS, local scans stored only on the device are not visible in Copilot unless manually uploaded to OneDrive. On Android, Copilot requires “All Files Access” permission to surface locally saved Lens scans — a broad permission that many enterprise security policies prohibit. Users who relied on offline scanning must now export everything to cloud storage before December 15, 2025, or risk losing easy access.

For IT Admins: A Migration Checklist

Microsoft’s Message Center advisory (MC1131064) states no mandatory admin action is required, but savvy IT teams will act to prevent user confusion and support tickets. Below is a practical checklist:

  1. Inventory Lens usage: Identify which employees use Lens and what workflows they depend on — direct OneNote exports, business cards, local storage, etc.
  2. Communicate the timeline: Notify users immediately and send reminders ahead of each key date (Sept 15, mid‑October, Nov 15, Dec 15). Include clear steps for exporting local scans.
  3. Pilot the Copilot scanner: Deploy Microsoft 365 Copilot to a test group, including accessibility users, and document the gaps. Verify that scan routing complies with data‑loss prevention (DLP) policies.
  4. Update MDM and app catalogues: Remove Lens from managed app inventories after November 15. Add Copilot if not already deployed. Plan for the removal of installation policies.
  5. Design workarounds: For missing OneNote and accessibility features, consider temporary solutions like Power Automate flows to move scans from OneDrive to OneNote, or evaluate third‑party scanning apps that maintain compliance.
  6. Address data governance: Auditing where sensitive scans are stored becomes critical. Copilot nudges users toward cloud storage, which is better for backup and compliance but also changes data residency and access models. Review your DLP and retention policies for OneDrive/SharePoint.

Alternatives and Workarounds

If the Copilot transition feels premature for your needs, several options exist:

  • Keep using Microsoft Lens until December 15, 2025. Export all important local scans to OneDrive or SharePoint before that date.
  • Adopt a third‑party scanning app. Many apps on the market still offer direct OneNote saving, Immersive Reader‑style features, or better accessibility support. Test them against your governance requirements.
  • Automate the two‑step flow. Use Power Automate Desktop or cloud flows to watch a OneDrive folder for new scans and automatically import them into a designated OneNote notebook or Word template.
  • Escalate feature requests. Submit feedback through the Microsoft 365 portal and encourage users to do the same. The more Microsoft hears about the accessibility and OneNote gaps, the higher the chance they prioritize restoring them.

The Bigger Picture

This consolidation is a textbook trade‑off between product focus and user friction. Microsoft gains a unified AI surface, faster iteration, and a stronger Copilot brand. Users and IT departments, however, inherit a migration that breaks several cherished workflows.

The risk of vendor lock‑in deepens as scanning becomes tethered to the Microsoft 365 ecosystem. For organizations already concerned about over‑reliance on Microsoft, losing a standalone, free‑form tool like Lens is a reminder to keep exit strategies viable.

Accessibility advocates and enterprise compliance teams will watch closely to see whether Copilot regains the missing features before Lens’s final shutdown. If months pass with no Immersive Reader or OneNote export, Microsoft may face backlash — and users may simply choose simpler, more dedicated scanning tools.

For now, the advice is clear: treat the September 15 – December 15, 2025 window as an active migration runway. Export those local scans, pilot Copilot, and line up the backups. Microsoft’s Copilot scanning will almost certainly improve, but whether it can recapture the no‑fuss reliability of Microsoft Lens remains an open question.