A new hire is ready on day one when IT has already created their own Microsoft 365 account, prepared a managed laptop, planned their MFA sign-in, and granted only the files, mailboxes, and apps the job needs.
Most onboarding work should be finished before the person walks in. Gallup reported in 2018 that only 12% of employees strongly agreed their organization did a great job onboarding new employees. I can’t tell you how much of that gap is the IT side. Some of it is. A laptop still in its box at 10 a.m. tells a new employee something, whether anyone meant it to or not.
Passwords are the first thing people call our help desk and remote IT support team about. Printers come second. A new hire can produce both calls before lunch on the first day. Neither one has to happen.
What follows is the IT half of onboarding, in the order it has to happen, with a note on who owns each step. HR owns the other half.

Watch: IT Onboarding Checklist for New Hires: Day One Ready
Video chapters
- 0:00 Intro
- 0:13 What IT Needs From You, and When
- 0:37 One Person, One Account
- 1:04 Getting Through the First Sign-In
- 1:47 The Laptop Should Be Finished Before Anyone Sees It
- 2:18 Access by Role, Not by Resemblance
- 2:43 The First Week and the Written Record
- 3:15 Things HR Tends to Ask IT
Read full transcript
A laptop still in its box at ten in the morning tells a new hire something, whether anyone meant it to or not. The IT work should be finished before the person walks in. Here’s the IT half of onboarding, in the order it has to happen.
It starts with an email. The moment an offer is accepted, send IT the name the person goes by, their title, their manager, the start date, where they’ll start, and any software outside Microsoft three sixty-five. Then work backward from the start date. A week out, the laptop is ordered or reset. A few days before, the account is created. The day before, the laptop is confirmed. Then sign-in, training, and a review at ninety days.
The most tempting shortcut is handing the new hire the old employee’s login. It feels efficient. It isn’t. That account still carries the last person’s sign-in setup, and everything done from it gets logged under a name that no longer describes who did it. Microsoft’s own process gives you what the shortcut promised. Convert the old mailbox to a shared mailbox, block sign-in on it, and give the new hire permission to open it. Customer history stays available, and nobody signs in as someone else.
This is where first mornings stall. In a tenant using security defaults, a new account has to register for MFA the first time it’s used. So the new hire needs their phone, charged, with Microsoft Authenticator already installed. Ask them to do that a few days early. And never put a password in an email. Microsoft built a feature for exactly this moment, the Temporary Access Pass. It’s a time-limited passcode an administrator creates for one person. It expires on its own. A password in a welcome email doesn’t. Hand the pass over in person, or read it out on a video call once you can see who you’re talking to. Set up the password manager next, while IT is still sitting with them. Day one is the easiest moment to start, before any work password lands in a browser or on a sticky note.
On Microsoft three sixty-five Business Premium, a new laptop can arrive ready to set itself up. With Windows Autopilot, the employee powers it on, gets online, and signs in. The settings, apps, security software, and encryption that IT prepared arrive on their own. Choose a standard user account, not an administrator. And put the printer on the laptop before the first print job, not after the first help desk ticket. A laptop that belonged to someone else gets reset to factory condition first. Not cleaned up. Reset.
Set her up like Dana sounds like a complete instruction. It’s also how a new person inherits years of somebody else’s accumulated access. Dana is a fine reference point and a poor model to copy. Grant access through groups named for roles, like front office, project managers, or billing. A new hire joins two groups and gets exactly what the role gets. Change jobs, change groups. Leave, and the groups are the list of what to remove.
Week one still belongs on the list. Security awareness training at hire isn’t an extra, and short is fine. Include one warning. Scammers follow hiring news and pose as the boss, sometimes before the person even starts, asking for gift cards or personal details. So tell the new hire on day one exactly how you’ll contact them and how you won’t. Then write down what you handed over. The account, the laptop, the groups, the password manager seat, and any logins outside Microsoft. Around ninety days in, look again. Remove what they never used. Add what they kept asking for.
You might be wondering whether the new hire can take over the old email address. Their mail, yes. Their account, no. Or whether a ten-person office really needs security training in week one. Size doesn’t change much about this risk, so keep it short and do it anyway. Onboarding and offboarding are two halves of one process. Whatever gets set up on the first day is exactly what someone has to take down on the last. Talk it over with our team. It’s free, with no obligation either way. The link is in the description.
What an IT Onboarding Checklist Covers
An IT onboarding checklist for a new hire is the short list of accounts, devices, access, and security steps that have to be complete before someone can sign in and work safely in their first hour. Kept properly, it also records everything the person was given, which is the list you’ll need the day they leave.
Gallup’s own researchers make a fair point about this. They warn that onboarding often gets confused with basic setup, the workspace and the laptop and the email account. They’re right. Real onboarding is about the job, the team, and what’s expected. Which is exactly why the setup should be done early. When the laptop takes the first morning, the job starts on the second.
For a small business on Microsoft 365, the IT half comes down to six things.
- A Microsoft 365 account and license that belong to this person alone.
- Sign-in security that works on the first try. That means MFA, multifactor authentication, on the phone they actually carry, plus a seat in the company password manager.
- A laptop that is ready before the first morning, either built in advance or registered so it sets itself up securely at first sign-in. The office printer should be part of that setup.
- Access by role. The shared files, mailboxes, and line-of-business apps the job needs, and nothing it doesn’t.
- Ten minutes in the first week on how the company will and won’t contact them, which matters more than it sounds.
- A written record of all of it.
What IT Needs From You, and When
Onboarding usually goes wrong at the handoff, long before anything technical happens. IT can’t build an account for someone it hasn’t heard about. So the first item on the list belongs to whoever signs the offer letter, and it’s an email.
Send IT these details as soon as the offer is accepted.
- Their legal name and the name they actually go by. The second one usually becomes the email address.
- Job title, manager, and start date.
- Where they’ll start, in the office, at home, or some of each, since a remote start changes how the laptop reaches them.
- Which current employee does the most similar work. That’s a reference point, not a template, and the difference gets its own section below.
- Any software outside Microsoft 365. The scheduling system, a supplier portal, the industry application your office runs on.
- Whether they need a new laptop or will get one you already own.
How much notice is enough? For a standard setup on a laptop you already have, a week is comfortable. Two days is tight. If a laptop has to be ordered, the schedule belongs to the reseller and the shipping carrier, not to IT. Send the details the day the offer is signed.
The Checklist, From the Start Date Backward
All of it fits in one table. The timing assumes a small office on Microsoft 365 and about a week of notice.
| When | What gets done | Who owns it |
|---|---|---|
| Offer accepted | Name, title, manager, start date, location, and non-Microsoft apps sent to IT | Owner, office manager, or HR |
| About a week out | New laptop ordered, or an existing one reset to factory condition | IT |
| Three to five days out | Account created and licensed, role groups assigned, password manager seat ready | IT |
| The day before | Laptop confirmed as registered to the company, or built and updated by hand if you don’t use Autopilot | IT |
| First morning | Sign-in with a Temporary Access Pass, then MFA, a password, and the password manager set up | IT, with the new hire |
| First morning | How to reach the help desk, and how the boss will and won’t contact them | Manager and IT |
| First week | Security awareness training, plus a check that files, apps, and printing all work | New hire and manager |
| Around 90 days | Access reviewed against what the job turned out to need, and the record updated | Manager and IT |
One Person, One Account
The most tempting shortcut in all of onboarding is handing the new hire the old employee’s login. The mailbox already holds the customer history. The files are already there. It feels efficient. It isn’t.
Tidiness has nothing to do with why. That account still carries the last person’s MFA registration, most likely on their personal phone. Whatever password they knew, they may still know. People remember. And everything done from that account from now on gets logged under a name that no longer describes who did it, which turns any later question about who sent what, or who deleted which folder, into guesswork. NIST’s catalog of security controls addresses this in control IA-4, which calls for preventing the reuse of identifiers, meaning a previously used individual identifier doesn’t get assigned to a different individual.
Microsoft’s own process for a departing employee gives you what the shortcut promised without the risk. Convert the old mailbox to a shared mailbox, then give the new hire permission to open it. A shared mailbox can hold up to 50 GB without a license, so the old license is free to move to the new person, and Microsoft is explicit that you shouldn’t delete the former employee’s account, because it anchors the shared mailbox and any forwarding. The same documentation adds two cautions. If nobody resets the password during the conversion, the original username and password will continue to work. And a shared mailbox isn’t meant for direct sign-in at all, so block sign-in on that account and leave it blocked.
One more thing before that license moves. The former employee’s OneDrive loses it too, and Microsoft puts an unlicensed OneDrive into read-only mode after 60 days and archives it after 93. Copy anything the business needs to a SharePoint site first.
Customers who still write to the old address? Their mail keeps landing in the shared mailbox, where the new hire can see it.
Getting Through the First Sign-In
This is where first mornings stall.
If your Microsoft 365 tenant uses security defaults, Microsoft’s free baseline protection, new users used to get 14 days to register for MFA. Microsoft removed that grace period starting July 29, 2024. A new account now has to register the first time it’s used, and under security defaults that means the Microsoft Authenticator app, or another authenticator app that generates codes. Microsoft steers tenants that have Entra ID P1, which Business Premium includes, toward Conditional Access instead, and it can be set up to require the same thing. Either way, the person needs their phone, charged, with the app installed, in the first ten minutes of their first day.
Most of the fix is preparation. A few days before the start date, ask the new hire to install Microsoft Authenticator. And don’t put a password in an email.
Microsoft Entra ID has a feature built for exactly this moment, the Temporary Access Pass. It’s a time-limited passcode an administrator creates for one person, and Microsoft describes its most common use as registering authentication details during the first sign-in or device setup. The default lifetime is one hour, and IT can make each pass single-use. Once IT has switched the feature on, a pass can also stand in for the password while a new Windows laptop joins Entra ID. A single-use pass can run out during a slow setup, so it helps to have IT on hand to issue a second. Hand it over in person on the first morning, or, for someone starting from home, read it out on a video call once you can see who you’re talking to.
The pass expires on its own. A password in a welcome email doesn’t. The FTC’s guidance for small businesses is blunt on this point, telling owners to never share passwords on the phone, in texts, or by email. A pass that dies within the hour is a different animal from a password that lasts for years, which is why reading one out on a call is reasonable and mailing a password isn’t. The account still needs a password, too. Let the new hire choose it on the first morning, with IT beside them.
The password manager comes next, while IT is still sitting with them. BitWarden is our recommended system. Day one is the easiest moment to start using one, before any work password lands in a browser or on a sticky note. We cover what separates a business vault from a personal one in our guide to password managers for small business teams. MFA on the email account is where identity security starts, not where it ends, and that is the argument behind our piece on identity and access management beyond MFA.
The Laptop Should Be Finished Before Anyone Sees It
On Microsoft 365 Business Premium, a new laptop can arrive ready to set itself up. Windows Autopilot’s user-driven mode asks very little of the employee. Power it on. Pick a language and keyboard if Windows asks. Get it online. Then sign in with a work account, using a password or the Temporary Access Pass. Microsoft’s description of what follows is short. “The rest of the process is automated.” The company settings, apps, security software, and encryption that IT prepared in Intune arrive on their own, and nobody has to touch the machine.
Autopilot is a one-time project for IT before it becomes a daily convenience, and after that each laptop still needs a few things. It has to run a business edition such as Windows 11 Pro, since Home isn’t on Microsoft’s supported list. It has to be registered to your company, which Microsoft says ideally happens at the manufacturer, reseller, or distributor you bought it from. And the new hire’s license has to be assigned before they sign in. Business Premium qualifies for Autopilot and includes Intune, Entra ID P1, and Defender for Business. Business Standard doesn’t cover Autopilot by itself, so in a Business Standard office the laptop half of this list gets done by hand, the day before. The Microsoft 365 plan you’re on decides how much of onboarding can run on its own, which makes it worth knowing before your next hire rather than during it.

Two settings matter more than the rest. One is the account type. An Autopilot profile lets IT choose whether the person’s account on the laptop is an Administrator or a Standard user. I’d choose Standard. The CIS Controls, a security baseline published by the nonprofit Center for Internet Security, ask that everyday work like email and browsing happen from the user’s primary, non-privileged account, with administrator rights kept on separate accounts. The other is less technical. The printer. It belongs on the laptop before the person’s first print job, not after their first help desk ticket.
What if the laptop isn’t new? A machine that belonged to someone who left gets reset to factory condition before anyone else uses it, after a quick check for files that never synced or anything you’ve been asked to preserve. Not cleaned up. Reset. The previous person’s files, saved browser passwords, cached sign-ins, and whatever they installed all go with it, and the new hire starts on a machine that knows nothing about who had it before.
Access by Role, Not by Resemblance
“Set her up like Dana.” It sounds like a complete instruction. It’s also how a new person inherits years of somebody else’s accumulated access. Dana may still have the folders from the job she held before this one, a shared mailbox nobody removed, and admin rights granted during some project and never taken back. Copy her account and all of it comes along.
Dana is a fine reference point. She’s a poor template. The CIS Controls ask every organization, the smallest included, for a documented process for granting access when someone is hired or changes roles, and the simplest version of that process is a list of groups.
Grant access through groups named for roles, not people. Front office. Project managers. Whoever handles billing. Give SharePoint sites and shared folders to the group rather than to individuals, and do the same with licenses, which the Microsoft 365 admin center can assign to groups as well. A new hire joins two groups and gets exactly what the role gets. Change jobs, change groups. Leave, and the groups are the list of what to remove.
Then there are the accounts that live outside Microsoft entirely. The line-of-business application, the supplier portal, the shipping account, the payroll site. They get forgotten at onboarding and, worse, at offboarding, because nobody wrote them down. List them per role. This is also where shadow IT in a small office tends to begin, when a new hire can’t get into the real tool in week one and quietly signs up for a free one.
The First Week Still Belongs on the List
Security awareness training at hire isn’t an extra. The CIS Controls say to conduct training at hire and, at a minimum, annually, and they place it in Implementation Group 1, the first and smallest tier of the controls. Short is fine. What matters is timing, in the first week, while the person is still forming habits.
One topic belongs in that first conversation above the others. The FTC has warned employers that scammers are following hiring updates on social media and contacting new employees quickly, sometimes before they’ve even started, while posing as the boss. The request is urgent. It often involves gift cards, or a quick text asking for personal or financial details. The FTC’s explanation of why it works is hard to argue with. Many new employees are eager to please, so they’re less likely to question the new “boss.”
The fix costs nothing. Tell the new hire on day one exactly how you’ll contact them and how you won’t. Give them your real number. Say out loud that nobody at the company will ever ask them to buy gift cards by text. It’s the same family of fraud as the fake invoices and wire requests in our business email compromise guide, aimed at the one person in the building least likely to know how you actually write.
The rest of week one is checking that the setup survived contact with the real job. Can they print? Can they open the shared files they were promised? Does the line-of-business app remember them? Do they know how to reach the help desk? That last one is easy to skip. Someone from my team responds within 15 minutes during business hours, which helps only if the new person knows the phone number, the portal, or the web form to use.

Write Down What You Handed Over
Every item on this checklist creates something that has to come back later. The account, the laptop, the group memberships, the password manager seat, the logins outside Microsoft. Onboarding is when that list is easiest to write, because you’re making it anyway.
The CIS Controls describe what an account inventory should hold at a minimum, the person’s name, username, start and stop dates, and department. Add the laptop’s serial number, the groups, and the accounts outside Microsoft, and offboarding becomes a lookup instead of a search. In plenty of small offices that record lives in one person’s head. It shouldn’t. When that person is the one who leaves, the business finds out how much was never written down, which is the problem at the center of the one-man IT shop.
Then, around 90 days in or whenever probation ends, look again. The job a person actually does is rarely the job their access was guessed for on day one. Remove what they never used. Add what they kept asking for. That small review is what keeps this person from becoming the next Dana.
Onboarding and offboarding are two halves of one process, and our managed IT services include help with both. The halves mirror each other. Whatever gets set up on the first day is exactly what someone has to take down on the last.
Things HR Tends to Ask IT
How much notice does IT really need before a start date?
Can the new hire take over the old employee’s email address?
Is it fine to hand them the laptop the last person used?
What changes when someone starts from home?
Do we have to buy another Microsoft 365 license for every hire?
Should new employees get admin rights so they can install their own software?
Does a ten-person office really need security training in week one?
We will look at how new people get set up in your office today, what is missing, and what their first morning should look like. No obligation.

