Ab900 Scenario Walkthrough

Guardrails

• Keep every walkthrough within AB-900 scope (M365 admin tasks, not Azure infrastructure).
• No contractions.
• No ambiguous "navigate around until you find it" steps. Every step must name the exact portal, blade, menu item, or button label.
• Always use current Microsoft product names and navigation paths. Apply all mappings from the agent terminology table silently.
• Use fictional company names (Contoso, Fabrikam, Tailwind Traders, Northwind Traders, Adventure Works) for scenario context in the scenario_context field.
• No cleanup section is required. Admin configurations can be noted as reversible with a brief note; no Azure resource deletion is needed.

AB-900 accuracy rules (non-negotiable)

These navigation paths must be exact every time they appear. Do not approximate or invent alternative paths.

• DSPM for AI portal path: purview.microsoft.com > Solutions > DSPM for AI (classic)
• Copilot PAYG billing: admin.microsoft.com > Copilot > Billing & usage
• Agent approval queue: admin.microsoft.com > Agents > All agents > Requests
• Researcher and Analyst block: admin.microsoft.com > Agents > All agents (separate block entry; not controlled by general agent toggle)
• SharePoint oversharing remediation: purview.microsoft.com > Solutions > DSPM for AI (classic) > Oversharing reports
• Sensitivity label creation: purview.microsoft.com > Solutions > Information protection > Labels
• DLP policy management: purview.microsoft.com > Solutions > Data loss prevention > Policies
• Conditional Access: entra.microsoft.com > Protection > Conditional Access > Policies
• PIM role activation: entra.microsoft.com > Identity governance > Privileged Identity Management
• Copilot license assignment: admin.microsoft.com > Users > Active users > [user] > Licenses and apps

Supported scenario types

Select one of the following scenario types per walkthrough:

• Copilot licensing: Assigning or removing Microsoft 365 Copilot licenses, reviewing license consumption, or understanding subscription vs. pay-as-you-go models.
• Agent approval: Reviewing, approving, or blocking an agent submission in the agent approval queue; separately blocking Researcher or Analyst.
• DSPM for AI review: Opening the DSPM for AI (classic) dashboard, reviewing sensitive data signals, interpreting oversharing reports, or reviewing AI interaction logs.
• SharePoint oversharing: Identifying overshared SharePoint sites or files through DSPM for AI (classic) and remediating access.
• Sensitivity labels: Creating or modifying a sensitivity label, configuring label settings (encryption, marking, scope), and publishing a label policy.
• DLP policy: Reviewing a DLP policy alert, creating a DLP policy scoped to Copilot interactions, or configuring a policy tip.
• PIM/Conditional Access: Activating a PIM role for a Copilot-related admin task, or reviewing a Conditional Access policy that affects Copilot-licensed users.

Timebox guidance

A walkthrough should contain 5-10 numbered steps across all tasks. If the walkthrough requires more than 10 steps, split the content into two separate walkthroughs, each focused on a narrower objective. Estimated time is 5-10 minutes (admin center navigation only; no Azure resource creation).

Workflow

1. Choose a single AB-900 objective and state it at the top.
2. Select a scenario type and draft a fictional company context.
3. Ground every navigation path and setting in Microsoft Learn via the Microsoft Learn MCP server.
4. Draft 5-10 numbered steps. Each step must include: what to navigate to, what to configure or observe, what the correct setting or action is, and why it matters for AB-900.
5. Confirm that all portal URLs and navigation paths match the AB-900 accuracy rules above.
6. Map each step to an exam domain (Domain 1, 2, or 3) in the exam_connection field.
7. Add Microsoft Learn references.

Output format