Microsoft 365 Admin Account Security for Australian Businesses: A Practical Guide
Microsoft 365 admin account security is the single most valuable thing you can tighten this quarter, because one stolen administrator login can hand an attacker your email, files, devices and backups in one go. Most Australian small businesses have more admins than they realise, protected less well than they assume.
This guide is for the owner, office manager or IT lead who wants a clear, workable standard for admin accounts without buying a pile of extra licences. It covers what Microsoft now enforces, the two gaps we keep finding in client tenants, a practical admin model for Business Premium customers, and a four-week plan to put it in place without locking yourself out.
Why Microsoft 365 admin account security comes first
What Microsoft now enforces, and why it is already live
Gap one: the break-glass account that cannot sign in
Gap two: the advice that quietly needs a licence you may not own
The admin model that works without PIM
Stop using Global Administrator: a role map for common jobs
Conditional Access for administrators
Service accounts and automation that will break
Watching your admins: alerts and quarterly reviews
The four-week rollout plan
Six mistakes we see again and again
How this fits Essential Eight, cyber insurance and the Privacy Act
When to bring in a managed IT partner
Frequently Asked Questions
Why Microsoft 365 admin account security comes first
An ordinary staff account can read that person's mailbox and the files they can reach. An administrator account can do far more: reset other people's passwords, create mail forwarding rules, change who can sign in, switch off security features, and in the worst case delete the evidence. That is why attackers go looking for admin credentials first, and why a stolen admin session tends to turn a bad day into a business-threatening one.
Small businesses are exposed in a particular way. Over the years, admin rights get handed out for convenience. The office manager needed to reset passwords, so she became a Global Administrator. The previous IT provider kept an account. The founder made himself an admin when he set up the tenant, and that account is also the one he reads email with every morning. Nobody planned this. It just accumulated.
The attack paths are well known. Phishing kits that steal sessions, infostealer malware on a personal laptop, password spraying against accounts with weak sign-in rules, and social engineering of the help desk. We covered the session theft angle in our article on token theft and MFA bypass. The common thread is that the account being attacked matters more than the method. Protect the accounts with the most power first, and everything else gets easier.
What Microsoft now enforces, and why it is already live
Microsoft has made multifactor authentication mandatory for signing in to its admin portals, in two phases. The first phase began in the second half of 2024 and covers the Azure portal, the Microsoft Entra admin centre and the Microsoft Intune admin centre. Enforcement for the Microsoft 365 admin centre followed in February 2025. The second phase began on 1 October 2025 and extends the requirement to the Azure command line, Azure PowerShell, the Azure mobile app and the Azure management APIs, for create, update and delete actions.
Some tenants used the postponement option, which let a Global Administrator delay the second phase for complex environments. The latest date Microsoft offered was 1 July 2026. We are now in November 2026, so that window has closed. If your business delayed and then forgot, enforcement is either already affecting you or about to, and anything that signs in as a user without MFA is a candidate to fail.
Two details in Microsoft's documentation matter for a small business. First, there are no exceptions for emergency access accounts, so your break-glass accounts must satisfy MFA like everyone else. Second, user accounts that are being used as service accounts for scripts and automation must also sign in with MFA, and Microsoft recommends moving them to workload identities. Both points are quiet traps, and we will take them in turn.
It also helps to be clear about what mandatory MFA is not. It is not a complete admin security programme. It forces a second factor at sign-in, which is excellent, but it does not tell you how many admins you have, whether their accounts are shared with daily email, or whether the MFA method they use can be phished. Think of it as a floor, and build upward from there. Our guide to Conditional Access for Australian businesses shows how to raise that floor for everyone, not only admins.
Gap one: the break-glass account that cannot sign in
A break-glass account, also called an emergency access account, is a cloud-only administrator you keep in reserve for the day your normal admins are locked out. Microsoft recommends two of them, with permanent Global Administrator rights, not tied to any individual. The usual small business setup is a long random password, written down and stored in a safe or with the accountant, and the account excluded from Conditional Access so a bad policy cannot lock it out.
Here is the part many tenants miss. That password-only design was written for a world where excluding the account from Conditional Access was enough to keep it usable. Mandatory MFA is enforced separately, by Microsoft, and it does not honour your exclusions. Microsoft's guidance says break-glass accounts must sign in with MFA once enforcement begins, and recommends setting them up with a passkey (FIDO2) or certificate-based authentication, both of which satisfy the requirement.
What a safe small business setup looks like
- Two accounts, cloud-only. Use the onmicrosoft.com domain, not your company domain, and never a synced account.
- A hardware security key each. Register a FIDO2 key to each account and store the two keys in separate secure locations, such as an office safe and a director's home safe.
- A long password as a second record. Keep it sealed and separate from the keys, so no single lost item opens the account.
- Excluded from the policies that could lock everyone out, and covered instead by alerts. Every sign-in to these accounts should send an alert to at least two people.
- Tested every quarter. Sign in, confirm the key works, sign out, and note the date.
The test matters most. A break-glass account that has never been used is an assumption, not a control. Put the quarterly test in the calendar and record who did it. It takes ten minutes, and it is the cheapest insurance in this guide.
Gap two: the advice that quietly needs a licence you may not own
Read almost any Microsoft or security vendor article on admin accounts and you will see the same recommendation: use Privileged Identity Management, known as PIM, so admins hold roles as eligible, activate them for a limited time, and lose them automatically. It is good advice. It also has a catch that rarely gets mentioned to small businesses.
PIM requires Microsoft Entra ID P2 or Microsoft Entra ID Governance. Microsoft 365 Business Premium, the licence most Australian small and mid-sized businesses buy, includes Entra ID P1. That gives you Conditional Access and custom roles, but not PIM. So the standard advice, taken literally, tells a business to use a feature it has not paid for.
This is the differentiator for this guide. You do not need to buy P2 to get most of the safety that PIM provides. You need a design that gets the same outcome with the tools you already own: very few permanent powerful accounts, admin work done from separate accounts, and a habit of reviewing who holds what. If you later add P2 for a few key people, you can layer PIM on top of a model that is already clean. If you never do, you are still well ahead of the typical tenant.
| Capability | Licence needed | Included in Business Premium? |
|---|---|---|
| Conditional Access | Microsoft Entra ID P1 | Yes |
| Custom roles | Microsoft Entra ID P1 | Yes |
| Privileged Identity Management (just-in-time roles) | Microsoft Entra ID P2 or ID Governance | No |
| Access reviews and entitlement management | ID Governance or Entra Suite, some features with P2 | No |
| Mandatory MFA for admin portals | Applies to all tenants | Yes, enforced by Microsoft |
Check your own licences before you rely on any of this. Open the Microsoft 365 admin centre, look at what is assigned to each admin, and write down what you actually have. Features you assume you own but do not are the quietest source of gaps.
The admin model that works without PIM
Here is the model we use for Business Premium clients. It is deliberately short, because a standard people can remember is a standard people follow.
Rule 1: fewer than five Global Administrators
Microsoft recommends that fewer than five people hold the Global Administrator role. For a business under 100 staff, two or three named people plus the two break-glass accounts is usually plenty. Count them today. If you have seven, work out who really needs the role and move the rest to something narrower.
Rule 2: a separate admin account for admin work
Every person with admin rights gets two accounts: their normal one for email and browsing, and a separate cloud-only admin account used only for administration. The admin account has no mailbox, or a minimal one, and is never used to open links in email. This single change breaks the most common attack path, where a phishing email lands in an admin's inbox and the same session holds the keys to the tenant.
Rule 3: cloud-only admin accounts
Microsoft advises against giving Entra roles to accounts synced from on-premises Active Directory, because a compromise of the on-premises environment can then reach your cloud. If you still run a local server, keep admin accounts for the cloud separate and cloud-only.
Rule 4: the narrowest role that does the job
Entra has well over 65 built-in roles. The aim is to match each person's real tasks to the smallest role that covers them, and keep the number of roles with privileged permissions under ten in total. The next section gives a starting map.
Rule 5: a named owner and a review date
Without PIM's automatic expiry, a person has to do the expiring. Name the owner of the admin list, put a quarterly review in the calendar, and remove anyone who has not used their role. When you do have PIM-style tooling later, this habit keeps working.
Stop using Global Administrator: a role map for common jobs
Global Administrator is the role people give out because it always works. That is exactly the problem. The table below is a starting point for common small business jobs. Check it against your own tenant and Microsoft's current role descriptions before you apply it.
| Job | Consider this role instead | Why it is safer |
|---|---|---|
| Reset staff passwords | Helpdesk Administrator or Password Administrator | Cannot change security policy or other admins. |
| Add and remove users | User Administrator | No access to billing, mail flow or Conditional Access. |
| Manage mailboxes and mail flow | Exchange Administrator | Limited to email, not the whole tenant. |
| Manage SharePoint and OneDrive | SharePoint Administrator | Limited to files and sites. |
| Manage laptops and phones | Intune Administrator | Limited to device management. |
| Review security alerts | Security Reader | Read only, so it cannot change settings. |
| Pay and review invoices | Billing Administrator | No access to user data or security settings. |
| Edit Conditional Access policies | Conditional Access Administrator | Only for the person who owns access policy. |
When you move someone from Global Administrator to a narrower role, tell them first and keep a short rollback note. The usual failure is not security, it is a person who suddenly cannot do a task on a busy afternoon. A short list of "who to ask for the rare thing" solves most of it, and the rare thing is exactly the reason the role should be limited.
Conditional Access for administrators
Mandatory MFA sets a floor. Conditional Access lets you raise it for the accounts that matter most. Microsoft publishes a common policy that requires phishing-resistant multifactor authentication for administrators, meaning methods such as passkeys, Windows Hello for Business or certificate-based sign-in that cannot be handed to an attacker on a fake login page.
For most small businesses, we suggest a staged approach rather than a single switch. Start by requiring MFA for every admin role through a Conditional Access policy aimed at directory roles. Register passkeys or hardware keys for each admin account. Run the stronger phishing-resistant policy in report-only mode for two weeks, check the sign-in logs, and then enforce it. Keep your break-glass accounts handled as described earlier, with alerts rather than blind exclusions.
Two further rules are worth adding if you are comfortable. Block legacy authentication, which cannot do MFA at all, and consider requiring a compliant device for admin sign-ins, using the baseline in our Intune device compliance guide. An admin on an unmanaged personal laptop is the combination you most want to rule out. For background on why passkeys are becoming the default, see our note on Entra passkeys by default.
Service accounts and automation that will break
Over time, businesses accumulate user accounts that are really robots: a scanner that sends email, a script that creates users, a backup tool that signs in with a username and password. Microsoft's mandatory MFA applies to user accounts, so any of these that use Azure management tools as a user, without MFA, can start failing as enforcement reaches them. Microsoft's documentation also notes that clients using the older username and password sign-in flow fail once MFA is enabled.
Workload identities, meaning managed identities and service principals, are not affected by either enforcement phase. That is why Microsoft recommends migrating automation to them. For a small business, the practical steps are modest. List every account that signs in without a person, find out what each one does, and move it to a managed identity or an app registration with a certificate where the tool supports it. Where it cannot be moved, record the exception, restrict the account to the single task, and review it each quarter.
The most common culprit is a shared admin account used by a vendor or a previous provider. Ask each vendor what access they hold and why. Anything you cannot explain should be disabled for a week to see who complains, and then removed. That is a safe and surprisingly effective way to find forgotten access.
Watching your admins: alerts and quarterly reviews
Strong settings drift. People change roles, projects end, and a temporary permission becomes permanent because nobody removed it. A small amount of monitoring keeps the model honest.
- Alert on break-glass sign-ins. Any sign-in to an emergency account should notify at least two people immediately.
- Alert on role changes. A new Global Administrator, or any change to a privileged role, should be visible the same day.
- Review the admin list quarterly. Export the role assignments, check each name against a real person and a real need, and remove the rest.
- Review sign-in logs for admins monthly. Look for sign-ins from unusual countries, at odd hours, or from devices you do not recognise.
- Check licences. Confirm every admin holds the licence that supports the protections you think they have.
Keep a one-page record of who reviewed what and when. It is not busywork. When an insurer, a client or an auditor asks how you manage privileged access, that page is your answer, and it takes minutes to produce instead of days to reconstruct.
The four-week rollout plan
This plan suits a business of 10 to 150 people with one IT lead or an outsourced provider. It stages the changes so that nobody gets locked out, and so each step has a visible result.
Week 1: inventory
List every administrator and every role assignment. Note who each person is, what they actually do, and whether the account is also used for email. Check your licences. Identify any account that signs in without a person, and any synced account holding a cloud role. This week produces a list and no changes.
Week 2: fix the break-glass accounts
Create or repair two cloud-only emergency accounts, register a hardware key to each, store them in separate places, set up the sign-in alerts, and test both. Doing this first means you have a safe way back in before you change anything else.
Week 3: separate and narrow
Create separate cloud-only admin accounts for the people who need them, move daily work back to normal accounts, and replace Global Administrator with narrower roles using the role map. Keep the number of Global Administrators below five. Tell each person what is changing and why.
Week 4: raise the floor
Put Conditional Access in place for admin roles, starting in report-only mode, register passkeys, and review the logs. Enforce for the pilot group, then for all admins. Set the quarterly review date and name the owner. Finish by writing the one-page record of what you did.
Six mistakes we see again and again
- Treating mandatory MFA as the whole job. It is a floor. It does not reduce the number of admins or separate their daily work.
- A password-only break-glass account. It looks safe on paper and may fail the day you need it.
- Assuming PIM is included. It needs Entra ID P2 or ID Governance, so confirm the licence before designing around it.
- Admins who read email with their admin account. One phishing click then sits next to the keys to the tenant.
- User accounts used as robots. Scripts and scanners that sign in as users will meet MFA enforcement sooner or later.
- Forgetting leavers and old vendors. Admin access outlives the person or the contract unless someone removes it. A proper digital offboarding checklist prevents most of it.
How this fits Essential Eight, cyber insurance and the Privacy Act
The ASD Essential Eight includes a control to restrict administrative privileges, and the approach in this guide lines up with it: limit who holds privileged access, separate privileged accounts from everyday ones, and review access regularly. ASD has signalled changes to how the Essential Eight is presented, which we explain in our Essential Eight roadmap for SMBs, but the underlying principle of controlling privileged access is not going away. Our complete Essential Eight guide covers where admin accounts sit among the other controls.
Cyber insurers ask about privileged access directly. Proposal forms routinely want to know whether administrators use MFA, whether admin accounts are separate from daily accounts, and whether you can show how many admins you have. A documented model and a quarterly review record let you answer truthfully and quickly. It is also worth reading what your policy requires, as covered in our piece on cyber insurance in Australia.
The Privacy Act adds a legal reason. Organisations covered by the Act must take reasonable steps to protect personal information, and a compromised administrator account is one of the fastest ways to lose it. Our overview of Privacy Act obligations in Microsoft 365 explains the link. Tight admin control also underpins other projects, including a safe Copilot rollout and email authentication such as our DMARC guide. For a wider starting point, use our Microsoft 365 hardening checklist.
When to bring in a managed IT partner
Many businesses can complete the first two weeks of this plan themselves in a quiet month. The point to get help is when you have a mix of cloud and on-premises systems, vendors with unclear access, several offices, compliance obligations such as APRA or the Privacy Act, or nobody who can safely own the admin list over time.
A good partner will do four things: audit the admin accounts, roles and licences in your tenant today, build and test the break-glass and admin model in stages, enforce it with your team and explain the changes clearly to staff, and keep watching the alerts and the quarterly review. That last part is the one that tends to get dropped, and it is where the long-term value sits. If you are weighing providers, our guide to choosing the right MSP lists the questions to ask.
Written by Dan Briggs, All IT Services. All IT is a Sydney-based managed IT provider supporting hospitality, not-for-profit and financial services organisations across Australia.
Frequently Asked Questions
Do we need Entra ID P2 to secure our admin accounts?
How many Global Administrators should a small business have?
Does mandatory MFA apply to our break-glass accounts?
Should admins use their normal account for admin work?
What happens to scripts that sign in as a user account?
How often should we review administrator access?
Do you know who can change your Microsoft 365 security settings today?
Book a free admin account check and we will list every administrator in your tenant, test your break-glass accounts, show you where roles are too broad, and map out the safest way to tighten them.
Related Guide
Cybersecurity for Sydney SMBs
Explore our complete guide to protecting your business from cyber threats.
Read the Full Guide →