Microsoft Lens, the free mobile scanning app that has helped millions of users digitize documents, whiteboards, and receipts for over a decade, is officially being retired. The company confirmed a phased shutdown that begins in September 2025 and culminates in December 2025, after which the standalone app will no longer allow new scans. All users are being directed to the Microsoft 365 Copilot app, where scanning capabilities are now consolidated alongside AI-powered features. While the move simplifies Microsoft’s product lineup, it also introduces significant feature gaps and migration challenges that users and IT administrators must address before the final deadline.

A Three-Stage Sunset: Critical Dates for Your Calendar

Microsoft’s official guidance, published on its support pages and communicated to administrators, lays out a precise timeline. There is some confusion in media reports about exact dates, but the most detailed and authoritative schedule comes directly from Microsoft’s admin messaging. The key milestones are:

  • September 15, 2025 – The retirement process begins. Microsoft starts decommissioning backend services and prepares for the app’s removal from stores.
  • Mid-October 2025 – New installations of Microsoft Lens will be disabled. The app becomes unavailable for download on the Apple App Store and Google Play Store around November 15, 2025.
  • December 15, 2025 – The final cutoff. Users can no longer create new scans within the Lens app. After this date, the app will only display previously saved scans in its “MyScans” section, provided the app remains installed on the device.

These dates are not flexible. Organizations and individuals who rely on Lens for daily workflows must treat them as hard deadlines for exporting local scans and transitioning to alternative tools.

What Migrates to Copilot—and What Gets Left Behind

For basic scanning needs, Microsoft 365 Copilot preserves the core experience. Users can capture documents, receipts, and whiteboards with automatic cropping, perspective correction, and optical character recognition (OCR). Scans can be saved directly to OneDrive, just as before. However, Microsoft explicitly acknowledges several feature gaps that will impact power users and those with specific workflows.

The most significant missing capabilities in Copilot’s current scan flow include:

  • No direct export to OneNote, Word, or PowerPoint. While Lens allowed one-tap saving into these apps, Copilot requires a multi-step process: scan → save to OneDrive → open in the desired Office app.
  • No business card scanning with OneNote contact import. The ability to capture a business card and automatically create a contact in OneNote is absent. Users must manually export card images or use alternative tools.
  • No integrated Read Aloud or Immersive Reader. These accessibility features, which were tightly coupled with Lens scanning for users with visual or reading disabilities, are not available in the Copilot scan flow.
  • Local file handling challenges. Copilot can display cloud-saved Lens captures in its “MyCreations” area, but locally stored scans are not guaranteed to appear. On Android, surfacing local files may require granting the Copilot app broad “All Files Access” permissions—a potential security concern for managed devices. On iOS, limitations may prevent automatic migration altogether.

For casual, cloud-first users, the Copilot experience likely covers the majority of day-to-day needs. But educators, accessibility-dependent users, and frontline workers who built workflows around Lens’s direct exports and offline capabilities will face immediate friction.

Strategic Context: Why Microsoft Is Consolidating

Microsoft’s decision to fold Lens into Copilot fits a broader product strategy. Maintaining separate standalone apps like Lens, Office, and Microsoft 365 requires duplicated engineering effort. By consolidating scanning into the Copilot app—which is the company’s primary mobile surface for AI-driven productivity—Microsoft can focus investment on a single platform. Scanning becomes one tile in a larger mosaic that includes generative AI, multimodal reasoning, and workflow automation.

From a product-management perspective, this is rational. Engineering teams can iterate faster when all features live inside a unified codebase. For end users, the loss of a familiar, zero-cost tool with deep Office integration is painful in the short term but may eventually be offset by AI enhancements—such as automatically extracting action items from a whiteboard photo or summarizing a scanned document.

Who Feels the Impact Most

The retirement of Microsoft Lens does not affect all users equally. The following groups will experience the greatest disruption:

  • Students and educators who used Lens to capture lecture notes and whiteboards and relied on one-click export to OneNote. They must now adopt a two-step flow or find alternative apps that integrate directly with OneNote.
  • Accessibility users who depended on Read Aloud and Immersive Reader scanning flows. The removal of these hooks from the scanning experience is a substantive regression that requires immediate mitigation.
  • Field workers and frontline staff who captured receipts, forms, or business cards offline and stored them locally on the device. Copilot’s preference for cloud-backed storage and its permission requirements on Android add complexity.
  • Small businesses that used Lens as a free capture layer for expense reporting, customer onboarding, or contact management. Automated pipelines that relied on Lens’s local storage or direct exports need to be redesigned.

Across all these groups, the risks are interrupted workflows, potential data loss if local scans aren’t exported in time, and temporary productivity declines during the transition.

Operational Risks and Governance Challenges

Beyond missing features, the migration introduces several risks that IT teams must manage proactively.

Accessibility Compliance

The loss of integrated Read Aloud and Immersive Reader from the scanning experience could create legal and ethical compliance issues for organizations subject to accessibility regulations. IT and accessibility teams must validate whether Copilot’s separate accessibility features—available outside the scan flow—meet individual needs. If not, they need to provision alternative tools and test them with affected users well before the December cutoff.

Data Governance and Residency

Shifting the canonical storage location for scans from a local Lens repository to OneDrive/SharePoint changes data residency, retention, and data loss prevention (DLP) postures. Scans containing personally identifiable information (PII) or regulated data must be inventoried and exported to managed, auditable storage before the deadline. Allowing Copilot to access local files via broad Android permissions also creates governance trade-offs that security teams must evaluate.

Permission and Privacy Trade-offs on Android

To surface locally stored Lens scans in Copilot, Android users may need to grant the Copilot app “All Files Access.” This permission is broad and may conflict with enterprise security baselines that restrict such access. A safer path for managed devices is to require users to export important scans to OneDrive or SharePoint, where access and DLP can be enforced, and then deny the All Files Access permission to Copilot.

Vendor Lock-in

Consolidating scanning into Microsoft 365 Copilot deepens organizational dependency on the Microsoft 365 platform. While most enterprises already run on Microsoft, some may have regulatory or procurement constraints that make single-vendor reliance unacceptable. These organizations should assess whether the consolidation increases risk and, if so, explore third-party scanning apps that integrate with multiple cloud vendors.

Practical Migration Checklist for Individuals

If you are an individual user, start preparing now:

  1. Inventory your local scans. Open Microsoft Lens and identify any scans saved only in the app’s “MyScans” area—those not already synced to OneDrive or exported elsewhere.
  2. Export everything. Move all local scans to OneDrive, SharePoint, or a personal cloud archive before December 15, 2025. Verify that each export was successful and that the files are readable.
  3. Begin using Copilot’s scan flow today. Open the Microsoft 365 Copilot app, tap the menu, and navigate to Create → Scan. Practice capturing documents and saving them to OneDrive. Determine if this covers your most common use cases.
  4. Build workarounds for missing features. If you need direct OneNote, Word, or PowerPoint exports, adopt a two-step process: scan → save to OneDrive → open in the respective Office app. For frequent tasks, consider using Power Automate to create a flow that automatically imports new OneDrive scans into OneNote.
  5. Export business cards now. For any business card data stored in Lens, export contacts or scanned images to a CSV or vCard file. Do not wait for Copilot to add this functionality.
  6. If you rely on accessibility features, explore whether Copilot’s standalone Immersive Reader or text-to-speech tools can replicate your workflow. If not, identify a third-party scanning app that includes these features and test it immediately.

Practical Migration Checklist for IT Administrators

For organizations managing fleets of mobile devices, the timeline demands a structured migration project:

  1. Communicate broadly and early. Announce the retirement dates—September 15 start, November 15 store removal, December 15 new scans disabled—to all users. Provide step-by-step guidance on how to export local scans and begin using Copilot.
  2. Inventory Lens usage. Use mobile app telemetry, MDM reports, and helpdesk tickets to identify which teams and individuals depend on Lens. Pay special attention to users who rely on OneNote export, business card capture, or accessibility features.
  3. Enforce a migration policy. Require users to export locally stored scans to managed cloud storage by a set date (e.g., December 1, 2025). For high-risk or high-volume users, schedule a managed export where IT performs the export centrally.
  4. Evaluate Android permissions. Determine whether allowing Copilot “All Files Access” on managed devices is acceptable. In most cases, it is safer to route users through cloud exports and block that permission.
  5. Build automation for missing exports. Use Power Automate or desktop scripts to recreate one-click export flows: for example, a cloud flow that watches a OneDrive folder for new scans and automatically imports them into OneNote or creates a Word document.
  6. Prepare training materials. Create quick reference guides or videos showing users how to scan in Copilot and how to access their migrated scans.

Workarounds and Third-Party Alternatives

Some organizations and users may find Copilot’s current feature set insufficient. Options include:

  • Keep Microsoft Lens installed until the final day. Existing installations will continue to work for creating scans until December 15, 2025. Use this window to perform final exports and test alternatives.
  • Leverage Power Automate or similar tools to bridge the gap between Copilot scans and the Office apps that users need.
  • Evaluate third-party scanning apps. Apps like Adobe Scan, CamScanner, or even built-in iOS/Android document scanners can replicate many of Lens’s features, often with direct OneNote/SharePoint connectors. However, third-party options introduce new vendor management, data-handling, and licensing considerations that must be weighed against the cost of adapting Copilot workflows.

Accessibility and Compliance Action Items

This migration has direct implications for accessibility and regulatory compliance. Do not overlook these steps:

  • Engage your accessibility team immediately. Validate whether Copilot’s current read-aloud and Immersive Reader tools meet the needs of users who relied on Lens’s integrated flows. If not, define, procure, and test a parallel solution with affected users.
  • Audit data residency. Determine where sensitive scans currently live. Ensure that OneDrive/SharePoint retention policies, DLP rules, and data residency commitments align with your regulatory requirements before migrating bulk data.
  • Log migration activity. Keep an audit trail of exported scans: who performed the export, when, and where the files were moved. This is critical for compliance, eDiscovery, and records requests.

What to Expect in the Coming Months

As the deadlines approach, several outcomes are likely:

  • Most casual users will transition smoothly. For cloud-native scanning of documents and receipts, Copilot’s Create → Scan feature is already sufficient. Microsoft’s large existing install base—estimated by third-party trackers in the tens of millions with high app-store ratings—will gradually shift over.
  • Power users will feel the pain. Those who built workflows around Lens’s direct exports, business card capture, and accessibility features will experience genuine disruption. Many will implement workarounds or switch to third-party apps.
  • Microsoft may restore some missing features. The company often iterates quickly on Copilot. Keep an eye on the Microsoft 365 Message Center and official roadmap for announcements about improved scanning integrations, especially OneNote and Immersive Reader support. However, do not assume parity until it is officially announced and validated in your environment.

Final Assessment

Retiring Microsoft Lens and consolidating its capabilities into Microsoft 365 Copilot is a natural step in Microsoft’s platform strategy. It reduces engineering overhead and positions scanning within an AI-first app where future enhancements can multiply the value of captured content. For cloud-first users, the core experience remains intact, and Copilot will likely become the new default scanning surface.

But the transition is not risk-free. Missing export paths, accessibility regressions, and local-data migration pressure create real-world friction. The announced dates—September 15 for the process start, November 15 for store removal, and December 15 for the new-scan cutoff—are firm planning anchors. Organizations and individuals who inventory their usage, export local scans to managed storage, test Copilot’s scan flow, and implement automation or third-party alternatives for critical gaps will avoid data loss and user disruption.

The end of Microsoft Lens marks an inflection point: a reasonable product consolidation that demands concrete operational work. Act deliberately in the months ahead, and you can preserve your workflows, protect your data, and begin tapping into Copilot’s emerging capabilities without losing the conveniences that made Lens indispensable.