Lab notes / Customer workshop

IDENTITY & ACCESS / OCTOBER 2026

The access-policy lab mixer

Use report-only evaluation to understand a policy before it affects access.

30–45 minCustomer workshopTest environment

BEFORE THE CUSTOMER SESSION

Give the activity a clear purpose.

Agree on the customer question and the expected outcome. Prepare synthetic data, confirm the test environment, and name the evidence you will capture. Finish with a short discussion of what the result means for the customer’s next decision.

01

Prepare a dedicated test tenant

Use a tenant with appropriate Conditional Access licensing, an account permitted to configure policies, and a small test group. Record a recovery path and review emergency-access exclusions. Do not experiment against your only administrative account.

02

Write the access expectation

Choose one test application and a simple control such as requiring MFA for the test group. Document which users and flows are in scope, plus the outcome you expect for each.

03

Set the policy to report-only

Create the policy with the intended assignments and controls, then select Report-only. Report-only evaluates the policy without enforcing its access decision; inspect current platform guidance before choosing settings.

04

Generate representative sign-ins

Sign in as the test users using the devices and authentication methods in your test plan. Include a case expected to meet the control and a case expected to need an additional step. Note the account, application, and UTC time.

05

Read the sign-in evidence

Open the matching sign-in events and inspect the report-only policy results. Separate policy evaluation from the result of the overall sign-in. Record unexpected scope, exclusions, authentication context, and any user prompts you observe.

06

Decide the next change

Adjust a mismatched assignment or condition and repeat the test. Keep this guide’s policy in report-only. Any later enforcement should follow a documented pilot, recovery plan, and the organization’s change process.

THE CUSTOMER TAKEAWAY

Make the outcome easy to explain.

Close the workshop with a short record of the customer question, test scope, expected behavior, observed behavior, evidence, and next steps. Connect the finding to a control the customer can evaluate.