Study guide
15.2 Diagnostics, KQL & Workbooks
Exam SC-300: Microsoft Identity and Access Administrator Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts & Logistics 1.2 Audience Profile, Zero Trust & Role Scope 1.3 Skills Measured & Study Map
2 Entra Tenant Administration
2.1 Tenant Properties, Domains & Company Branding 2.2 Built-in & Custom Roles, Effective Permissions 2.3 Administrative Units
3 Users, Groups, Licenses & Devices
3.1 Create, Configure & Manage Users 3.2 Groups & Custom Security Attributes 3.3 Licenses, Bulk Operations & Device Join
4 External Identities & Cross-Tenant Access
4.1 External Collaboration & Guest Lifecycle 4.2 Cross-Tenant Access Settings 4.3 Cross-Tenant Sync & External Identity Providers
5 Hybrid Identity
5.1 Entra Connect Sync vs Cloud Sync 5.2 PHS, PTA & Seamless SSO 5.3 AD FS Migration & Connect Health
6 Authentication Methods & MFA
6.1 Authentication Methods Portfolio 6.2 MFA, SSPR & Password Protection 6.3 Passwordless, Session Control & Entra Kerberos
7 Conditional Access
7.1 Planning, Assignments & Controls 7.2 Session Management, Device Restrictions & CAE 7.3 Auth Context, Protected Actions, Templates & Troubleshooting
8 Identity Protection & Global Secure Access
8.1 User Risk & Sign-in Risk 8.2 MFA Registration Campaigns & Risky Workloads 8.3 Global Secure Access
9 Workload & Managed Identities
9.1 Selecting Identities for Apps & Azure Workloads 9.2 Create, Assign & Use Managed Identities 9.3 Service Principals Fundamentals
10 Enterprise Apps & App Registrations
10.1 Enterprise Applications Integration 10.2 App Registrations, API Permissions & App Roles 10.3 Application Proxy & Consent
11 Microsoft Defender for Cloud Apps
11.1 Cloud Discovery & Connected Apps 11.2 CA App Control & Session Policies 11.3 OAuth App Policies & Catalog Management
12 Entitlement Management
12.1 Catalogs & Access Packages 12.2 Access Requests & Terms of Use 12.3 Connected Organizations & External User Lifecycle
13 Access Reviews
13.1 Plan & Create Access Reviews 13.2 Monitor & Respond to Access Reviews
14 Privileged Identity Management
14.1 PIM for Entra Roles & Azure Resources 14.2 PIM for Groups, Approval & Audit 14.3 Break-Glass (Emergency Access) Accounts
15 Monitoring, Logs & Secure Score
15.1 Sign-in, Audit & Provisioning Logs 15.2 Diagnostics, KQL & Workbooks 15.3 Identity Secure Score
15.2 Diagnostics, KQL & Workbooks
Key Takeaways Explain This Topic AI
Diagnostic settings stream Microsoft Entra logs to destinations such as Log Analytics workspaces, storage accounts, and Event Hubs for retention, SIEM, and custom analytics beyond portal defaults.
Log Analytics plus Kusto Query Language (KQL) lets identity admins query SignInLogs, AuditLogs, and related tables for trends, failures, and Conditional Access impact without relying only on manual portal filters.
You need conceptual KQL for SC-300—simple filters, summarize/count patterns, and time windows—not expert data-science fluency.
Microsoft Entra workbooks and reporting experiences provide prebuilt and customizable dashboards for sign-ins, Conditional Access, provisioning, and security operations.
Design monitoring as a pipeline: choose log categories → diagnostic destination → queries/alerts/workbooks → operational response.
Last updated: July 2026
From portal triage to a monitoring pipeline
Section 15.1 taught interactive investigation in the Entra admin center. Production tenants need more: longer retention , SIEM correlation , alerts , and repeatable dashboards . Microsoft Entra diagnostic settings export log categories to Azure destinations. In Log Analytics , you query with KQL . Workbooks and built-in reports turn those streams into operational visibility.
This is classic SC-300 Domain 4 monitoring—not AZ-104 deep infrastructure design, but you must know what to send where and how to ask simple questions of the data. Practice items: /practice/azure-sc-300 . Complementary security operations mindset: /practice/azure-az-500 .
Diagnostic settings: the export control plane
A diagnostic setting on Microsoft Entra ID specifies:
Which log categories to export (for example AuditLogs, SignInLogs, NonInteractiveUserSignInLogs, ServicePrincipalSignInLogs, ProvisioningLogs—exact category names evolve with the product).
Which destination(s) receive the stream.
Optionally, metrics or additional categories your tenant supports.
You can maintain multiple diagnostic settings to fan out the same categories to different sinks (workspace for ops, Event Hub for SIEM, storage for cold archive).
Destination comparison
Destination Best for SC-300 notes
Log Analytics workspace Interactive KQL, workbooks, Azure Monitor alerts, Microsoft Sentinel connector patterns Primary “query and visualize” path for identity admins
Storage account Cheap long-term archive , legal hold-style retention, occasional rehydrate Not ideal for day-to-day interactive investigation
Event Hubs Streaming to external SIEM /custom pipelines (Splunk, QRadar, custom consumers) Near-real-time egress; partner tools subscribe to the hub
- Design question Typical choice
- SOC needs 1-year searchable history + alerts Log Analytics (and/or Sentinel) with retention policy
- Compliance wants immutable multi-year dump Storage account archive tier strategy
- Existing enterprise SIEM is non-Microsoft Event Hubs → SIEM connector
- Helpdesk only needs 14-day clicks in portal Portal may suffice short-term, but still export for incidents
Exam trap: “Store logs forever in the Entra portal only” is not a retention architecture. Correct answers emphasize diagnostic settings to Log Analytics, storage, or Event Hubs.
What to export for identity operations
Minimum useful set for SC-300-style monitoring:
AuditLogs — who changed directory/config.
SignInLogs — interactive user authentications.
NonInteractiveUserSignInLogs — token/refresh style user activity.
ServicePrincipalSignInLogs (and related managed identity categories where listed) — workload auth.
ProvisioningLogs — HR/app provisioning.
Risk / ID Protection related categories when licensed and available for export.
Exporting only AuditLogs leaves you blind to authentication failures; exporting only SignInLogs leaves you blind to privilege grants.
Permissions and ownership
Configuring diagnostic settings and reading workspaces typically requires privileged Entra roles (for example Security Administrator / Global Administrator patterns for tenant diagnostics) plus Azure RBAC on the destination resource (Log Analytics Contributor, etc.). SC-300 cares that identity monitoring is a joint Entra + Azure resource operation: the workspace lives in a subscription; the log source is the tenant.
Log Analytics tables (conceptual)
Once diagnostics land in a workspace, data appears in tables you query. Conceptual mapping:
- Entra stream Common table / family (names can evolve) Questions
- Interactive sign-ins SignInLogs Failures, apps, locations, CA outcomes
- Audit AuditLogs Role/group/policy changes
- Provisioning AADProvisioningLogs or similarly named Sync errors by system
- Non-interactive / SP Separate sign-in tables when exported Workload and background auth
You do not need to memorize every column for the exam. You need to know that after diagnostic settings , investigations can use KQL against these tables in addition to the portal.
KQL for identity admins (teach concepts, not expert mode)
Kusto Query Language (KQL) is the query language for Log Analytics. SC-300 expects literacy , not certification-level KQL craft.
Building blocks
- Building block Purpose Tiny pattern
- Table Data source SignInLogs
- Time filter Limit window | where TimeGenerated > ago(24h)
- Where Filter rows | where ResultType != 0 (failed sign-ins often non-zero result codes)
- Project Select columns | project TimeGenerated, UserPrincipalName, AppDisplayName
- Summarize Aggregate | summarize Failures=count() by UserPrincipalName
- Order / take Rank and sample | order by Failures desc | take 10
- Example 1 — failed interactive sign-ins last day (concept) SignInLogs
- | where TimeGenerated > ago(1d)
- | where ResultType != "0"
- | summarize FailureCount = count() by UserPrincipalName, ResultDescription
- | order by FailureCount desc
- | take 20
Teaching point: start from the sign-in table, constrain time, filter failures, aggregate by user and reason, sort. Exact property names can vary slightly by schema version; exam items test the approach .
- Example 2 — Conditional Access failure focus (concept) SignInLogs
- | where TimeGenerated > ago(7d)
- | where ConditionalAccessStatus == "failure"
- | summarize Attempts = count() by UserPrincipalName, AppDisplayName
- | order by Attempts desc
Teaching point: CA impact analysis at scale uses exported sign-ins, not only opening one user in the portal. Report-only pilots can similarly be summarized when the schema exposes report-only results.
- Example 3 — audit who changed groups (concept) AuditLogs
- | where TimeGenerated > ago(48h)
- | where Category == "GroupManagement"
| project TimeGenerated, OperationName, Identity = tostring(InitiatedBy.user.userPrincipalName), Target = tostring(TargetResources[0].displayName)
| order by TimeGenerated desc
Teaching point: audit queries answer accountability questions across the whole tenant window, useful for SOC reviews after a privilege or membership incident.
- Example 4 — provisioning failures by app (concept) AADProvisioningLogs
- | where TimeGenerated > ago(3d)
- | where ResultType != "Success"
- | summarize Events = count() by JobId = tostring(JobId), ResultDescription
- | order by Events desc
Teaching point: same pattern—filter non-success, summarize, prioritize the noisiest job or error.
KQL hygiene for SC-300 answers
Always time-bound queries; unbounded scans are slow and expensive.
Filter early (user, app, failure) before heavy joins.
Use summarize for trends; use project for incident timelines.
Alerts in Azure Monitor are often “run this KQL on a schedule; fire if threshold met” (for example spike in legacy auth failures).
You will not be asked to hand-write perfect production queries under every schema nuance. You will be expected to choose Log Analytics + KQL when the stem wants historical analysis, custom reporting, or automated detection beyond the default portal UX.
Workbooks and reporting
Azure workbooks (and Entra monitoring workbook experiences) are interactive dashboards built on Log Analytics queries and visualizations. Microsoft ships Entra-oriented workbook templates for topics such as:
- Workbook / report theme Operational value
- Sign-ins Success/failure trends, top apps, legacy auth visibility
- Conditional Access Impact, failures, report-only outcomes at fleet scale
- Sensitive operations / audit High-risk directory changes
- Provisioning Health of HR and app sync jobs
- Identity protection / risk (when data present) Risky sign-in and user trends
- Secure Score related views Track improvement over time (pairs with 15.3)
- Using workbooks well
Ensure diagnostic settings populate the workspace the workbook expects.
Open Entra workbooks / Azure Monitor workbooks gallery for identity templates.
Set time range and subscriptions/workspace parameters.
Drill from chart → grid → single sign-in/audit event.
Clone and customize for your org (add filters for privileged users, break-glass UPNs, Tier-0 apps).
Pin key views for weekly identity ops review .
Built-in reports vs workbooks vs raw KQL
- Tool Strength Limitation
- Entra portal reports Fast, guided, least setup Retention and customization limits
- Workbooks Visual, shareable, template-accelerated Needs Log Analytics data feeding them
- Raw KQL Maximum flexibility, alert rules Requires query skill and schema familiarity
Microsoft Sentinel (adjacent) SOC correlation, incidents, playbooks Broader than pure identity admin scope; know it can consume Entra logs
SC-300 identity admin answers usually stop at diagnostic settings + Log Analytics/workbooks ; full Sentinel engineering is more SC-200/SOC territory, but recognizing Sentinel as a consumer of Event Hub/workspace data is fair game.
- Monitoring architecture patterns
- Pattern A — Identity ops core
Entra diagnostics → Log Analytics → workbooks + Azure Monitor alerts (failed MFA spike, break-glass sign-in, privileged role assignment).
Pattern B — Enterprise SIEM
Entra diagnostics → Event Hubs → corporate SIEM; optional parallel → Log Analytics for identity team self-service.
Pattern C — Compliance archive
Entra diagnostics → Storage for long retention + Log Analytics for 90-day hot query; lifecycle policies on storage.
Alert ideas that map to earlier chapters
- Signal Why alert
- Sign-in success for break-glass accounts Emergency account use is rare and critical
- Audit: Add member to Global Administrator Privileged access change
- Spike in legacy authentication attempts Attack or misconfigured client
- Provisioning failure rate on HR job Joiner/mover pipeline broken
- Service principal sign-in failures after secret expiry Workload outage / rotation gap
- Operational checklist
Inventory which categories you currently export (many tenants export nothing).
Create or select a dedicated Log Analytics workspace with appropriate retention.
Configure Entra diagnostic settings to workspace (+ Event Hub/storage as needed).
Validate data latency with a known test sign-in and a simple KQL take query.
Deploy starter workbooks for sign-ins and CA.
Define three to five alerts tied to runbooks (who gets paged, what they check).
Review workbook trends in the same ops meeting as Identity Secure Score (next section).
Document workspace access (least privilege; not every helpdesk agent needs full query rights on all tables).
Common exam traps
Confusing Azure activity logs (ARM resource operations) with Entra sign-in/audit logs .
Choosing storage when the requirement is interactive KQL investigation (Log Analytics).
Choosing only portal filters when the requirement is 12-month retention and SIEM .
Believing workbooks work with full historical depth without diagnostic export.
Writing that KQL is required for every single-user helpdesk ticket (portal is fine for one-off).
Summary of section 15.2
Diagnostic settings stream Entra audit, sign-in, provisioning, and related categories to Log Analytics , storage accounts , and Event Hubs . KQL enables simple, time-bounded queries and summaries for failures, Conditional Access impact, and directory changes. Workbooks and reports turn those queries into operational dashboards. Together they scale the investigation skills from section 15.1 into continuous monitoring. Section 15.3 uses related visibility to drive Identity Secure Score improvements. Continue drills at /practice/azure-sc-300 .