The most expensive misunderstanding in Australian endpoint refresh planning right now is the belief that a business needs a Copilot+ PC to use Microsoft 365 Copilot. It doesn't. Microsoft 365 Copilot is a cloud service. It runs in Microsoft's data centres, reaches your tenant's data through the Microsoft Graph, and renders results inside Word, Excel, Outlook, Teams and the Copilot Chat app. The processing happens on a server, not on the device on the user's desk. A five-year-old laptop running a supported version of Windows and the M365 apps can use Copilot exactly as well as a brand-new machine.
What a Copilot+ PC actually is
A Copilot+ PC is a hardware specification, not a software entitlement. To carry the Copilot+ badge a device must include a Neural Processing Unit (NPU) capable of at least 40 trillion operations per second (40 TOPS), alongside a minimum of 16 GB of RAM and 256 GB of storage. The NPU is a dedicated chip for running small AI models locally on the device, separate from the CPU and GPU. The first wave shipped on Qualcomm Snapdragon X (Arm) silicon; Intel Lunar Lake and AMD Ryzen AI now meet the bar on x86 as well.
The badge governs what on-device AI features Windows will switch on. It has no bearing on whether Microsoft 365 Copilot — the cloud assistant your organisation licenses per user — will function. Those are two different products that happen to share the Copilot name.
Cloud Copilot vs on-device AI — the line that matters
Draw a clear line and the buying decision gets simpler. On one side sits Microsoft 365 Copilot: cloud-hosted, licensed per user, grounded in your tenant data, and indifferent to the hardware it's displayed on. On the other side sits a set of Windows features that run on the NPU inside the device itself, with no licence and no cloud round-trip. Confusing the two is what leads finance to approve a premium hardware line item it never needed to spend.
- Cloud — Microsoft 365 Copilot. Per-user licence (indicative AUD list around $45.90 per user per month, annual commitment — confirm at purchase). Needs an internet connection and the M365 apps. Hardware-agnostic.
- On-device — Windows Copilot+ features. No licence, no cloud call for the local features. Needs the NPU. The work happens on the device.
What the NPU genuinely adds
The on-device features are real and some are useful, but they are productivity conveniences in Windows rather than the enterprise data assistant most businesses are buying Copilot for. The headline Copilot+ capabilities as they stand in 2026:
- Recall — a timeline that periodically snapshots what's been on screen so a user can search back through past activity in natural language. Off by default, opt-in, and gated behind Windows Hello, Microsoft Defender and BitLocker. This is the feature that drew the most security scrutiny.
- Live Captions with real-time translation — captions and translation generated locally for any audio playing on the device, including calls and recorded media.
- Windows Studio Effects — background blur, auto-framing, eye contact correction and voice focus for the webcam, run on the NPU instead of the CPU so battery and performance hold up.
- Cocreator and image features in Paint and Photos — local image generation and editing assisted by the on-device model.
- Improved battery life on AI workloads — offloading inference to the NPU keeps the CPU cooler and extends runtime on Arm-based machines in particular.
None of those features touch your SharePoint, your Exchange mailboxes or your Teams history. Recall indexes what the individual user has personally viewed on their own screen; it is not a tenant knowledge tool. If the business case for AI is "help our staff find and reason over company data," that case is met entirely by the cloud Copilot licence and needs no NPU.
The Recall question for Australian businesses
Recall is the on-device feature that warrants a deliberate decision rather than a default. Because it captures periodic snapshots of screen content, it can incidentally record sensitive information — client records, payroll, health data — that an organisation may hold under the Privacy Act 1988. Microsoft has delivered the controls administrators asked for: Recall is opt-in, encrypted, protected by Windows Hello, and can be disabled or blocked entirely through Microsoft Intune policy. For most regulated or data-sensitive Australian organisations the sensible posture on day one is to disable Recall by policy across the managed fleet and revisit it deliberately, rather than let it arrive switched off-but-available on every new device. Frontrow treats this as a standard hardening line in the device build.
Where the on-device premium does earn its place
Copilot+ hardware is not a waste of money — it just has to be bought for the right reason. The premium is justified when the device characteristics matter on their own merits:
- Battery and portability — the Arm-based Copilot+ machines deliver genuinely long runtime and quiet, cool operation. For a heavily mobile workforce that alone can justify the choice.
- Field and frontline roles — local live captions and translation are useful where connectivity is patchy and a cloud round-trip isn't reliable.
- Future-proofing a refresh — if a device is being replaced anyway in the normal three-to-four-year cycle, choosing a Copilot+ model costs little or nothing extra and positions the fleet for on-device AI features that will expand over time.
- Roles that lean on webcam quality — Studio Effects materially improves the look and audio of customer-facing video calls.
What Frontrow would actually do
The pragmatic position for an Australian mid-market business in 2026 is to decouple the two decisions completely. License Microsoft 365 Copilot for the people who will get value from a cloud data assistant, on whatever supported hardware they already own — there is no need to refresh a single laptop to start. Separately, when devices reach their normal end of life, default the replacement to Copilot+ specification because the incremental cost is small and the NPU, RAM and storage floor are sensible baselines regardless of AI. Do not bring a hardware refresh forward to "enable Copilot"; that spend buys nothing the cloud licence doesn't already deliver.
Manage the fleet the same way you already do
Copilot+ PCs deploy and manage through the same Microsoft Intune and Windows Autopilot pipeline as any other Windows endpoint. They enrol via Autopilot, receive Configuration Profiles and Compliance Policies through Intune, and pick up the same Conditional Access and BitLocker posture. The one addition is a deliberate policy stance on the on-device AI features — disabling or scoping Recall and the local generative tools where data sensitivity warrants it. Arm-based Copilot+ devices on Snapdragon do warrant an application-compatibility check before mass rollout: confirm line-of-business apps, VPN clients, security agents and any legacy 32-bit tools run cleanly on Arm before committing a department to that silicon. Intel and AMD Copilot+ models avoid that question entirely.
The bottom line on cost
The premium for a Copilot+ specification over a comparable standard business laptop is modest and shrinking as the silicon becomes mainstream — increasingly it is simply the current generation of business hardware rather than a separate tier. The decision that carries real money is the Microsoft 365 Copilot per-user licence, and that decision is independent of the hardware on the desk. Spend the licence budget where the data-assistant value is; let the hardware follow the normal refresh cycle. The one outcome to avoid is paying a premium, or pulling a refresh forward, in the belief that it's a prerequisite for Copilot. It isn't.