Skip to main content
Certifications Microsoft SC-300 Home projects Back to certification

Home labs & practical projects

Test a conditional access change before broad rollout

A project to do with your own tools, with guidance on what to create and capture.

Vendor environment Suggested time: 2–3 hoursYour own authorised environment
01

What you could create

An identity team wants stronger sign-in controls for a sensitive application without locking out legitimate support or recovery access.

Example evidence format
Project evidence map (example)
Conditional access change planScope and inputs
Pilot test matrix and rollback recordDecisions and reasoning
Evidence record (example)
EvidenceWhat to capture
Conditional access change planShow the inputs, scope and decisions behind this record. Expected and observed outcomes are recorded for every test identity.
Pilot test matrix and rollback recordInclude the evidence supporting your conclusion. Emergency access is considered and verified before wider enforcement.
02

What you'll need

Vendor environment

Use a training Entra tenant with suitable licensing and test users. Define a pilot group, a recovery procedure and expected sign-in outcomes.

Project record

Keep the working files for conditional access change plan and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Access may require a licence, trial or training subscription. Confirm availability and permitted use before committing; no free tenant is assumed.

Use an authorised training tenant with test identities and synthetic data. If access is unavailable, document the plan and label it untested.

03

Suggested milestones

  1. 1

    Plan and investigate

    Design a narrowly scoped policy and an initial observation stage where supported.

  2. 2

    Develop your approach

    Test the intended user, an excluded test case and a non-compliant sign-in.

  3. 3

    Verify and explain

    Review results before enforcement and document rollback ownership.

04

Useful resources

Use these resources to deepen your understanding and check key details.

Turn the project into evidence

Keep your artefacts and reasoning together so you can explain what you did.

A useful starting point

Use a training Entra tenant with suitable licensing and test users. Define a pilot group, a recovery procedure and expected sign-in outcomes.

What a good result looks like
  • Expected and observed outcomes are recorded for every test identity.
  • Emergency access is considered and verified before wider enforcement.

Finish the project

Remove test identities, policies and data, restore the initial configuration, and check trial expiry or renewal settings.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.