Direct answer
Before a new endpoint is handed over, verify its identity, management enrollment, supported OS, applicable protections and recovery path using a documented acceptance checklist.
Register the correct asset
Match the physical device and owner to the asset, identity and management records using approved identifiers. Confirm the intended device group and role. A device that appears in a directory may not yet be enrolled or reporting to management.
Verify protection and reporting
Check the supported Windows release, update state, encryption, firewall and intended antivirus provider against policy. If the organization uses Defender for Endpoint, review sensor health and reporting; Microsoft distinguishes active, inactive and misconfigured states.
Reference: Microsoft: Device sensor health.
Test the handoff
Confirm the authorized user's sign-in, required applications, backup or data location and support recovery route. Record policy failures and pending restarts with an owner rather than silently marking the device complete. Repeat checks after provisioning has finished.
Handle a pending enrollment
If a new laptop appears in the directory but has not checked in to management, keep onboarding open and identify the network or enrollment error. Verify the actual encryption and protection state locally where authorized, then recheck the management report after sync. Assign an owner and deadline instead of treating a directory record as completion.
Assessment limits
Onboarding checks are a point-in-time sample of defined controls, not a certification that the endpoint has no vulnerabilities or future reporting gaps.
Frequently asked questions
Does a directory record prove management enrollment?
No. Verify enrollment and the last successful device check-in separately.
Does active sensor reporting prove the endpoint is threat-free?
No. Reporting is one visibility signal, not a guarantee of security.
Should a pending failure be marked as complete?
Track it with an owner and retest condition until the effective state is verified.
Primary sources and further reading
These guides combine published security guidance with practical assessment planning. Adapt checks to the owner's policy, environment, and authorized scope.
This guide was prepared with AI assistance using the linked sources and illustrative examples. Check current vendor guidance and your environment before making changes.