· cyber security · 5 min read

Conditional Access: The Microsoft 365 Settings Small IT Teams Skip

Conditional Access is already included in many Microsoft 365 plans and sits unused. These five policies, rolled out in report-only mode first, are a good starting point for co-managed IT teams.

Conditional Access is already included in many Microsoft 365 plans and sits unused. These five policies, rolled out in report-only mode first, are a good starting point for co-managed IT teams.

Many organizations pay for Microsoft 365 Business Premium and never open the Conditional Access page. It is understandable. The page looks like a rules engine, and one wrong rule can lock a whole office out at 7:30 on a Monday morning.

Picture a 120-person engineering firm. Consultants sign in from client sites and airports, a few contractors work from another country, and the two-person IT team also handles the phones and the printers. Nobody has had time to touch the sign-in rules.

Conditional Access is part of Microsoft Entra ID (the sign-in service behind Microsoft 365). It requires Entra ID P1, which Business Premium includes. Each policy says: for this user, on this device, from this place, allow, require something extra, or block.

Here are five policies worth having, and a safe way to turn them on.

Block legacy authentication

Legacy authentication means older sign-in methods such as basic IMAP, POP, and SMTP. They cannot do MFA (multifactor authentication), so an attacker with a stolen password can use them to skip it entirely.

Blocking them is usually the first policy we recommend. Before you do, look for things that still depend on them. Scanners and copiers that email documents are the classic example. Some old line-of-business software is another.

Require MFA

Require MFA for every user, and for administrators every time. Many organizations have MFA turned on per user, which leaves gaps whenever a new account is created. A Conditional Access policy covers new accounts automatically.

If you are still on text message codes, move administrators to a phishing-resistant method such as a security key first.

Require compliant devices for email and business applications

A compliant device is one enrolled in Microsoft Intune that meets your rules: disk encryption on, screen lock set, operating system current. This policy says a valid password and MFA are not enough on their own. The laptop also has to be one you manage.

That matters when client files, source code, or customer records sit in the mailbox. A contractor’s personal PC with no encryption and three browser toolbars should not be syncing it.

One caveat. This policy can only protect a line-of-business application (your ERP, CRM, or similar) that signs in through Entra ID. If yours uses its own login, ask the vendor whether single sign-on is available. Until then, the policy covers the Microsoft 365 side, including the mailbox where much sensitive data ends up.

Block countries you do not operate in

If every employee works in the United States and Canada, a sign-in from another continent has no business reason. Create a named location list and block sign-ins from outside it. If you have contractors or a nearshore team elsewhere, add that country to the list and apply the rule so it covers only the people who work there.

Treat this as a filter. An attacker can route traffic through a VPN in the United States, so it will not stop everyone. It does remove a large amount of noise from the sign-in logs, which makes the odd entries easier to spot. Build in a process for travel, such as a temporary exception for a consultant at a conference.

Exclude and watch the break-glass accounts

A break-glass account is an emergency administrator account used when normal access fails, for example if a policy mistake locks everyone out. Create two. Make them cloud-only, give them long random passwords stored offline, and exclude them from your Conditional Access policies.

Then alert on every sign-in to them. They should almost never be used, so any use is worth a look.

Start in report-only mode

Each policy can run in report-only mode, which logs what it would have blocked without blocking anything. Run all five for a week or two. Then read the results and fix the surprises: the scanner nobody remembered, the executive who checks mail from a vacation home.

Only then switch the policy to on. Turn them on one at a time, with a few days between each, so a problem has an obvious cause.

Microsoft Secure Score works well alongside this. It is built into Microsoft 365 and gives a prioritized list of settings with an overall score. Use it as a checklist, not a target. Some recommendations fit a 20-person firm and some do not, and a lower score with a reason written down beats a higher one nobody can explain. Cyber insurance questionnaires often ask about several of these same controls, so the written record has a second use.

Change control in co-managed IT

Conditional Access is where co-managed IT needs clear ground rules, because a policy change touches everyone at once.

A workable split:

  • The MSP (managed service provider) drafts the policy, sets it to report-only, and prepares the results
  • Your internal IT team reviews the results, because they know the scanner, the traveling consultant, and the odd vendor login
  • The IT manager or an operations lead approves the switch to on, in writing, for a time outside business hours
  • Everyone knows the rollback is one toggle and who has the authority to flip it
  • The change goes into the shared documentation with the date and the reason

Also decide who receives the alert if staff cannot sign in. Name a person, not a team.

Kayak Cyber builds and tests these policies for co-managed clients and keeps the documentation current. Once the policies are live, we review what they catch: blocked sign-ins from countries you don’t work in, old email apps that keep retrying, and any account that suddenly lands in an admin role. Your IT manager keeps the final say on what goes live. You can read more about our managed IT services and cybersecurity services.

Call us at 405-253-5101 or schedule a discovery call to get on the calendar.

  • co-managed-it
  • microsoft-365
  • conditional-access
Share:
Back to Blog