Skip to content
M365 Desk Microsoft 365 user support
Menu

“Who actually owns the laptop, not just the camera plugged into it?”

The device needs a named owner too, not only the peripherals in it.

Device and peripheral support covers cameras, docks, and headsets. This is the other half of the same device: who enrolls it, keeps it patched, and retires it when someone leaves—named the same way a mailbox or a Teams account already is.

Ask about device enrollment

Enrollment & new-device setup

The device model, who it belongs to, the exact screen or error shown, and whether the same enrollment process has worked for anyone else recently.

Good desk starting points
  • A new laptop that won’t complete Intune enrollment
  • A device stuck on a setup or sign-in screen during first use
  • Confirming a device shows as compliant after setup
  • Adding a device to the right group for its user

Patch status & compliance prompts

The exact compliance message, the device’s current update status, and how long the condition has been showing.

Good desk starting points
  • A device flagged “not compliant” for an unclear reason
  • An update stuck downloading or failing to install
  • A compliance prompt blocking access to mail or Teams
  • Confirming whether a specific device is up to date

Reassignment & retirement

The device’s current holder, its next holder if any, and the approved departure or reassignment date.

Good desk starting points
  • Wiping and reassigning a returned device to a new person
  • Removing a departed employee’s device from management
  • Confirming a retired device no longer holds tenant access

Read the request

Four patterns, four different next steps.

Most device-management reports fall into one of these—naming which one saves a round trip.

A missed update

One device fell behind and needs a nudge—an everyday desk request, not a policy problem.

A policy that needs deciding

How strict compliance should be, and for whom, is a decision for your business, not an assumption the desk should make.

A pattern across many devices

The same prompt on several machines at once usually means the policy or rollout itself needs a second look.

A fleet that outgrew ad hoc management

Once device count and turnover both grow, enrollment and patching deserve a named ongoing owner—inside the desk relationship or alongside it.

Common questions

Everyday device request, or a policy decision.

Does the desk design our Intune compliance policy?

No. Deciding what a compliance policy should require—minimum OS version, encryption, PIN rules—is a device-management decision for your business. The desk can support the day-to-day: a specific device, a specific prompt, a specific person.

Can the desk enroll a new hire’s laptop?

Yes. Walking a specific device through an already-defined enrollment process is a routine request, matched to the same onboarding checklist that covers the person’s account and licence.

What if several devices fail compliance at once?

That pattern is worth naming clearly and early—it usually points at the policy, a rollout, or a shared cause rather than any one device. The desk can help describe the pattern; deciding the fix may need your device-management owner.

Related guides

The device story continues where the peripherals leave off.

Device and peripheral support →Employee onboarding and offboarding →
M365 Desk

One place for everyday Microsoft 365 questions to begin.

English-language user support for growing Canadian teams. Service plans are priced in Canadian dollars.

Describe your issue

M365 Desk is an independent IT provider and is not affiliated with Microsoft. Microsoft and Microsoft 365 are trademarks of the Microsoft group of companies.

Related brands share common ownership and are operated by the same team.