Skip to content

Conditional Access for Microsoft Entra ID

Conditional Access implementation
without locking anyone out.

For IT leads with small teams who want to introduce Conditional Access in Entra ID without locking staff out. We implement it in your tenant at a fixed price, with break glass accounts, a report-only phase and a pilot group before any policy applies to everyone. The result: MFA at every sign-in, and the evidence your insurer and customers ask for.

Bastian Wenske

Founder and managing director

Book an introductory call
How it works 
For
Companies that use Microsoft 365, with in-house IT or an IT provider
Scope
Break glass accounts, MFA, policy baseline, pilot and activation
Duration
3 to 6 weeks, including at least 2 weeks in report-only mode
Result
Active policies, documented exceptions, evidence for insurers and customers
Price
Fixed price after scoping

Projects for organisations including

Sound familiar?

Why does Conditional Access so often stall?

MFA decided on, but not everywhere

Legacy protocols, guests and individual accounts still sign in with a password only.

The worry about locking everyone out

A badly scoped policy can hit administrators too. So the project keeps slipping.

Insurers or customers are asking

You need to show that every sign-in is protected, and you have nothing to show them.

Rollout

How do we roll out Conditional Access without lockouts?

Emergency exit first, then observe, then enforce. An example tenant, step by step.

Step 1 / 6

Which Conditional Access policies belong in the baseline?

The baseline follows established Conditional Access best practices, tailored to your licences and edge cases.

Block legacy authentication

Old protocols without MFA are blocked once scanners and interfaces have been moved over.

MFA for all users

At every sign-in; only the break glass accounts stay excluded.

Administrators

Phishing-resistant sign-in with passkeys, enforced through an authentication strength.

Guests and external accounts

MFA for guests too, instead of a blanket exclusion.

Devices

Where Intune is in use: access from compliant devices only.

Risk-based policies

A response to sign-in and user risk, where Entra ID P2 is licensed.

How does the project work?

  1. 30 minutes

    Introductory call

    Clarify the starting point, licences and edge cases.

  2. Fixed price

    Scoping and quote

    Scope based on your tenant and edge cases; the price is fixed before we start.

  3. 3 to 6 weeks

    Implementation

    Inventory, break glass accounts, report-only, pilot and activation.

  4. Documented

    Handover

    Policy documentation, exception list and evidence; ongoing review through managed security if you wish.

Where does your tenant stand on Conditional Access?

In 30 minutes we clarify licences, edge cases and scope, followed by a fixed-price quote.

Bastian Wenske

Founder and managing director

Book an introductory call

What changes?

Today

  • MFA only where it happens to be requested
  • Legacy protocols bypass MFA
  • No emergency exit if a policy misfires
  • Exceptions without a reason

After the rollout

  • MFA at every sign-in, guests included
  • Legacy authentication blocked
  • Two tested break glass accounts
  • Exceptions with reason, owner and expiry date

Frequently asked questions

What does it cost?

The rollout has a fixed price that depends on your tenant and its special cases. We set it after scoping, a short review of scope and special cases, before any work starts.

Will anyone be locked out?

The process is designed to prevent that. We first set up two emergency accounts, and every policy runs in report-only mode for at least two weeks and then for a pilot group before it applies to everyone. If someone is affected anyway, we roll back the policy through an emergency account and find the cause in the sign-in log.

How long does it take, and how much of our time does it need?

Three to six weeks, including at least two weeks in report-only mode. From your IT we need agreement on special cases such as scanners and interfaces, and a pilot group from IT and the business. Your staff keep working as normal; at the end, sign-in with a second factor is added for them.

Our IT provider looks after Microsoft 365. How do you work with them?

We agree special cases and timing with them and only make changes after your approval. At the end they receive the policy documentation and the list of exceptions and can look after the setup themselves. If you wish, we review the policies on an ongoing basis through managed security.

What do we receive at the end?

Active policies, a list of exceptions with reason, owner and expiry date, and a dated policy export with extracts from the sign-in logs. With these you can show your insurer and customers that every sign-in is protected.

Which licence do we need for Conditional Access?

Microsoft Entra ID P1. It is included in Microsoft 365 Business Premium, E3 and E5, among others. Risk-based policies require Entra ID P2, which is included in Microsoft 365 E5, for example.

We use security defaults. Is that enough for MFA?

Security defaults enforce MFA across the board, with no exceptions, no device conditions and no evidence per policy. The two cannot run side by side, so we switch over on the same day the replacement policies take effect.

Let's talk about your IT security

In the introductory call (30 minutes, no obligation) we clarify:

  • where your company stands today and what concerns you most
  • which next step makes sense for your organisation
  • what effort and price range to expect
Bastian Wenske

Bastian Wenske

Founder & Managing Director

Heidelberger Straße 15
12059 Berlin
Germany

Prefer to reach out directly? Send us an email at [email protected].