Microsoft 365 pilot

Is your next Windows pilot group ready?

Three devices are in the sample Intune report. One has installed the application and checked in. Before adding another group, see which device can also produce the browser activity your security team needs.

Three fictional Windows devices have installed, failed and pending results. Only the installed device reports a heartbeat.
Northstar’s fictional installation report. Read the installation and heartbeat columns together, then check the browser adapter on the endpoint.

What to verify before adding another group

Count the devices in scope

Record the expected hostnames, included groups, exclusions and reporting time. Keep missing devices in the total so a small set of healthy laptops cannot hide an incomplete rollout.

Trace one browser event

Use a harmless test file on an approved AI page. Find the filename on the same device in your tenant, then record the action and UTC time. Repeat for each browser or action the next group needs.

Give each gap an owner

Record failed installations, missing check-ins and unavailable browser adapters separately. Give the endpoint team a device and a reproducible test. Recheck the affected device before expanding the group.

Work through a device with missing browser events

The troubleshooting guide follows an Engineering laptop with a recent heartbeat and an unavailable adapter. Use the companion scorecard to record what your own pilot demonstrated.

A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope
More supported tools

This creates a planning document. It does not enroll devices or submit a request.