Windows Autopilot registration and deployment
We register devices with Windows Autopilot and configure deployment profiles with Intune. We help businesses and hardware resellers prepare each delivery, from device data through to first-boot validation.
A setup process prepared before the device reaches its user
A new computer should reach its user with a clear setup process. Windows Autopilot lets you prepare that experience from the cloud: the device recognises the organisation and receives its assigned setup. Intune manages the applications and policies included in the project.
MSAdvance can handle registration alone or support the full implementation. We review the existing environment, agree who owns each part and test the result on representative devices before extending the rollout.
Registration, profiles and enrolment each have a role
Associate its identity with the organisation through an authorised channel and check the result.
Prepare groups and profiles that define how each device type is set up.
Validate Intune enrolment, applications and policies during initial setup.
For your business or the customers you supply
New computers for your team
You need to prepare laptops for new starters, replace existing devices or deliver computers to people working remotely.
A batch awaiting registration
You have devices or registration data and need someone to validate the records, process them and report which units registered successfully.
Devices you supply to customers
You are a hardware reseller, integrator or equipment supplier and want to include Autopilot registration in your service.
Device registration, profiles and Intune configuration
Registration and inventory
We validate device data and the available registration channel, carry out authorised registration and reconcile each batch. We review duplicates, errors and outstanding units.
Groups and assignments
We define Group Tags, grouping criteria and assignments to reflect device models, departments or the types of delivery you need to manage.
Deployment profiles
We configure the initial experience, settings supported by the chosen mode and user permissions. Device naming and initial setup options are agreed where the scenario supports them.
Applications and enrolment status
We prepare essential applications and the Enrollment Status Page. We review dependencies, installation, blocking behaviour and error handling so that device preparation has a clear outcome.
Intune configuration and security
We include agreed policies for updates, encryption, device protection or compliance. Identity and Conditional Access are coordinated with the environment’s owners to avoid conflicting settings.
Pilot and validation
We test the journey from first boot to the desktop with representative models and users. We check identity, enrolment, applications and policies before expanding the rollout.
What we need to register your devices with Autopilot
Before processing an order, we check its destination, authorisation and available identifiers. This keeps received devices distinct from successfully registered devices, with a clear record of any units still outstanding.
Customer, tenant and authorisation
We identify the destination organisation and its technical contact. The tenant ID, domain and registration relationship are checked before devices are associated. Intune administration permissions are agreed separately and limited to the contracted work.
Device identifiers
We check serial numbers, manufacturer, model and the data accepted by the chosen channel, such as PKID or hardware hash. For new-device orders, we prioritise information and registration from the OEM or authorised distribution channel where available. Incomplete files and duplicates are reviewed before upload.
Tags, groups and order criteria
We agree whether a batch needs a Group Tag and what it represents, such as customer, department or device type. A tag helps organise devices; profiles and applications still depend on configured assignments. Where the customer manages Intune, their administrator receives the criteria needed to validate groups and profiles.
Per-device results and outstanding actions
We reconcile the order against registration results. The report identifies completed devices, errors and outstanding units, with known reasons and the next responsible party. Registration-only delivery is kept distinct from completed device configuration or a first-boot test.
Windows Autopilot registration for hardware resellers
If you sell or supply computers, we can help you deliver Autopilot registration as an organised, repeatable service. We work with your team and the end customer’s IT owner, with clear authorisations and responsibilities for each operation.
Prepare each order
We agree the information required for each customer and batch, the destination tenant, identification criteria and the process for reporting issues.
Use the right registration channel
We coordinate the OEM/CSP route where available and authorised, or tenant import with the required identifiers. A serial number alone is not sufficient for every registration method.
Confirm and hand over results
We report device status, errors and outstanding units. If configuration is also in scope, we coordinate profiles and testing with the customer’s Intune administrator.
Registration and administration use different permissions. An approved registration relationship does not automatically provide access to configure Intune. Customer profiles, applications and policies require their own permissions and agreed scope.
We can support one-off orders or recurring batches and agree a white-label arrangement. Volumes, support windows, contacts and delivery evidence are defined together. MSAdvance delivers remotely; physical preparation, packaging and shipping remain with the supplier or local team.
The right option for your devices and operating model
Classic Windows Autopilot
For scenarios that need registered devices and Autopilot deployment profiles. We select a supported mode and validate its identity, hardware and network requirements.
Windows Autopilot device preparation
We assess this option for compatible Windows 11 and Microsoft Entra ID scenarios. Preparation and device association follow a different workflow; classic Autopilot hardware-hash registration is not required.
Pre-provisioning
We design the process and guide the technician or supplier preparing the physical devices. Compatibility, TPM and attestation, applications and the final user experience are checked first.
Autopilot profiles, applications and security with Intune
The setup experience depends on more than the Autopilot profile. We review environment requirements and agree what must be available before users start work and what can be installed afterwards.
Initial experience and user permissions
We agree deployment mode, join type, groups and initial setup options. Standard or administrator access, naming and supported branding are reviewed for the scenario. The pilot checks what users actually see rather than assuming every option applies to every deployment mode.
Essential applications and the Enrollment Status Page
Essential applications are separated from the wider catalogue. We review silent installation, detection, dependencies and assignment context. For classic Autopilot, the Enrollment Status Page —ESP— is configured where appropriate, including blocking applications, time limits and failure options. Device preparation has its own configuration process.
Policies and resource access
We coordinate encryption, updates, compliance and device protection within scope. Enrolment is checked against existing identity and access policies. Any required exceptions are reviewed with their owners. The outcome needs to be a configuration the team can maintain, alongside a device that starts successfully.
Windows, licensing and connectivity
We check supported Windows versions and editions, required Intune and Entra ID licences and assignments, enrolment restrictions and service connectivity. An Office licence or Windows alone does not replace these requirements. Pre-provisioning and other scenarios also receive their own hardware and network prerequisite checks.
Support beyond the initial registration
Registration and deployment issues
We investigate incomplete data, duplicates, pending assignments, enrolment restrictions and application or status-page errors. We identify when the manufacturer, Microsoft or another administrator needs to act.
Reuse and reassignment
We plan reset and reprovisioning around the device’s current state and the intended scenario. Data protection, applications and user impact are agreed before changes take place.
Retirement and tenant changes
We coordinate authorised deregistration and the associated Intune and Entra ID tasks. Removing an Autopilot record does not automatically remove enrolment or the device identity. Existing ownership in another tenant must be resolved first.
From requirements to a verified handover
Review
Devices, licences, available data and responsible teams.
Design
Deployment mode, profiles, groups and acceptance criteria.
Prepare
Registration and configuration within the agreed scope.
Pilot
First boot, applications and policy checks.
Hand over
Batch results, documentation and knowledge transfer.
How we check that a device is ready for handover
Tests are agreed before rollout expands. Registration-only work validates the outcome for each unit; a wider implementation also tests the full journey with representative devices, users and applications.
Confirmed registration and assignment
We compare the Autopilot inventory with the expected batch. Where configuration is included, the assigned profile and relevant groups are also checked before the test boot. Synchronisation and assignments can take time; uploading a file alone does not mark a unit complete.
Correct identity and enrolment
We test sign-in with the intended account and check Intune and Entra ID device status against the design. Naming, associated user where applicable and management state are reviewed. Reused devices follow the reset or reinstallation procedure agreed in advance.
Applications and everyday work
We check that essential applications install and open, expected policies arrive and the user can access business resources. Errors, observed setup times and required changes are recorded. Pilot timings inform planning; they are not a fixed promise across every network or device model.
Evidence and named owners at handover
Your team receives batch or pilot results, the configuration in scope and outstanding issues. Each exception has an owner and a next step. IT receives guidance for repeating the agreed tasks; ongoing support and later application changes have their own scope.
What your team receives and what we check first
- Processed device list with the outcome for each unit.
- Groups, tags, profiles and assignments included in the project.
- Contracted Intune configuration and applications.
- Pilot results and outstanding issues.
- Instructions for agreed onboarding, changes and retirement tasks.
- Documentation and a handover session for the responsible team.
For application, policy and device maintenance after the project, we can agree Microsoft Intune administration or managed services. Frequency, service hours and responsibilities are defined in the proposal.
Registration, permissions and deployment
Can you handle device registration only?
Yes. We can validate and process a batch, confirm the outcome and document exceptions. Profiles, applications and Intune administration can be added when included in the engagement.
Can you help a reseller that does not administer Intune?
Yes. We coordinate registration with the customer’s approval and provide the outcome to their IT team. Registration does not mean taking over tenant administration; we check the channel and permissions first.
Are serial numbers enough to register devices?
It depends on the channel. An authorised OEM or partner can use identifiers supported by its customer relationship. Authorised imports through Intune require the relevant hardware hash. We check the available data before accepting a batch.
Do you configure deployment profiles and applications?
Yes. We can prepare profiles, groups, the Enrollment Status Page and the agreed applications and policies. Assignments are tested on representative devices before general rollout.
Can you include computers already in use?
We review their current state, identity, management and applications. A reset or reinstallation may be needed, so backups, change windows and user support are agreed in advance.
What if a device is registered to another tenant?
The existing registration must be resolved through the previous organisation and authorised channels. We investigate and help coordinate the process. A device cannot be transferred by ignoring its existing ownership.
Is device preparation the same as classic Autopilot?
They are different experiences with different requirements and capabilities. Device preparation does not require classic hardware-hash registration. We choose the approach based on your scenario, compatibility and management needs.
What do you need to prepare a proposal?
Approximate device counts, models and Windows versions, destination tenant, licences, Intune status, available device data and target date. For resellers, batch volumes and the customer authorisation process also help define the service.
Does Windows Autopilot replace Microsoft Intune?
No. Autopilot prepares the initial setup experience and device onboarding process. Intune manages the applications, settings and policies included in the project. We can handle registration alone or coordinate both parts with your administrator.
Which licences do we need for an Autopilot deployment?
We review the required Windows, Microsoft Entra ID and Intune capabilities and the subscriptions covering them. Microsoft 365 Business Premium is one possible option; the right plan depends on users and the scenario. The proposal separates licensing from professional services, with assignments checked before the pilot.
How long does registration or implementation take, and what does it cost?
Scope depends on volume, data quality, customer authorisation, deployment mode and the Intune work included. Batch registration and an implementation with applications involve different tasks. After reviewing these inputs, the proposal defines price, schedule, dependencies and acceptance criteria without assuming a fixed time per device.
Do we need to send computers to MSAdvance?
No. We deliver remotely. Your supplier or local team handles physical preparation, device data collection that requires local access, on-site tests and shipping. We can guide those activities and review results within the agreed scope.
Devices, identity and ongoing operations
Prepare your next device delivery with Autopilot
Tell us whether you need to register a batch, configure deployment for your business or add Autopilot to your customer deliveries. We will define the process, the data required and the scope of work.

