Before excluding users from Conditional Access, review the excluded list, plan emergency access, and confirm your MFA approach before making changes.
Key takeaways
- Review each excluded account and its reason.
- Distinguish emergency access from staff exceptions.
- Confirm your MFA approach before saving changes.
Every small accounting firm reaches the same moment. A staff member cannot sign in because their phone is in a drawer, or a partner's personal device will not accept the approval prompt, or a new hire is stuck on the second step of a sign-in. Someone in the room says, "Just exclude them from the MFA rule for a day." It sounds harmless. It is also how a temporary fix quietly turns into a permanent hole in your security.
This post is for partners and operations leads who set multifactor authentication rules for staff sign-ins in Microsoft 365. It covers three checks to run before you add anyone to the excluded list of a Conditional Access policy. None of them are hard. Together they help keep exclusions from piling up unnoticed over time.
The post goes through the checks in order, then ends with a short routine you can use whenever someone asks for an exception.
Why MFA exclusions deserve a pause
Start with what MFA is for. Microsoft's guidance on setting up MFA for users describes it this way: "Multifactor authentication (also known as MFA, two-factor authentication, or 2FA) requires a second verification method for user sign-ins and improves account security." ( Microsoft Learn)
That second method is the point. An exclusion should be a deliberate, written-down decision rather than a quick click on a busy afternoon.
There is often no dedicated security team. The same person who sets the policy may also be the one answering the help desk calls, approving the exceptions, and remembering why they were made. That is a good reason to slow down at the exclusion step, not speed through it.
The cost of getting it wrong is also uneven. Adding one exclusion takes seconds. Finding out months later that a departed employee's account has been outside the second step the whole time can take an afternoon of digging, and explaining it to clients or staff takes longer. Spending a few minutes on the checks below is cheap by comparison.
Where Conditional Access fits
Microsoft 365 gives you more than one way to require MFA. The same guidance notes that "If your Microsoft 365 organization includes Microsoft Entra ID P1 or later, you can use Conditional Access instead of security defaults for a higher security posture and more granular control." ( Microsoft Learn)
Two points from that sentence matter here. First, Conditional Access is the option that offers granular control, and granular control is exactly what makes exclusions possible. Conditional Access lets you name specific people and groups to leave out of a rule, which means it also gives you a list that can grow out of hand. Second, the option depends on your license. If you are not sure what your firm has, check that before you plan any policy changes.
Microsoft also states its general position plainly: "We strongly recommend using security defaults or Conditional Access for MFA in Microsoft 365." ( Microsoft Learn) The rest of this post assumes you have chosen one of those two routes and that you are working in Conditional Access. If you have not settled on a route yet, Check 3 covers that question.
Check 1: know exactly who is excluded, and why
Open the policy and read the excluded list before you add anyone new. The setup guidance describes the field this way: "Select excluded users and groups: The value 1 user is shown, and the user account that was used to create the policy is shown." ( Microsoft Learn) In other words, the screen shows a count of excluded users and groups, and the account that created the policy can appear there as well.
A count is not a list. Do not stop at the number. Open each entry and read the names. Then ask four questions about every name you find.
Who is this account, and do they still work here? An excluded account that belongs to someone who has left the firm is a risk, and it is worth checking first whenever you review the list. If the person is gone, note the exclusion for removal after Check 3 and handle the account through your normal offboarding steps.
Why is this account excluded? Write the reason next to the name in your own records. "Phone was lost, new phone set up next week" is an acceptable reason for a short period. "Not sure, it was already there" is not a reason. If nobody can say why an account is excluded, treat that as a finding to resolve, not a setting to keep.
Is the exclusion really about the person, or about a device or a process? In many cases the actual problem is a lost phone, a second method that was never registered, or an app that does not handle the prompt well. Those problems usually have a fix that does not involve taking a person out of the rule. Solve the underlying issue first, and only exclude the account if the fix is not available yet.
Who owns this policy now? Check that name. If that person has moved into a different role, left, or is no longer the one handling admin tasks, decide now who will own the policy and its exclusions. A policy with no clear owner collects exceptions that nobody ever reviews.
Once you have answered those questions, write the list down somewhere outside the admin portal. A simple table with the account name, the reason, the person who approved it, and the date you plan to review it is enough. The point is that the next person who looks at the policy can see what each exclusion is for, without having to guess.
For related staff access checks, see firm authentication mistakes.
Check 2: never clear the list by accident, and plan for emergency access
The setup steps also show what happens when the excluded list is emptied. The guidance says: "The value changes to 0 users and groups selected and the warning text Select at least one user or group appears." ( Microsoft Learn) Treat that warning as a prompt to stop and check what you are about to change. It is not a box to tick so the screen will let you move on. If you see it after removing entries, go back and confirm each removal was intended before you save.
The same guidance covers emergency access accounts, which are added through the same excluded users field. The step reads: "To add emergency access accounts to the excluded users list, select 0 users and groups selected." ( Microsoft Learn) That wording is the label on the screen, so expect the count to change as you select accounts. Do not let the odd phrasing make you skip the reason behind it.
Protect emergency access accounts deliberately. A few practical points for a small firm:
- Keep emergency access accounts separate from the accounts your partners and staff use every day. Nobody should use them for routine work.
- Store their credentials securely, with access limited to the people who genuinely need them, and record where they are kept.
- Test them on a planned schedule so you know they still work before you need them in a crisis.
- Make sure the sign-in activity for these accounts is watched, because any use of them should be unusual and worth a question.
Notice what this check is really about. Emergency access accounts are a planned exception with a defined purpose. A convenient exclusion added to get one employee through a bad morning is a different thing. Keep the two apart in your records so nobody confuses them later.
Check 3: confirm your MFA approach before you change anything
The third check happens one level up, before you touch any individual exclusion. Ask which MFA approach your tenant is actually using: security defaults or Conditional Access. ( Microsoft Learn)
Before you commit to Conditional Access, confirm your licenses. If your organization includes Microsoft Entra ID P1 or later, the guidance points to Conditional Access as the option with more control. If it does not, the decision is about what you can actually use, and the answer may be to fix the device or method issue for that person rather than create a new exception.
If you are already on Conditional Access, look at the whole policy set, not just the one rule someone is asking about. Read the policies that apply to the same users and groups, and note which one an exclusion is meant to affect.
If you are unsure which approach is in use, stop and find out before you make any change. Changing a policy you do not fully understand is how a simple exception becomes an outage. Ask your Microsoft 365 administrator or whoever set up the tenant, and write down the answer, so the next person does not have to ask again.
By then you know what the exclusions are for, and you can judge whether the approach you are using still fits the firm.
A simple routine for exception requests
Most exclusion requests arrive in the middle of a busy week, from someone who needs to get working again. That is the moment to follow a fixed routine rather than improvise. Here is one that works for a small firm.
1. Ask for the reason in writing. A short message is enough. What is the problem, who is affected, and how long do they expect it to last? A request that cannot answer those three questions is not ready.
2. Try the fix that does not involve an exclusion first. Can the person sign in from a registered device? Can they re-register their second method? Can the problem be solved with a different sign-in method that you have already approved? If one of these works, there is no need for an exclusion at all.
3. If an exclusion is still needed, set an end point. Decide when it will be reviewed and removed. Put that date in your calendar or task list. An exclusion without an end point tends to stay forever, and the list grows without anyone deciding that it should.
4. Record the exception. Add the account, the reason, the approver, and the review date to your list. This is the same record described under Check 1. If you keep one list and update it every time, the review becomes a short job rather than an investigation.
5. Make the change in the policy, and then check it. Before you start, note the current excluded list so you can put it back if something goes wrong. After you save, read the excluded list again. Confirm the right account is there and that nothing else changed. If the warning about zero users and groups selected appears, or the count is not what you expected, stop and fix it before you move on.
6. Remove the exclusion on time. When the review date comes, check whether the exception is still needed. If the person is back to normal, remove the account and update the record. If it is still needed, write down the new reason and the new review date. Do not let it roll forward silently.
Put this routine in a shared document that everyone who can approve exceptions can see. A written process protects the people involved as much as the firm. When a partner asks why an account was excluded six months ago, the answer should be in a file, not in someone's memory.
Illustrative example: a lost phone
A staff member loses their phone and cannot approve the sign-in. First, have them try another approved sign-in method. If an exclusion is still needed, record the reason, the approver, and the review date. At review, check whether a replacement phone has solved the problem before removing the exclusion.
Wrapping up
An exclusion from Conditional Access is sometimes necessary. A lost phone, a device that will not take the prompt, or a legitimate emergency access account can all justify one. The trouble starts when exclusions are added quickly, never reviewed, and never explained. That is how a firm that set up MFA carefully ends up with a list of exceptions nobody understands.
For a broader review, see the tax firm security checklist.
If your firm is not sure where it stands, start with the Microsoft guidance on setting up MFA for users, which covers the choice between security defaults and Conditional Access. ( Microsoft Learn) Today, sit down with whoever manages your Microsoft 365 tenant and go through the excluded list together.
Questions about exclusions
Does an exclusion remove every MFA requirement?
No. An exclusion applies to that policy's requirement, so check other applicable settings before judging the account's sign-in requirements.
What should an exception record contain?
Record the account, reason, approver, and review date. Keep that record where the next person reviewing the policy can find it.