Microsoft 365 account-compromise simulation

What if someone had your employee’s password?

See how access policies could respond to a stolen password, then take a clear report to your IT provider.

Explore this worked example before creating an account. It shows how CyberProva explains policy requirements, assumptions and gaps in plain English.

Explore the simulation example

Illustrative example · fictional policies

Scenario: a stolen password on a noncompliant device

This example uses fictional accounts and policies. It does not query Microsoft, inspect your business or save an assessment. The result is calculated from the example configuration, not your security settings.

  1. Assumed

    The attacker has a valid password

    An employee’s password is assumed to be known. The example models a browser sign-in to Exchange Online from a noncompliant device in the United States. No sign-in is attempted.

  2. Required by an enabled example policy

    A password alone does not satisfy this policy

    The enabled example policy applies and requires multifactor authentication. This identifies an additional requirement; it does not prove an attacker could not satisfy or bypass authentication in a real incident.

  3. Report-only · not enforced

    The device policy needs attention

    A second example policy would require a compliant device, but it is in report-only mode. That policy does not enforce its device requirement. Other protections could still apply.

Example outcome

Additional controls required

The enabled example policy requires MFA. The report-only device policy contributes no enforced requirement. This result does not predict whether a real sign-in or attack would succeed.

Explore the example policy details

These are fictional inputs interpreted by CyberProva’s simulation engine. No Microsoft tenant has been evaluated to produce this public example.

Example policy: require MFA

Policy state: Enabled

Applies to these assumptions: Yes

At least one listed control is required (OR).

  • Multifactor authentication

Example policy: require a compliant device

Policy state: Report-only

Applies to these assumptions: Yes

At least one listed control is required (OR).

  • Compliant device

Report-only: these controls are not enforced by this policy.

Coverage and limitations

A connected simulation models which Conditional Access policies apply to the account, application and conditions you select. It assumes a valid password. It does not perform a live attack, prove MFA completion, test service dependencies or establish effective access to mail or files. Missing information remains explicit and simulation results do not change assessment scores.

Personalised evaluation requires a verified Microsoft 365 connection, administrator consent and appropriate Microsoft licences. Entra P1/P2 coverage is needed for the selected account; risk-based scenarios require P2. Microsoft licences are separate from your CyberProva plan.

Assessment methodology · What CyberProva checks

From a public snapshot to a useful conversation with IT

  1. 1. Start with your public email and domain records

    Check SPF, DKIM, DMARC and MX observations without signing up. The snapshot gives you follow-up questions, not a business security score.

  2. 2. Create a workspace and optionally connect Microsoft 365

    Start with a free workspace. An administrator can review the permissions and approve a Microsoft 365 connection. On-demand simulations are included in Business and above.

  3. 3. Review your report and agree the next actions

    Select an account and hypothetical sign-in conditions. Share the policy explanations and coverage limits with your provider, request supporting evidence and record follow-up actions in your existing assessment.

A practical first step

Start with what your domain makes public

Get a free email and domain snapshot, then decide whether to explore your Microsoft 365 configuration in more detail.

Check your domain for free