A new starter IT onboarding checklist is the difference between a new employee who is productive by ten o’clock on their first morning and one who spends the day borrowing a colleague’s laptop, waiting for a password reset and asking which Teams channel they are supposed to be in. In most UK small and mid-sized businesses the onboarding process lives in somebody’s head — usually the office manager or the one person who “knows computers” — and it changes slightly every time. That inconsistency is expensive, it frustrates the new starter, and it quietly creates the security gaps that Cyber Essentials assessors and insurers look for.
This checklist sets out a repeatable, day-one-ready joiner process built on the tools most UK SMEs already pay for: Microsoft 365, Microsoft Entra ID, Intune and Windows Autopilot. You will learn what has to happen before the start date, how to ship a laptop that configures itself out of the box, how to hand over credentials without emailing a password, how to assign licences and groups by role rather than by copying another user, and how to document the whole thing so it stands up to an audit. It is the mirror image of our Microsoft 365 offboarding guide for leavers — together they cover the full joiner–mover–leaver lifecycle.
What is new starter IT onboarding? Definition and context
New starter IT onboarding is the controlled process of creating a person’s digital identity, granting them exactly the access their role needs, issuing and configuring their devices, and teaching them the minimum security habits your organisation expects — all before or on their first day. It sits alongside the HR side of onboarding (contract, right-to-work check, payroll, induction) but it has its own dependencies and its own failure modes. HR can issue a contract in an afternoon. Ordering, enrolling and shipping a laptop to a hybrid worker in Leeds takes several working days if it is done properly.
In a modern Microsoft 365 estate, onboarding touches a long list of systems. There is the user object in Microsoft Entra ID (formerly Azure AD), the Microsoft 365 licence, the Exchange Online mailbox, OneDrive, the SharePoint sites and Teams the person needs, any distribution lists and shared mailboxes, multi-factor authentication registration, the Intune-managed laptop and phone, line-of-business applications connected via single sign-on, the phone system extension, the printer, building access and often a finance or CRM licence on top. Each of those can be configured by hand — and each hand step is a chance to get it wrong or forget it entirely.
The aim of a good joiner process is not to automate everything on day one. It is to make the process predictable: the same inputs from HR produce the same accounts, the same group memberships, the same device configuration and the same first-day experience, whoever in the business happens to be running it. Predictability is what makes onboarding fast, and it is also what makes it secure, because access granted by role can be reviewed and removed by role when the person later moves teams or leaves.
Agree a single trigger for IT onboarding — usually a signed contract logged in your HR system or a short web form completed by the hiring manager — and a minimum lead time of five working days. Every request that arrives “for Monday” on a Friday afternoon costs more and gets fewer of the checks below.
Manual set-up vs zero-touch onboarding with Autopilot and Entra ID
Most UK SMEs still onboard the way they did in 2015: someone buys a laptop from a reseller, unboxes it in the office, signs in with a local admin account, installs Office, the VPN client, the PDF editor and the accounts package one by one, creates the user in the Microsoft 365 admin centre by copying an existing colleague, and writes the temporary password on a sticky note. It works, after a fashion, but it takes a technician most of a day per starter and it produces a slightly different machine every time.
The alternative is zero-touch onboarding. The laptop is registered with Windows Autopilot by the reseller at the point of sale, so its hardware hash is already in your tenant. It ships sealed, direct to the new starter’s home or the office. When they power it on and connect to Wi-Fi, it recognises your organisation, asks them to sign in with their work account, joins Entra ID, enrols in Intune and pulls down its applications, security baseline, BitLocker encryption and Wi-Fi profiles automatically. Access is granted by dynamic or assigned groups that reflect the person’s department and role.
Manual onboarding
Hand-built laptop, copied user
Zero-touch onboarding
Autopilot, Intune and role-based groups
Zero-touch is not only for large enterprises. Windows Autopilot and Intune are included in Microsoft 365 Business Premium, which many UK SMEs already license for its security features. The investment is in the initial design — the configuration profiles, the app packaging, the group structure — and that is usually a one-off project of a few days, after which every subsequent starter benefits. For businesses still on Business Standard, the case for moving up a tier is often made by onboarding and device management alone, before you count Defender for Business and Conditional Access. If you are weighing up licence tiers at the same time as AI add-ons, our Microsoft 365 Copilot licensing cost guide sets out how the layers stack.
Onboarding readiness scoring — where most UK SMEs sit today
Before you rebuild the process, it helps to be honest about where you are starting from. The score cards below reflect the patterns we see most often when reviewing joiner processes in UK organisations of 10 to 250 people. “High risk” means a gap that regularly causes either a security exposure or a lost first day; “medium” means friction and rework; “low” means the area is usually handled adequately.
The pattern is consistent: devices and paperwork are usually handled reasonably well, while identity and access — the area that matters most for security — is where shortcuts accumulate. “Copy Sarah’s permissions” is the single most common source of over-privileged accounts in small businesses, because Sarah has been there six years and has collected access to every project, every shared mailbox and the finance folder she once needed for a month in 2021. The new starter inherits all of it.
New starter onboarding by the numbers
The figures below are typical ranges for UK SMEs running Microsoft 365, drawn from our own onboarding projects and from published Microsoft and industry guidance. They are not guarantees for any individual business; they are useful for setting expectations with directors and hiring managers.
The five-day lead time is the one that matters most and is most often ignored. It covers the time a reseller needs to ship a pre-registered device, the time to create the identity and let group memberships and licences propagate, and a buffer for the inevitable question about which applications the person needs. Where businesses keep a small pool of spare Autopilot-registered laptops, the device element can drop to same day — but the access decisions still need a hiring manager’s input in advance.
Where does first-day time actually go when the process is not designed? The chart below shows the share of new starters in a typical unmanaged process who lose meaningful time to each issue during their first week.
Almost every item on that list is an access-definition problem rather than a technical one. Nobody told IT which shared mailbox the role needs, or which finance package licence to buy, or that the person would be answering the sales line. That is why the checklist later in this article starts with a role template rather than with the laptop.
Onboarding maturity benchmarks for UK SMEs
A useful way to plan improvement is to look at which onboarding controls are already common and which are still rare. The progress rows below show the approximate share of UK organisations with 10–250 staff that we typically find doing each thing consistently for every new starter — not occasionally, not “when we remember”, but every time. They are indicative ranges rather than survey statistics, but they line up closely with what Cyber Essentials assessors and cyber insurers report when they ask the same questions.
Share of UK SMEs doing this for every new starter
Two things stand out. First, the basics — a named account and a signed policy — are close to universal, so most businesses are not starting from zero. Second, the controls that make onboarding repeatable (role groups, Intune enrolment, Autopilot) are the least common. Those are also the controls that make offboarding reliable later, because the same groups that grant access on day one are the ones you remove on the last day.
Cyber Essentials v3.3 is relevant here even if you are not certified. Its user access control requirements expect every account to be unique, administrative rights to be granted only where needed and on separate accounts, and accounts to be created through an approval process. Its secure configuration requirements expect default passwords to be changed, unnecessary software removed and devices locked after inactivity. A well-designed joiner process satisfies all of these automatically for every new device and account; a manual one relies on the technician remembering each item each time.
The onboarding timeline — from signed contract to first week
The timeline below is a practical sequence for a hybrid UK SME using Microsoft 365 Business Premium, Intune and Autopilot. Adjust the day counts to your own lead times, but keep the order: access decisions first, identity second, device third, people last.
The single most important change in that sequence, for most businesses, is the gap between “access confirmed” and “identity created”. When the account is created only on the morning of day one, licences and group memberships are still propagating while the new starter is trying to sign in, and the first hour is lost to “it says I don’t have access”. Creating the identity two or three days ahead, but leaving it unusable until the Temporary Access Pass becomes valid, removes that problem without opening a security gap.
Decision framework — how ready is your onboarding process?
Score your current process out of 100 using the weightings below. Give yourself the full points only if the item happens for every new starter, not just most of them.
- Written runbook and single request form — 15 points
- Role templates mapped to Entra ID groups — 20 points
- Group-based licensing — 10 points
- Temporary Access Pass or in-person credential handover — 10 points
- MFA and Conditional Access enforced from first sign-in — 15 points
- Autopilot and Intune device build with BitLocker — 15 points
- Standard user accounts, no local admin — 5 points
- Week-one security induction and policy acknowledgement — 5 points
- Closed ticket with evidence and asset register update — 5 points
A score below 50 usually means onboarding depends on one or two people and would struggle if three people started in the same week. Between 50 and 75, the process works but carries avoidable risk — most often in access copying and credential handover. Above 75, you have a process that scales and produces audit evidence as a by-product. The quickest gains almost always come from the role templates and the request form, because they cost nothing in licensing and they fix the access-definition problems shown in the bar chart above.
What new starter onboarding costs — licences, devices and time
The table below shows typical per-starter costs for a UK SME. Licence prices are indicative list prices excluding VAT on annual commitment and change periodically; device prices reflect a mid-range business laptop. Labour is shown at a blended managed IT support rate.
| Cost element | Manual process | Zero-touch process | Notes |
|---|---|---|---|
| Microsoft 365 licence | £10–£19 per user per month | £18–£19 per user per month (Business Premium) | Premium includes Intune, Autopilot, Entra ID P1 and Defender for Business |
| Business laptop | £700–£1,200 | £700–£1,200 | Autopilot registration by reseller is usually free or a small fee |
| Technician time per starter | 4–8 hours (£260–£520) | 0.75–1.5 hours (£50–£100) | Based on a blended rate of around £65 per hour |
| Courier or collection | Starter travels to office | £10–£25 tracked delivery | Signed-for delivery recommended for asset tracking |
| One-off design project | None | £1,500–£5,000 | Groups, profiles, app packaging and runbook; scales with application count |
For a business taking on ten to fifteen people a year, the time saved per starter typically covers the one-off design project within the first year, before you count the value of a new employee being productive on day one or the reduced risk of over-privileged accounts. For businesses hiring two or three people a year the financial case is thinner, but the security and consistency case is the same — and the same Intune configuration also handles laptop replacements, repairs and rebuilds, which every business has regardless of headcount growth.
Be wary of comparing only the licence line. Business Standard is cheaper per user, but it does not include Intune, Conditional Access or Autopilot, so the “cheaper” option often carries a hidden technician cost on every starter, every rebuild and every leaver. Our guide to IT support cost per user in the UK shows how onboarding effort feeds into a managed support quote.
Where onboarding effort goes when it is designed properly
Once a zero-touch process is in place, the remaining technician effort shifts away from building machines and towards the decisions only a person can make. The donut below shows the approximate share of remaining onboarding effort that goes on access decisions and exceptions — confirming the role template, handling the one-off requests, and checking that what was granted matches what was asked for.
That is exactly where the effort should be. Building a laptop is a mechanical task that software does better than people. Deciding whether a new account manager should see the finance team’s SharePoint site is a business decision that needs a human, and ideally the same human who will approve it when the person moves role. The more of your onboarding time is spent on those decisions rather than on installers and drivers, the better your process is working.
The new starter IT onboarding checklist — the 12-point essentials
This is the core of the process. Each item is written so that it can be ticked off by whoever is running onboarding that week, and so that the evidence it leaves behind is useful for Cyber Essentials, cyber insurance renewals and your own access reviews.
- Receive a complete joiner request at least five working days ahead. One form, one ticket. Legal and preferred name, job title, department, line manager, start date, location, working pattern and role template. Reject or chase incomplete requests rather than guessing.
- Confirm the role template and any exceptions with the hiring manager. The template defines standard groups, licences, shared mailboxes, Teams and applications for that role. Exceptions are listed by name and approved by the manager, so they can be reviewed later.
- Allocate or order an Autopilot-registered device. Ask your reseller to register the hardware hash to your tenant at purchase. Assign the device to the user and to the correct Autopilot deployment profile. Record serial number and asset tag in the asset register.
- Create the identity in Entra ID with consistent naming. Use the agreed format for UPN and email address, set the display name, job title, department, manager and usage location (United Kingdom) — dynamic groups and the address book depend on these attributes being right.
- Add the user to role and department groups, not individual resources. Teams, SharePoint sites, shared mailboxes and app assignments should flow from group membership. Never “copy” another user’s access.
- License by group. Use group-based licensing so the Microsoft 365 licence and any add-ons arrive with the role group. This also makes licence reconciliation and leaver clean-up far simpler.
- Prepare a Temporary Access Pass for first sign-in. Issue a time-limited, single-use Temporary Access Pass valid from the morning of day one. Hand it over by phone or in person — never in the same email that tells the person their username.
- Enforce MFA and Conditional Access from the first sign-in. The starter should register Microsoft Authenticator (or a FIDO2 key) and Windows Hello for Business during set-up. Conditional Access should require a compliant device for access to company data.
- Confirm the device build completes with the security baseline. BitLocker encryption on, Defender active, Windows updates and app updates managed, firewall on, auto-lock configured, standard user rights only. Check device compliance status in Intune on day one.
- Set up phone, printing and line-of-business apps. Teams Phone or VoIP extension, printer deployment via Universal Print or Intune, and SSO-connected apps such as the CRM, accounts package or practice management system.
- Deliver a short security and systems induction in week one. How to report phishing, how to contact IT support, where files live, the acceptable use and password policies, and how to lock a screen. Record the policy acknowledgement.
- Close the ticket with evidence. Attach or record groups, licences, device serial, compliance status, MFA registration and policy acknowledgement. Schedule a 90-day access review for anyone granted exceptions.
Mobile phones follow the same principles. Company-owned phones should be enrolled in Intune as corporate devices. For personal phones used for email and Teams, Intune app protection policies (sometimes called MAM) protect company data inside Outlook and Teams without taking control of the whole handset — which also keeps you on the right side of BYOD expectations under UK GDPR and Cyber Essentials.
If you are also reviewing how laptops join your Wi-Fi, the same Entra ID identity and Intune-delivered certificates can authenticate devices to the office network without a shared passphrase — see our guide to WPA3-Enterprise and 802.1X Wi-Fi with Meraki and Entra ID. A new starter then gets office Wi-Fi access automatically with their device, and loses it automatically when they leave.
Mini case study — a 45-person Bristol architecture practice
A 45-person architecture practice in Bristol was taking on eight to twelve people a year, mostly graduates in September and a handful of experienced hires through the year. Onboarding was handled by the practice manager and an external IT provider on a pay-as-you-go basis. Each starter’s laptop was built by hand in the office, which meant the starter could not have it until they arrived, and design software licences were often still being sorted out on day two or three. Access to project folders was granted by copying an existing architect’s permissions, which over time had given several junior staff access to the partners’ finance and HR folders.
The practice moved to Microsoft 365 Business Premium and spent a short project defining four role templates — partner, architect, technologist and studio support — each mapped to Entra ID groups for SharePoint project sites, Teams, shared mailboxes and app assignments. The reseller began registering every new laptop with Autopilot at purchase. The CAD and rendering applications were packaged for Intune, and licences for them were tied to the role groups where the vendor supported it.
The next September intake of five graduates received their laptops at home the week before starting, signed in on their first morning with a Temporary Access Pass, and were working in their project Teams by mid-morning. The access review that accompanied the project removed finance and HR folder access from eleven accounts that had inherited it by copying. The practice manager now completes a single form per starter and no longer handles devices at all.
“The biggest change wasn’t the laptops turning up ready, although that was nice. It was that for the first time we could actually say who had access to what and why. When we went through Cyber Essentials the following spring, onboarding was the easiest section to evidence.” — Practice manager, Bristol architecture practice
The lessons generalise well beyond architecture. Most of the value came from the role templates and the request form, not from the technology itself. Autopilot made the device element smoother, but the practice could have removed the over-privileged access with the role groups alone.
Common new starter onboarding mistakes to avoid
These are the errors we see most often when reviewing joiner processes. None of them is unusual, and most are the result of good people taking reasonable shortcuts under time pressure.
- Copying another user’s permissions. It is fast, but it propagates every historical exception to the new starter. Over a few years it produces a business where most people can see most things.
- Emailing the temporary password. Sending the username and password to the starter’s personal email, or to the manager, puts a working credential in a mailbox you do not control. Use a Temporary Access Pass delivered separately.
- Granting local admin rights “so they can install things”. This undermines your malware defences and breaches the Cyber Essentials expectation that admin rights are restricted. Deploy apps through Intune or the Company Portal instead.
- Creating the account on the morning of day one. Licences and group memberships take time to propagate. Create the identity a few days ahead and control first use with the Temporary Access Pass start time.
- Skipping MFA registration “until they’re settled in”. New accounts without MFA are a known target. Registration should be part of the first sign-in, not a follow-up task.
- Not recording the device. If the serial number and asset tag are not recorded against the person, recovering the device when they leave becomes a negotiation rather than a process.
- Treating onboarding and offboarding as separate projects. The groups that grant access on day one should be the same groups you remove on the last day. Designing one without the other leaves gaps at both ends.
- No owner for the process. When onboarding is “everyone’s job”, the checklist drifts within months. Name an owner, even if the work is done by a managed IT support provider.
Contractors, temps and work-experience placements are where most of these mistakes cluster, because they are seen as “not really staff”. They need the same identity controls, an expiry date on the account set at creation, and a sponsor who confirms each month that access is still needed. Guest access in Entra ID is often a better fit than a full licensed account for short-term collaborators.
At-a-glance summary — new starter IT onboarding
| Item | Recommended approach |
|---|---|
| Trigger | Single joiner form or HR system record, one ticket per starter |
| Minimum lead time | Five working days from request to start date |
| Access model | Role templates mapped to Entra ID groups; exceptions named and approved |
| Licensing | Group-based licensing, usually Microsoft 365 Business Premium |
| Identity creation | Two to three days before start, consistent naming and attributes |
| Credential handover | Temporary Access Pass, delivered separately from the username |
| Authentication | MFA and Windows Hello for Business registered at first sign-in |
| Device build | Windows Autopilot and Intune, shipped direct to the starter |
| Device security | BitLocker, Defender, managed updates, standard user rights |
| Phones | Intune enrolment for corporate devices; app protection for personal ones |
| Induction | 30-minute security and systems session in week one |
| Policy | Acceptable use acknowledgement recorded electronically |
| Evidence | Ticket closed with groups, licences, device serial and compliance status |
| Review | 90-day review of exceptions; access removed through the same groups at leaving |
How Cloudswitched helps with new starter onboarding
Cloudswitched designs and runs joiner–mover–leaver processes for UK businesses as part of our managed IT support. That typically includes defining role templates with your managers, building the Entra ID group and licensing structure, configuring Windows Autopilot and Intune with a security baseline aligned to Cyber Essentials, packaging your line-of-business applications, and taking on the day-to-day onboarding tickets so your office manager no longer has to. We work with the Microsoft 365 licences you already have where possible and set out clearly where an upgrade would change what is achievable.
Make every new starter’s first day a working day
Our IT support team can review your current onboarding process, design role-based access and set up zero-touch laptop deployment for your business.
Talk to us about IT SupportFrequently Asked Questions
What should a new starter IT onboarding checklist include?
A practical new starter IT onboarding checklist covers six areas: a complete request from HR or the hiring manager with enough lead time; a role template that defines standard access; identity creation in Entra ID with consistent naming and group membership; licensing, ideally assigned by group; a secured device built through Autopilot and Intune with encryption and standard user rights; and a first-day handover that includes MFA registration, a short security induction and acknowledgement of your acceptable use policy. The checklist should finish with a closed ticket recording what was granted, so the same access can be reviewed when the person moves role and removed when they leave.
How much notice does IT need for a new starter?
Five working days is a sensible minimum for most UK SMEs. That allows time to confirm access with the hiring manager, ship a pre-registered laptop to the starter’s home or office, create the identity a few days ahead so licences and group memberships propagate, and run pre-start checks. Businesses that keep a small stock of spare Autopilot-registered laptops can handle shorter notice for the device, but the access decisions still need a manager’s input. Same-day requests are possible in an emergency, but they are where most security shortcuts happen.
What is Windows Autopilot and does a small business need it?
Windows Autopilot is a Microsoft service that lets a new Windows laptop configure itself for your organisation the first time it is switched on. The reseller registers the device to your tenant at purchase; when the user signs in with their work account, the device joins Entra ID, enrols in Intune and installs its apps and security settings automatically. It is included in Microsoft 365 Business Premium, so many small businesses already have it. It is most valuable for hybrid and remote teams, for businesses hiring more than a few people a year, and for anyone who wants every laptop built to the same standard without a technician touching it.
How should we give a new starter their first password securely?
The preferred approach in Microsoft 365 is a Temporary Access Pass: a time-limited passcode, valid from a start time you choose, that lets the person sign in once and register their own MFA method and Windows Hello for Business. It should be delivered separately from the username — by phone, in person, or through the line manager — and never sent to a personal email address alongside the account name. If you are not yet using Temporary Access Pass, a one-time password that must be changed at first sign-in, delivered by a separate channel, is the minimum standard.
Should new starters have local administrator rights on their laptop?
No, in almost all cases. Standard user rights are an expectation of Cyber Essentials, which requires administrative access to be restricted to those who need it and used through separate accounts. Local admin rights make it much easier for malware to take hold and for unapproved software to be installed. The usual reason for granting them — “so they can install what they need” — is better handled by publishing approved applications in the Intune Company Portal, where users can install them on demand without elevated rights. Developers and some technical roles may need managed elevation tools for specific tasks.
Why is copying another user’s access a problem?
Copying access feels efficient, but it transfers every historical permission the existing user has collected, including temporary access that should have been removed years ago. Over time, it produces accounts that can see far more than their role requires, which increases the impact of a compromised account and makes access reviews almost impossible. Role templates mapped to Entra ID groups solve this: the new starter receives the standard access for their role plus named, approved exceptions, and nothing else.
Which Microsoft 365 licence do we need for zero-touch onboarding?
Microsoft 365 Business Premium is the usual choice for UK SMEs with up to 300 users, because it includes Intune, Windows Autopilot, Entra ID P1 (for Conditional Access and group-based licensing) and Defender for Business. Business Standard and Business Basic do not include Intune or Conditional Access. Larger organisations or those with specific compliance needs may use Microsoft 365 E3 or E5. It is often possible to license Business Premium only for the users who need managed devices, but mixing tiers adds complexity to group design.
How does onboarding relate to Cyber Essentials?
Several Cyber Essentials controls are applied at onboarding. User access control expects unique accounts, an approval process for creating them, MFA on cloud services and restricted admin rights. Secure configuration expects default passwords to be changed, unnecessary software removed and screens to lock automatically. Malware protection and security update management expect every new device to be protected and patched from day one. A consistent onboarding process means every new account and device meets these standards automatically, and the evidence is ready when your assessor asks for it.
What about personal phones used for work email?
For personal phones, Intune app protection policies are usually the right approach. They protect company data inside apps such as Outlook and Teams — for example preventing copy and paste into personal apps and requiring a PIN — without enrolling or controlling the whole device. Company-owned phones should be fully enrolled in Intune. Whichever you choose, include the decision in the role template and the acceptable use policy, and cover it in the first-day induction so the starter understands what the business can and cannot see.
Can a managed IT support provider run onboarding for us?
Yes. Many UK SMEs hand day-to-day joiner, mover and leaver tasks to their managed IT support provider, with the business retaining ownership of access decisions through the hiring manager and the role templates. The provider typically designs the groups and device configuration once, then processes each joiner request as a standard ticket within an agreed lead time. Check that the support agreement defines onboarding as an included service request, states the notice period it needs and specifies the evidence it will record for each starter.
How long does it take to set up a zero-touch onboarding process?
For a typical SME with up to 100 users and a modest number of line-of-business applications, the design and build usually takes between one and four weeks of elapsed time. The work covers role templates and groups, Autopilot deployment profiles, Intune configuration and compliance policies, Conditional Access, application packaging and a written runbook. The bulk of the variation comes from the applications: a business running only Microsoft 365 and a browser-based CRM is quick, while one with several desktop design or accounts packages needs more packaging and testing.
Related reading
These guides cover the other stages of the employee and device lifecycle, and the licensing and security decisions that sit alongside onboarding.
Onboarding, devices and access — handled as part of your IT support
Cloudswitched provides managed IT support for UK businesses, including joiner and leaver processes, Intune device management and Microsoft 365 administration.
Explore our IT Support service








