If you're moving into IT from healthcare or another sector, the Microsoft 365 administrator role is one of the fastest routes to a stable, well-paid career. M365 is everywhere in UK organisations: the NHS alone runs it across thousands of trusts, councils use it, schools depend on it, and every mid-sized business has it humming in the background. But getting the role means clearing the interview stage, and that's where most candidates stumble.
The hiring manager isn't just asking random technical trivia. They're checking whether you can diagnose real problems, whether you understand the underlying concepts (not just clicking buttons), and whether you've thought through the business impact of your decisions. This article walks you through the actual questions you'll face, the logic behind each one, and the answers that convince interviewers you're ready.
This is often the first technical question because it reveals whether you understand the commercial and operational heart of M365.
What they're listening for: Do you know the licence types (Business Basic, Business Standard, Business Premium, enterprise SKUs), can you explain why someone might choose one over another, and do you grasp the concept that features live at the licence level?
A strong answer:
"M365 licences are bundles of services. If someone has Business Basic, they get Exchange, Teams, SharePoint and OneDrive, but not Defender or advanced analytics. Business Standard adds Bookings and scheduling apps. Business Premium adds security features like advanced phishing protection. Enterprise E3 and E5 give you more advanced governance, eDiscovery, and compliance tools. In practice, I'd recommend Business Basic for frontline staff who mainly need email and Teams, Business Premium for managers who need richer security, and E5 for data-sensitive roles. The key is aligning the licence to what the person actually needs. I'd also flag that you pay per user per month, so recommending the cheapest licence that covers the role is a cost-control skill too."
Why this works: You've shown you know the products, you understand business logic (different roles need different tools), and you understand cost management.
This is a real-world scenario question. They're not looking for one magic answer; they're looking at your diagnostic thinking.
A strong answer:
"First, I'd confirm what device and Outlook version they're using. If it's Outlook web access, I'd clear the cache and try a private/incognito window to rule out client-side caching. If it's the desktop client, I'd check whether they're signed in with the right account (cached credentials can cause sync issues), and whether they've recently changed their password. I'd verify their licence includes Exchange (some M365 plans don't). I'd also check whether the calendar folder has the right permissions if they're sharing a calendar. Finally, I'd look at the device sync settings and whether Outlook has offline mode enabled, because offline mode can pause syncing. If none of that works, I'd escalate to check the backend, like whether there's a service incident on the Microsoft status page."
Why this works: You've shown a structured thought process (device, software, credentials, licensing, permissions, settings), you've mentioned checking the status page (which real admins do), and you've ruled out things in a logical order. You haven't just said "restart Outlook."
This tests whether you understand M365 collaboration features at a conceptual level.
A strong answer:
"A distribution group is a one-way list of recipients. When you email the group, the message goes to everyone on it. It doesn't have a mailbox. A shared mailbox is an actual mailbox that multiple people can access directly. People log into it, see the same inbox, and respond to emails as the shared mailbox account. So if you have a support team, a distribution group is good for notifications (everyone gets a copy), but a shared mailbox is better if the team needs to see what others have replied to, because they're all looking at the same inbox. A shared mailbox also has a calendar and contacts storage. Distribution groups are lighter weight and better for informational emails. Shared mailboxes are for collaborative work."
Why this works: You've clarified the technical difference, explained the use cases, and shown you understand the business logic. You've also implicitly shown you know how to manage both.
This tests your understanding of governance and permissions in M365.
A strong answer:
"SharePoint has site-level permissions and library-level permissions. The most practical approach is usually site-level: I'd create a security group (or Microsoft 365 group), add the team members to it, and grant that group permission to the specific sites. That scales better than adding individuals. If they need granular access (some people can only edit, others can only read), I'd set those permission levels at the library level. I'd also consider conditional access policies at the Entra ID level to restrict access based on device, location or risk level if the data is sensitive. The key is that I'd recommend the simplest approach that meets the business requirement, and I'd document it so it's clear how to add new team members later."
Why this works: You've described a practical workflow (groups, not individuals), you've explained scalability, you've mentioned conditional access (showing you know the security layer exists), and you've thought about maintenance.
This tests your knowledge of recovery features and your ability to handle user crises.
A strong answer:
"OneDrive has a recycle bin that retains deleted files for 93 days (the first recycle bin for 93 days, then the admin recycle bin for another 93 days). I'd first ask the user to check their own recycle bin in OneDrive. If the files are there, they can restore them themselves. If not, I'd check the admin recycle bin in the SharePoint admin centre. If they're still not there, I'd check whether they have a backup via OneDrive version history if the files were overwritten rather than deleted. If nothing works, I could restore the entire OneDrive from a snapshot if the organisation has enabled version history or backup, but that's a last resort because it might overwrite other work. I'd also document when the deletion happened so the user can help me narrow down which backup point to restore from."
Why this works: You've shown you know the recovery tools, you've explained the timescales, you've taken a logical step-by-step approach, and you've mentioned documentation.
Beyond the individual answers, interviewers are assessing:
Most candidates fail because they either memorise disconnected facts or they admit they don't know something and then go quiet. Instead, talk through what you would do, what you'd check, and where you'd look it up if needed.
The best preparation is hands-on. If you don't have lab access, Microsoft offers free trials. Create some test users, set up shared mailboxes, experiment with groups and permissions, and deliberately break something so you know how to fix it. Read through the Microsoft documentation on M365 admin scenarios (not everything, but the common ones). If you're serious about the role, join an admin community; real admins solve real problems there every day.
If you're career-changing into this role, don't assume you need to know everything before you apply. Hiring managers expect career-changers to have gaps. What they don't expect is for you to guess wildly or claim knowledge you don't have. Being honest, structured, and curious is far more valuable.
If you're not sure whether the M365 admin path is right for you, or you want to understand the broader UK IT landscape and salary picture, the free AI career roadmap tool at SmoothOps 365 takes just five minutes and shows you which roles match your background and earning potential. Many healthcare workers find they're closer to admin roles than they realise.
Be honest. Say something like "I haven't worked with that specifically, but here's how I'd approach learning it" and describe your troubleshooting process. Interviewers respect honesty and clear thinking far more than bluffed answers, and they can usually tell when someone's pretending.
You don't need years of experience, but you need some. Ideally, you've managed at least 50 to 100 users, dealt with a few real incidents, and touched licensing, groups, and permissions. If you're career-changing from healthcare, a structured training programme like the SmoothOps 365 Microsoft 365 Administrator Programme is a legitimate way to build that foundation.
The Microsoft 365 Certified Associate (Administrator Expert) certification helps and shows employers you're serious. However, many people pass interviews without it. Certification is useful as proof if you don't have direct work experience, but the interview is more about practical thinking.
Entry-level M365 admin roles in the UK start around £28k-£32k, with experience-level roles (2 to 5 years) at £35k-£45k, and senior/lead roles at £45k-£55k+. London and the South East tend to pay 10-15% more. See the full UK IT salary guide by role and region for detailed breakdowns.
SmoothOps 365 runs live instructor-led training every Saturday and Sunday. 3 months. 50 contact hours. Keep your job while you train.