Engineering sprint · Identity

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.

2
weeks
Depending on scope
End-to-End
Enforcement
Including go-live
Microsoft Entra ID

Security and operations

This is how we introduce changes in your tenant, regardless of package.

  1. Settled before the start
    • Licence status
    • Dependencies, such as service accounts and older devices
    • Access for the implementation
    • Pilot group
  2. Checked before activation
    • Impact in report-only mode
    • Exclusions, including the emergency accounts
    • Rollback procedure per policy
  3. 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.

Essentials
Fixed price on request
Up to 25 users
Identity protection against phishing and account takeover for small teams. Puts in place the MFA and sign-in measures that cyber insurers often ask about.
Deliverables
  • 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)
Corporate
Fixed price on request
Up to 500 users
Enterprise Conditional Access with IaC deployment and a supported rollout.
Deliverables
  • 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
Enterprise
Fixed price on request
500+ users
Complex multi-domain architectures with PIM and risk-based access. Duration set once the scope is clear.
Deliverables
  • 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

Benefits for your business

The ROI for management.

Cyber insurer requirements
Cyber insurers increasingly ask about MFA, separate admin accounts and disabled legacy authentication when you take out or renew a policy. You receive clear documentation for this.
Protection against ransomware
Phishing-resistant MFA and device-bound policies make the initial intrusion and lateral movement within the network much harder.
Foundation for Swiss FADP (revDSG) & NIS2
The architecture covers key technical access controls that help you implement data security under the Swiss Federal Act on Data Protection (FADP) and, for companies with ties to the EU, under the NIS2 Directive.
Controlled rollout
Thanks to the audit-first principle and deploying the CA policies in report-only mode, the impact becomes visible before activation. This is how we minimize outages and support escalations for your end users.

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

Ready for a Zero Trust foundation?

By submitting, you agree to the privacy policy.

You will receive a reply by email within one business day. If your scope is already clear, we send the fixed-price quote right away.