Microsoft Entra ID Security Technology Syllabus

• Explain Entra tenant architecture and identity trust boundaries using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: map the components, identities, data paths and trust boundaries for Entra tenant architecture and identity trust boundaries
• Evidence: produce an annotated architecture diagram and explain the validation result

• Explain Users, groups, administrative units and role design using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: compare a baseline design with a risky or incomplete design for Users, groups, administrative units and role design
• Evidence: produce a design decision record and explain the validation result

• Explain Authentication methods and phishing-resistant MFA using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: trace one permitted and one denied access decision for Authentication methods and phishing-resistant MFA
• Evidence: produce an access-flow worksheet and explain the validation result

• Explain Conditional Access policy design and report-only rollout using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: plan a least-privilege configuration and a safe rollout sequence for Conditional Access policy design and report-only rollout
• Evidence: produce a change plan with rollback steps and explain the validation result

• Explain Identity Protection risk detections and remediation using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: review policy order, dependencies, exceptions and rollback conditions for Identity Protection risk detections and remediation
• Evidence: produce a policy review checklist and explain the validation result

• Explain Enterprise applications, consent and service principals using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: configure or assess the control with secure defaults for Enterprise applications, consent and service principals
• Evidence: produce a configuration evidence sheet and explain the validation result

• Explain Managed identities and workload identity federation using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: test expected and unexpected behavior against explicit pass criteria for Managed identities and workload identity federation
• Evidence: produce a pass/fail validation record and explain the validation result

• Explain Privileged Identity Management and just-in-time roles using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: locate the relevant telemetry and build an investigation timeline for Privileged Identity Management and just-in-time roles
• Evidence: produce an investigation timeline and explain the validation result

• Explain Access reviews, entitlement management and lifecycle workflows using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: triage a realistic finding and separate risk from expected activity for Access reviews, entitlement management and lifecycle workflows
• Evidence: produce a triage note with severity rationale and explain the validation result

• Explain Hybrid identity, synchronization and federation security using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: tune a noisy control without removing required visibility for Hybrid identity, synchronization and federation security
• Evidence: produce a tuning record with before-and-after evidence and explain the validation result

• Explain Sign-in logs, audit logs and incident investigation using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: troubleshoot a production-style failure using an evidence-first workflow for Sign-in logs, audit logs and incident investigation
• Evidence: produce a troubleshooting runbook entry and explain the validation result

• Explain Zero Trust identity capstone using current Microsoft terminology and connect it to the Microsoft Entra ID Security architecture
• Practice: combine design, validation, operations and handover in the capstone for Zero Trust identity capstone
• Evidence: produce a concise capstone handover and portfolio artifact and explain the validation result

This is a published technology learning blueprint. Contact Techclick to confirm current trainer availability, delivery format, schedule, lab access and pricing before making a decision.

No. Vendor certification programmes and exam blueprints change independently. This syllabus focuses on practical technology skills and official documentation.

Yes, subject to trainer and lab availability. Share your existing environment, target outcomes and preferred timeline for a scoped discussion.