Provision
A new device arrives configured to the standard build, with accounts, applications, and access ready before it reaches the employee.
Device lifecycle / Purchase to retirement
A device is only as reliable as the plan behind it.
Laptops and phones do not stay healthy on their own. Device care is a repeatable plan for every stage a machine moves through—not a reaction to the day it finally stops working.
Lire cette page en françaisStarting point
Know the fleet before you manage it.
Device care starts with a plain description of what your team actually uses: how many machines, which platform, who owns each one, and how old they are. Without that baseline, “we manage your devices” is a slogan, not a service.
- A current inventory by device, owner, and location
- A standard build so new machines start from the same baseline
- A defined update and patch cadence
- Warranty and support-plan end dates that do not surprise anyone
Four stages, one owner
The plan matters most before and after the ticket.
Maintain
Updates, disk health, and basic performance get regular attention instead of waiting for a visible failure. See how monitoring and patching actually work
Support
When something breaks, the fix considers the device’s history—not just the symptom in front of you.
Retire
A device leaving service gets a deliberate step for data and disposal, not a drawer.
Who this fits
Built for standard business hardware.
A good fitCompany-owned Windows or Mac laptops, phones, and common peripherals used for everyday work.
Probably not the fitSpecialized industrial, medical, or point-of-sale hardware tied to a manufacturer’s own service program, or personal devices with no management agreement in place.
Across the life of a device
Each stage has a typical action and a decision owner.
| Stage | Typical action | Decision owner |
|---|---|---|
| Provisioning | Build, tag, and prepare before day one | Managed service, per the agreed standard |
| Routine maintenance | Updates, health checks, minor repairs | Managed service, on the agreed cadence |
| Support incident | Diagnose, repair, or arrange manufacturer service | Managed service, escalated when warranty applies |
| Refresh or retirement | Assess age and condition against the standard | Your team approves replacement and budget |
A device leaving service still carries data until someone deals with it deliberately—a wipe, an encryption confirmation, or vendor-managed disposal, depending on the device and your policy. This site does not claim a specific data-destruction certification; confirm the exact method and evidence you need in writing.
Personal devices
Supporting a personal device is a scope decision.
Some teams want limited support for personal phones or laptops used for work email and Teams. That can work, but it needs an explicit agreement about what is and is not touched.
- What data or apps the device may access
- What the employee agrees to install or allow
- What happens to work data if the device is lost or the employee departs
- What is explicitly out of scope
Next step
Turn your IT context into a clear scope.
A scope conversation covers your team, Microsoft 365, devices, vendors, and responsibilities to transfer. You leave with the scope questions that need answers—without sharing secrets.
Discuss your IT scope