Microsoft's popular Lens mobile scanning app is getting the axe, and the clock is ticking for millions of users. The company announced that Lens will begin its retirement on September 15, 2025, with full discontinuation by December 15, 2025. That means only a few months remain to migrate scanning workflows before the app stops working for new captures.

Lens, originally launched as Office Lens in 2015, became a staple for anyone needing to digitize documents, receipts, whiteboards, and business cards on the go. Its simplicity and seamless integration with OneNote, OneDrive, Word, PowerPoint, and Excel earned it a loyal following. On Android alone, the app has been installed over 50 million times, with an average rating of 4.8 out of 5. On iOS, it holds a 4.8–4.9 rating from roughly 135,000 reviews. But now, Microsoft is pushing users toward the Microsoft 365 Copilot app, where it plans to consolidate scanning features.

The move, while framed as a strategic consolidation, has left many users concerned about missing features and data migration hurdles. The three-phase retirement timeline is non-negotiable, and IT administrators and individual users alike need to act now to avoid disruptions.

Three Deadlines Every Lens User Must Know

Microsoft has set a clear, phased schedule for the Lens shutdown:

  • September 15, 2025: The retirement process officially begins. Microsoft will start transitioning users away, though the app will still function.
  • November 15, 2025: Lens will be removed from both the Google Play Store and Apple App Store. No new downloads will be possible after this date.
  • December 15, 2025: The ability to create new scans within the Lens app will be disabled. Existing scans will remain viewable as long as the app stays on the device, but capturing new content will stop entirely.

These dates come straight from Microsoft’s support documentation and the Microsoft 365 Message Center advisory (MC1131064). They are hard deadlines, not suggestions.

What Microsoft Lens Did So Well

For nearly a decade, Lens excelled at turning physical documents into crisp, editable digital files. Its key features included:
- Quick scanning of documents, receipts, whiteboards, and business cards.
- Optical character recognition (OCR) that outputted directly into Word, PowerPoint, Excel, PDF, and images.
- Built-in filters to enhance text clarity, adjust lighting, and despeckle images.
- Direct save to OneNote, OneDrive, and other cloud services.
- Accessibility features like Immersive Reader and read-aloud text-to-speech.

These capabilities made Lens indispensable in classrooms, offices, and field settings. It was a rare gem: a free, no-subscription utility that did its job without bloat.

Enter Copilot: The Designated Successor, but with Gaps

Microsoft’s recommended replacement is the Microsoft 365 Copilot mobile app. The app includes a “Create → Scan” flow that can capture documents and save them to the cloud. However, as the official retirement guidance openly acknowledges, several popular Lens features are missing from Copilot’s scanning experience:

  • No direct save to OneNote, Word, or PowerPoint: You can scan to PDF or images and then upload to OneDrive, but the seamless export of editable Office formats is gone.
  • No business card scanning: Lens could extract contact details and save them as vCards or OneNote business card pages. Copilot cannot.
  • No Immersive Reader or read-aloud: Lens integrated deeply with Microsoft’s accessibility tools, allowing visually impaired users to have scanned text read aloud. These features are absent from Copilot’s scan tool.
  • Local file migration is awkward: On Android, Copilot needs “All Files Access” permission to see locally stored Lens scans. On iOS, local scans may not appear automatically; users must manually export them.

For users who built workflows around these missing features, the migration is not a simple swap.

Microsoft’s Official Guidance: What It Says and What It Doesn’t

Microsoft’s support document states that no mandatory admin action is required, but it “strongly recommends” notifying users and updating documentation. The company encourages exporting any locally stored scans to OneDrive or another cloud store before December 15, 2025, to preserve access.

The document also suggests that users can continue to view previously saved scans in the Lens app post-retirement as long as they keep it installed. That offers a temporary reprieve, but relying on a deprecated app is risky—OS updates or accidental deletion could wipe out data.

Notably, Microsoft’s communication has been low-key. No blog post or major announcement accompanied the support page; the news broke through Bleeping Computer and TechCrunch. This quiet approach has left many users and IT pros scrambling.

Privacy and Compliance Risks

The transition is not just an inconvenience; it has real compliance implications. Lens users often stored scans locally on their devices, especially when working offline. Those local files are not subject to organizational retention policies, eDiscovery, or legal holds unless users proactively upload them to managed cloud storage.

Microsoft’s guidance urges exporting local scans to OneDrive or SharePoint before the December cutoff. For regulated industries, failure to do so could mean losing records that should be retained. Additionally, the broad file access permissions required on Android for Copilot may conflict with security policies that enforce least privilege. IT teams must weigh the need to surface local scans against the risks of granting app-level file system access.

Accessibility: A Step Backward for Some Users

The loss of Immersive Reader and read-aloud in the scanning flow is a significant blow. Many students and professionals with dyslexia, vision impairments, or other reading challenges relied on Lens to capture printed text and hear it spoken back. While Immersive Reader remains available in other Microsoft apps (like OneNote or Word), it no longer ties directly into the scanning experience.

Organizations that have provided Lens as a reasonable accommodation under accessibility policies will need to identify alternative workflows. This might involve scanning to PDF, then importing into a app that supports text-to-speech, but that adds friction. Microsoft has not indicated if or when these features will be added to Copilot.

What Should You Do Now? An Action Plan

With the clock ticking, here’s a practical checklist for IT teams and power users:

By September 15, 2025

  • Inventory usage: Identify which users rely on Lens and for what specific tasks. Pay special attention to OneNote saves, business card scans, and accessibility-dependent workflows.
  • Notify users: Send clear communications about the retirement timeline and what will change.

Between September 15 and November 15, 2025

  • Test Copilot scanning: Have users try the “Create → Scan” flow in the Microsoft 365 Copilot app. Note any gaps that affect productivity.
  • Plan local file migrations: For Android, decide whether to grant All Files Access; for iOS, instruct users to manually export scans.

Before December 15, 2025

  • Export everything: Ensure all locally stored Lens scans are moved to OneDrive, SharePoint, or another managed cloud repository.
  • Set up automations: If you need to replicate the direct-to-OneNote/Word/PPT workflow, configure Power Automate or similar tools to push scanned PDFs from OneDrive into those apps.
  • Address accessibility: Pilot alternative reading tools for users who depended on Lens’s built-in features.

After December 15, 2025

  • Keep Lens installed (optional): Users can retain the app as a read-only archive, but instruct them not to rely on it for new work. All scanning should move to Copilot or an alternative.

Alternatives if Copilot Falls Short

If Copilot’s current feature set does not meet all your needs, consider third-party options. Adobe Scan, Tiny Scanner, and CamScanner offer robust OCR and export capabilities, though many have subscription models. The key is to evaluate them against your security and compliance requirements now, while you still have time to transition.

For organizations deeply invested in OneNote, a two-step process—scan to PDF via Copilot, then import to OneNote via desktop—may be the simplest workaround. Power Automate can automate this, but it requires configuration.

Why Is Microsoft Doing This?

Microsoft has been steadily consolidating its mobile offerings into the Copilot umbrella, aiming to drive AI-powered experiences. By killing Lens, it reduces app fragmentation and channels users toward a single platform where it can layer in features like AI analysis of scanned documents. The promise is that future Copilot updates could surpass what Lens offered, with intelligent extraction, summarization, and more.

However, the execution feels rushed. Discontinuing a beloved tool before the successor achieves feature parity risks alienating users. The backlash on social media and in forums shows that Lens’s simplicity was its superpower—something AI bells and whistles may not easily replace.

The Bottom Line

Microsoft Lens’s retirement is a done deal. The dates are fixed, and the gaps in Copilot are real. For the average user snapping a receipt or whiteboard, the migration will be straightforward. But for those who tapped into Lens’s deeper integrations—OneNote, business cards, accessibility—the road ahead is bumpier. Act now: inventory your workflows, export your scans, and test the new scanning flow in Copilot. December 15 will be here fast, and after that, Lens goes dark.