Enrolment design
Choose appropriate ownership, join and enrolment routes for new and existing Windows devices, with prerequisites made explicit.
Endpoint management
Turn endpoint setup into a controlled, repeatable deployment.
IrwellCore helps businesses and MSPs design, test and roll out Microsoft Intune and Windows Autopilot without treating every device as a one-off build.
What the service covers
A focused workstream built around the required outcome.
Build a repeatable endpoint-management foundation with enrolment, policies, applications, testing and handover included in the project.
Policy baseline
Create an agreed set of configuration, compliance and security policies with clear assignments and exception handling.
Application delivery
Package and assign agreed business applications, define dependencies and test the user experience before wider deployment.
Autopilot rollout
Configure deployment profiles, pilot the build path and document the operational steps for future devices.
When to use this service
Bring a defined change, constraint or delivery gap.
A useful first conversation explains what must be different at the end, who owns the environment and what is currently blocking the team.
- New laptops take too long to prepare or differ from one engineer to the next.
- Existing devices are unmanaged or enrolled inconsistently.
- A Windows refresh needs a repeatable build and user handover process.
- Policies and applications have accumulated without clear ownership or testing.
- An MSP needs a specialist endpoint workstream delivered for a client.
Project deliverables
Useful records, not just completed tasks.
Exact deliverables are confirmed in the proposal. The aim is to leave the receiving team with enough context to operate and support what changed.
Boundaries and prerequisites
- Compatible Microsoft licensing, supported devices and customer-controlled accounts are required.
- Legacy applications and unusual hardware may need separate packaging or compatibility work.
- The project establishes the agreed deployment; ongoing endpoint support remains with your support team or MSP.
- Readiness assessment covering identity, licensing, devices and applications
- Agreed enrolment, policy, application and assignment design
- Pilot deployment with recorded issues and decisions
- Controlled rollout plan and acceptance checks
- Configuration register and operational handover guidance
Delivery process
A clear route from discovery to handover.
The technical detail changes by service, but ownership and project controls stay consistent.
- 01
Scope
Define the outcome, environment, stakeholders, constraints and what a successful handover looks like.
- 02
Plan
Agree access, delivery windows, dependencies, communications and a practical change or rollout sequence.
- 03
Deliver
Complete the work in controlled stages, keeping blockers and decisions visible as the project moves.
- 04
Handover
Validate the outcome, record the configuration and transfer knowledge to the client or ongoing MSP.
Service FAQs
Questions to settle before delivery.
These answers explain common assumptions. The written proposal is the final record of what a specific project includes.
Read all general FAQsCan existing laptops be enrolled into Intune?
Often, yes. The right route depends on device ownership, current join state, Windows edition, user impact and whether a rebuild is acceptable. Discovery identifies the workable options.
Do we need Microsoft licences before the project starts?
The required licences must be available for the features in scope. IrwellCore records licence assumptions during discovery so the technical plan does not depend on unavailable features.
Can you package all of our applications?
A defined application list can be included. Complex, unsupported or frequently changing applications may require separate discovery rather than being assumed within a standard deployment.
How do you reduce rollout risk?
The project uses representative pilot devices and users, recorded acceptance checks, staged assignments and agreed recovery options before broader rollout.
Related services
Build the complete workstream without blurring ownership.
Adjacent services can be combined when their dependencies, delivery windows and acceptance checks are clear.
Start with the outcome
Discuss a intune & autopilot project.
Share the current environment, required outcome, timing and known constraints. The next step is a focused scope check.