IT Onboarding Checklist: 10 Steps for New Starters
A new employee arrives on Monday morning.
Their laptop is still being configured.
They cannot access the shared files they need.
Nobody is quite sure which software licence to give them.
By lunchtime, three different people are involved in getting them set up.
It is frustrating for the new starter, but it also wastes time across HR, management and IT.
A clear IT onboarding checklist prevents that situation.
For growing SMEs, a good new starter IT setup is not simply about creating an email address. It is about giving somebody the right tools, access and security from day one - without relying on last-minute requests and individual memory.
If a new employee cannot work properly on their first day, that is usually a process problem rather than an IT problem.
Why does good IT onboarding matter as your business grows?
Informal onboarding often works when a business is small.
Someone tells IT that a new person is joining.
A laptop is found.
Their manager explains where everything is.
Everyone fills in the gaps.
As the business grows, that approach becomes harder to manage.
You may have:
More departments
Hybrid and remote employees
Different software requirements
More Microsoft 365 groups and Teams
Greater security requirements
Employees joining at different locations
The cost of poor onboarding also becomes more noticeable.
Managers lose time chasing access.
New employees wait instead of working.
IT receives urgent requests that could have been planned days earlier.
Security shortcuts get taken because everybody wants to get the employee operational quickly.
A consistent employee onboarding process removes much of that friction.
1. Start the IT setup before the employee's first day
Good onboarding should begin as soon as the start date is confirmed.
IT needs enough notice to understand:
Who is joining
Their start date
Their job role
Where they will work
Who their manager is
What equipment they need
Which systems they require
This sounds obvious.
Yet we regularly see IT teams or support providers finding out about a new starter a day or two before they arrive.
That immediately turns a planned task into an urgent one.
A simple process between HR, managers and IT can prevent this.
📅 Ideally, the new starter request should trigger the setup process automatically rather than depending on somebody remembering to send an email.
2. Give them the right equipment for their role
Not every employee needs the same setup.
An office-based administrator may have very different requirements from an engineer visiting customer sites.
Before ordering or assigning equipment, consider:
Laptop or desktop
Monitors
Docking station
Headset
Mobile device
Keyboard and mouse
Specialist hardware
Remote-working equipment
Standardisation is useful.
Having a small number of approved device types makes support, replacement and security easier.
But standardisation should not mean giving everyone identical equipment regardless of how they work.
The cheapest device is rarely the cheapest option if the employee loses time using it every day.
The objective is to provide equipment that fits the role without overcomplicating the estate.
3. Create accounts before the employee arrives
A new starter should not spend their first morning waiting for an email account.
Their Microsoft 365 account should normally be prepared before they start.
That may include:
Email
Microsoft Teams
OneDrive
SharePoint access
Relevant Microsoft 365 groups
Business applications
Telephone services
Other company systems
The exact setup should depend on the role.
This is where templates can help.
For example, every new member of the finance team may need a similar baseline set of tools.
Every project manager may require another.
Role-based setup is usually more reliable than rebuilding access from scratch for each employee.
4. Make security part of the setup from day one
Security should not be something added later.
It should be part of the employee's first login.
Depending on your environment, this may include:
🔒 Multi-factor authentication
🔒 Secure password setup
🔒 Device encryption
🔒 Endpoint protection
🔒 Screen-lock policies
🔒 Managed software updates
🔒 Controlled access to business systems
A common mistake is relaxing security temporarily because somebody needs to start work quickly.
That might mean sharing a password, leaving multi-factor authentication until later or giving broader access than required.
Those temporary workarounds have a habit of becoming permanent.
Security becomes much easier when the correct controls are part of onboarding rather than something you try to fix six months later.
5. Give people the access they need - not everything
New employees need enough access to do their jobs.
They do not need access to every file and system in the company.
For Microsoft 365 onboarding, this means thinking carefully about:
Teams
SharePoint sites
Shared mailboxes
Microsoft 365 groups
Shared calendars
Departmental files
Customer information
Imagine a new operations employee joins the business.
Giving them access to the entire company SharePoint environment may be quicker than deciding what they genuinely need.
But they may now be able to view finance, HR or management information unnecessarily.
That is not good access management.
A better principle is simple:
Start with what the role needs. Add more access when there is a genuine business reason.
This reduces both security risk and clutter for the employee.
6. Make sure files are easy to find
Access alone is not enough.
A new employee can technically have permission to everything they need and still have no idea where anything lives.
Their manager should be able to explain:
Where customer files are stored
Where internal documents live
Which Teams are important
When to use OneDrive
When to use SharePoint
Where templates and procedures are kept
This is where poor Microsoft 365 structure becomes obvious.
Existing employees often learn to work around messy file storage because they know its history.
A new starter does not.
If every employee needs a guided tour of ten different folders to find basic information, the problem is probably the structure.
Onboarding can therefore be a useful test of how easy your systems are to understand.
7. Install the software they actually need
Software access should also follow the employee's role.
A useful IT onboarding checklist should identify:
Standard company applications
Department-specific software
Browser requirements
Microsoft 365 licences
Industry applications
Security tools
Remote-access requirements
Avoid installing software simply because everyone else has it.
Unused software adds cost and can create unnecessary support or security overhead.
The same applies to licences.
A new employee should have the Microsoft 365 licence that matches their requirements rather than automatically receiving the most expensive or most common plan.
✅ Good onboarding is also an opportunity to keep your software estate under control.
8. Explain how your business actually uses Microsoft 365
Giving somebody Teams does not mean they know how your business uses Teams.
The same applies to SharePoint, OneDrive and Outlook.
Your employee onboarding process should explain practical rules such as:
Where internal conversations should happen
Which Teams channels matter
Where shared files should be stored
When email is more appropriate
How meetings are booked
How documents should be shared
Where company-wide information is kept
This does not require a two-hour Microsoft training session.
A short explanation of how your company works is usually more useful.
Every business uses Microsoft 365 slightly differently.
The new employee needs to understand your way of working, not every feature Microsoft provides.
9. Cover cyber security without overwhelming people
Security awareness should be part of onboarding, but keep it practical.
New employees should understand:
How to recognise suspicious emails
How to report a potential phishing message
Why they should not share passwords
How to handle sensitive information
What to do if a device is lost
Who to contact if something feels wrong
Avoid turning the first day into a long security lecture.
The aim is to give people simple rules they can actually remember.
For example:
⚠️ Unexpected payment request? Verify it another way.
⚠️ Microsoft login page from an unusual email? Do not rush to sign in.
⚠️ Lost laptop? Report it immediately.
Employees are part of your security setup.
They should know what the business expects from them from the beginning.
10. Check everything works before the employee needs it
One of the most valuable steps is also one of the simplest.
Test the setup.
Before the employee starts, check that:
The device starts correctly
Their account works
MFA can be configured
Required software is installed
Teams is available
Shared files can be accessed
Email is working
Printers or specialist equipment are available where needed
This avoids discovering problems while the employee and their manager are waiting.
For remote employees, it matters even more.
Posting a laptop on Friday and hoping everything works on Monday is not much of a process.
A short pre-start check can prevent hours of disruption later.
What should happen during the employee's first week?
IT onboarding should not finish at 9am on day one.
After a few days, employees have a better understanding of what they actually need.
That is a good point to check:
Is anything missing?
Do they have unnecessary access?
Are they struggling to find files?
Is their equipment suitable?
Are any applications not working?
Do they understand how to get IT support?
Managers should also review access if the role changes during onboarding.
Giving somebody more permissions is easy.
Remembering to remove permissions they no longer need is much harder.
A short first-week review keeps the setup accurate.
What should you avoid during new starter IT setup?
Several mistakes appear repeatedly.
Avoid copying another employee's access without checking it
It is tempting to say:
“Give the new starter everything Jane has.”
That can save time.
It can also copy years of unnecessary permissions.
Jane may have changed roles, worked on temporary projects or accumulated access she no longer needs.
Use role requirements as the starting point instead.
Avoid shared user accounts
Giving multiple people the same login might seem convenient.
It creates problems around security, accountability and offboarding.
Where possible, employees should use individual accounts.
Avoid personal devices by default
Bring-your-own-device arrangements can work for some businesses.
They need proper rules and security controls.
Allowing employees to use personal laptops simply because company equipment was not ready is not a strategy.
Avoid making the new employee responsible for discovering what they need
A new starter does not know your systems yet.
They should not have to spend their first week gradually finding out which applications and folders they are missing.
The business should define the baseline requirements for the role.
Could onboarding be automated?
Parts of it can.
Growing businesses often have highly repetitive onboarding tasks.
For example, once HR confirms a new starter, a workflow could:
Notify IT.
Create an equipment request.
Inform the manager.
Add onboarding tasks to a shared list.
Send reminders before the start date.
Confirm when key actions are complete.
Microsoft Power Automate can support workflows like these where the underlying process is clear.
The important part is getting the process right first.
Automating a disorganised onboarding process only gives you disorganisation at higher speed.
Define who does what.
Then automate the repetitive steps.
How does better onboarding save the business time?
A good onboarding process reduces work in several places.
The new starter becomes productive sooner.
Their manager spends less time chasing access.
HR receives fewer questions.
IT deals with planned requests instead of urgent ones.
Security is more consistent because access and devices follow an agreed process.
The individual time saving on each task may seem small.
Across every employee you recruit, it becomes significant.
There is also a less measurable benefit.
A smooth first day gives a new employee confidence that the business is organised.
A chaotic one sends the opposite message.
Should onboarding and offboarding use the same process?
They should be connected.
Many of the things you create when somebody joins eventually need reviewing when they leave.
That includes:
User accounts
Microsoft 365 licences
Devices
SharePoint access
Teams memberships
Business applications
Email
OneDrive files
Telephone access
If you maintain a reliable record of what an employee receives during onboarding, offboarding becomes much easier.
This also helps when someone changes role internally.
IT access should follow the employee's current responsibilities rather than staying frozen from the day they joined.
What does a good IT onboarding process look like?
For most SMEs, good onboarding is not complicated.
It is repeatable.
✅ IT receives enough notice.
✅ Equipment matches the role.
✅ Accounts are prepared in advance.
✅ Security is enabled immediately.
✅ Access follows genuine business need.
✅ Microsoft 365 is structured clearly.
✅ Software and licences are appropriate.
✅ Employees know the basics.
✅ The setup is tested.
✅ Somebody reviews it after the employee starts.
Most importantly, ownership is clear.
HR should know what information IT needs.
Managers should know what access to request.
IT should know what needs preparing.
The new employee should not have to coordinate everyone else.
The practical takeaway
A strong IT onboarding checklist does more than make somebody's first day smoother.
It reduces wasted management time, improves security and creates a consistent way to bring people into a growing business.
You do not need a complicated onboarding platform to get started.
First, document what should happen every time somebody joins.
Then define who owns each step.
Once that works consistently, look at where Microsoft 365 and automation can remove repetitive admin.
Good onboarding should feel uneventful. The employee arrives, everything works and they can focus on the job they were hired to do.
People Also Ask
What should be included in an IT onboarding checklist?
An IT onboarding checklist should cover equipment, user accounts, Microsoft 365 access, software, security controls, shared files, communication tools and a final check that everything works before the employee starts.
When should IT onboarding start for a new employee?
IT onboarding should start as soon as the employee's start date and role are confirmed. Giving IT enough notice allows equipment, accounts, access and security controls to be prepared before the first day.
What Microsoft 365 access does a new starter need?
The right access depends on the employee's role. It may include Outlook, Teams, SharePoint, OneDrive, shared mailboxes and relevant Microsoft 365 groups. Employees should only receive access they genuinely need.
How can businesses make employee onboarding more secure?
Businesses can improve onboarding security by enabling multi-factor authentication, protecting devices, controlling permissions, using individual accounts and giving new employees clear cyber security guidance from day one.
Can Microsoft 365 automate employee onboarding?
Parts of the onboarding process can be automated using tools such as Power Automate. Businesses can automate notifications, approval steps, task creation and reminders, but the underlying process should be clear before automation is introduced.
How often should new starter access be reviewed?
Access should be checked after the employee has settled into the role and whenever their responsibilities change. Regular reviews help remove unnecessary permissions that may have accumulated over time.
