MFA decided on, but not everywhere
Legacy protocols, guests and individual accounts still sign in with a password only.
Conditional Access for Microsoft Entra ID
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.
Projects for organisations including
Sound familiar?
Legacy protocols, guests and individual accounts still sign in with a password only.
A badly scoped policy can hit administrators too. So the project keeps slipping.
You need to show that every sign-in is protected, and you have nothing to show them.
Rollout
Emergency exit first, then observe, then enforce. An example tenant, step by step.
The baseline follows established Conditional Access best practices, tailored to your licences and edge cases.
Old protocols without MFA are blocked once scanners and interfaces have been moved over.
At every sign-in; only the break glass accounts stay excluded.
Phishing-resistant sign-in with passkeys, enforced through an authentication strength.
MFA for guests too, instead of a blanket exclusion.
Where Intune is in use: access from compliant devices only.
A response to sign-in and user risk, where Entra ID P2 is licensed.
30 minutes
Clarify the starting point, licences and edge cases.
Fixed price
Scope based on your tenant and edge cases; the price is fixed before we start.
3 to 6 weeks
Inventory, break glass accounts, report-only, pilot and activation.
Documented
Policy documentation, exception list and evidence; ongoing review through managed security if you wish.
In 30 minutes we clarify licences, edge cases and scope, followed by a fixed-price quote.
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.
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.
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.
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.
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.
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.
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.
In the introductory call (30 minutes, no obligation) we clarify:
Bastian Wenske
Founder & Managing Director
Prefer to reach out directly? Send us an email at [email protected].