Microsoft Copilot+ PCs: What the AI PC Means for Your Workforce

What You'll Learn

• What makes a Copilot+ PC different from a standard laptop
• The Recall feature: how it works, what it stores, and the privacy implications
• A procurement checklist for executives evaluating AI PCs

Microsoft announced Copilot+ PCs at Build 2024. The defining feature is a dedicated neural processing unit (NPU) built into the chip, enabling AI features to run locally on the device rather than sending data to the cloud. The first devices are the Surface Pro 11 and Surface Laptop 6, both with Snapdragon X Elite chips.

On-device AI processing changes the enterprise security calculus. Cloud AI features have faced legitimate objections from compliance and legal teams: data leaves the device and crosses network boundaries. On-device AI removes that objection for a specific category of AI features, including the flagship Recall feature.

This article explains what Recall actually does, which AI features are on-device versus cloud-dependent, the privacy considerations for enterprise deployment, and a procurement evaluation checklist.

SUBSCRIBER BREAK -- Premium Content Below

What Makes a Copilot+ PC

A Copilot+ PC requires a minimum of 40 TOPS (trillion operations per second) of NPU performance. This is the threshold Microsoft set to guarantee that AI features run locally without cloud dependency. The first Snapdragon X Elite chips exceed this threshold, with Intel and AMD NPU options expected through the rest of 2024.

The Recall Feature: What It Actually Does

Recall takes a screenshot of your screen every few seconds. It processes these screenshots locally using the NPU to extract text, identify applications, and create a searchable index of everything you have seen on your PC.

The user-facing experience: type a natural language query like "find that email from the supplier about shipping delays in April" and Windows retrieves the relevant screenshots and context, even if you deleted the email or no longer remember where you saw it.

What stays on-device: The screenshots and the index are stored locally, encrypted, and processed by the NPU. Microsoft states this data does not leave the device.

Privacy and Enterprise Considerations

Before deploying Recall in an enterprise environment, review these questions with IT and legal:

• Who has access to the screenshot index?
• What happens to the index when a device is provisioned to a new user?
• Can IT administrators disable Recall for specific roles or devices?
• How does Recall interact with DLP (data loss prevention) policies?

Microsoft has indicated that enterprises can disable Recall via Group Policy, and that sensitive content filters (credit card numbers, passwords) are excluded from the index by default.

Procurement Checklist

• Identify high-priority roles. Which employee categories (analysts, executives, researchers) would benefit most from Recall's information retrieval capability?
• Evaluate current device age. Copilot+ requirements mean existing devices do not qualify. This is a new-device category, not a software update.
• Review the privacy policy. Confirm Microsoft's Recall data handling commitments align with your data classification policies before procurement.
• Pilot with a small group. Start with 10-15 volunteers who evaluate Recall for 30 days and document time savings on information retrieval tasks.
• Include in next refresh cycle. For most organizations, the right path is including Copilot+ specifications in the next laptop refresh RFP rather than accelerating replacement of functional devices.