Entra ID
Identity Hardening
Identity protection against phishing and account takeover. We implement the Microsoft tiering model, phase out legacy protocols in a controlled way and roll out Conditional Access policies as infrastructure as code.
Security and operations
This is how we introduce changes in your tenant, regardless of package.
-
Settled before the start
- Licence status
- Dependencies, such as service accounts and older devices
- Access for the implementation
- Pilot group
-
Checked before activation
- Impact in report-only mode
- Exclusions, including the emergency accounts
- Rollback procedure per policy
-
Included at handover
- Documentation of policies and exclusions
- Clarified operational ownership
- Runbooks for changes and emergencies
Scope & packages
Three packages by tenant size and complexity. You receive a binding fixed-price quote for your scope. User counts and packages are a guide. The binding scope also depends on the existing architecture, number of sites, hybrid scenarios, security requirements, integrations and technical special cases.
- Baseline protection against ransomware & phishing
- Mandatory MFA for all employees
- Blocking insecure sign-ins (legacy auth & sign-ins from abroad)
- Setup of secure emergency access accounts (break-glass)
- Everything in Essentials
- 15+ enterprise Conditional Access policies (via IaC)
- Separate admin accounts with minimal roles (least privilege)
- 7-day telemetry monitoring & supported go-live
- Everything in Corporate
- Multi-domain & complex Microsoft Entra Connect topologies
- Risk-based access (automatic response to risky sign-ins)
- Privileged Identity Management (PIM) with approval workflows
Technical details
Details for technical validation.
Policies (Enterprise Conditional Access)
A consistent architecture based on best practices. We roll out a ready-made set of 15+ policies based on a block-first approach, mandatory device compliance and network-based rules.
- Production CA policy set (deployed via IaC)
- Phishing-resistant MFA for admin accounts
- Device-bound access controls
Admin (Admin Tiering & PIM)
Emergency access and admin concepts based on enterprise standards. Permanent “standing privileges” are eliminated and, with Microsoft Entra ID P2, replaced with just-in-time (JIT) access for administration.
- Privileged Identity Management (PIM) setup (Entra ID P2)
- JIT admin access workflows
- Isolated break-glass emergency access accounts
Hardening (Entra ID Hardening)
Protection against modern attack vectors and identity theft. Systematic preparation for disabling legacy authentication methods and automated routing for compromised accounts.
- Legacy authentication hard-block preparation
- Sign-in risk & user risk policies
- Password spray & brute-force protection
Enforcement (Log Analysis & Go-Live)
No half-finished work. We first roll out the policies in report-only mode, monitor the telemetry for anomalies for 7 days and then, in agreement with you, carry out the final switch to enforcement.
- 7-day report-only telemetry monitoring
- Identification of blocking risks (legacy apps)
- Final go-live by Flowbotics (end-to-end)
Benefits for your business
The ROI for management.
Frequently asked questions
What prerequisites must be met before the sprint starts?
Conditional Access requires Microsoft Entra ID P1, for example through Microsoft 365 Business Premium; PIM and risk-based policies require Entra ID P2. As soon as the licenses and a time-limited admin account are in place, we get started.
Won’t strict CA policies lock us out?
We reduce this risk in several steps: every policy runs first in report-only mode and with a pilot group, we check it with What If analyses and define for each policy how it is rolled back. Two isolated emergency accounts (break-glass) are excluded from the blocking policies and are monitored.
How will our IT admins work after the sprint?
Securely and with an audit trail. Permanent “Global Administrators” are removed except for the emergency access accounts (least privilege). Your admins work with separate admin accounts and only the roles they need. With Microsoft Entra ID P2, they activate these rights through PIM when needed (just-in-time).
Will the hardening immediately bring legacy applications to a standstill?
Not without warning. Every policy is first rolled out in report-only mode via infrastructure as code (IaC). This lets us find applications that would be blocked before block mode is switched on in agreement with you.
Does this include securing the devices?
We secure devices in the Intune & Autopilot sprint. Until then, policies that require a compliant device stay in report-only mode. Older devices such as scanners that cannot sign in with modern authentication show up during testing, and we show you a suitable solution.
How much internal effort does this take?
Plan for 4–6 hours of your IT team’s time: a list of admin accounts and known exceptions (e.g., scanners, service accounts), tests with a few pilot users and approval before enforcement.
Who looks after the solution after the sprint?
Your IT team or IT partner, using our documentation. For ongoing development we can agree regular reviews, improvements or an engineering allowance; services and intervals are quoted individually.
Read more in the knowledge article: Conditional Access for SMBs: The baseline policies