Your practice
You set the device standard, decide who’s authorized to request a new enrollment, and confirm when a device is formally retired.
Endpoint lifecycle Cycle de vie des postes
Enrollment, patching, and retirement — one line, not three separate habits.
A properly managed device fleet follows a documented path, not whatever the last technician happened to remember. This page names enrollment, compliance policy, and end-of-life retirement as their own delivered line — distinct from everyday requests — so your practice can sell "managed devices" as a specific item with its own scope.
Delivery team
We enroll devices into the agreed Intune tenant, apply the compliance policy you’ve set, and process the retirement checklist when a device leaves the fleet.
Enrollment, compliance, and retirement
For a client who wants new and returning devices enrolled and configured the same way every time — not whatever the last technician remembered.
What we need first
Tenant access with the right role, the compliance policy baseline you want applied, and a named approver for exceptions (a device that can’t meet policy but still needs to be used).
What’s included
- New-device enrollment into the agreed profile
- Compliance checks against the baseline you set
- A retirement checklist when a device is decommissioned or reassigned
Handled separately
- Deciding the device standard or purchasing hardware
- Enrolling a device outside the agreed profile without sign-off
- Presenting this as a Microsoft partnership or certification
What you get: A fleet where enrollment, policy, and retirement follow one documented path instead of three different habits depending on who handled it.
What we hand back: An enrollment or retirement note naming what changed and what’s still open.
What "managed devices" has to define before it’s priced
Enrollment method
Self-service by the user versus pre-provisioning before a device ships — the choice changes what we can guarantee about consistency, and it’s set before the first device.
Who counts as an authorized requester
Enrollment should never depend on an informal email. Name who, on your client’s side, can actually request a new device or a re-enrollment.
What "retired" actually means
Full wipe, reassignment to another user, or return to a device pool — all three are legitimate, but only one should be your account’s default rule.
Exception path
A device that can’t meet the compliance baseline (older hardware, particular line-of-business software) needs a documented exception path, not a quiet workaround.
What this line doesn’t include
- Choosing the MDM platform or device brand
- A guaranteed enrollment turnaround time
- Data recovery from a personally-owned or unmanaged device
Straight answers on managed devices
Does this only work with Windows?+
Scope depends on the platforms your practice has actually agreed with us at setup — it’s not a default assumption, and it’s confirmed before the first device is enrolled.
Do you support personal devices (BYOD)?+
Scope for a personally-owned or mixed-ownership device is a decision your practice makes upfront, not a default we assume. Name it in the agreed profile before the first device.