1. App Registration – registration and configuration of the application
App Registration in Azure Entra ID defines how an application identifies itself, issues tokens, and exposes permissions to other components. This part addresses tenant models, manifest settings, redirect URIs, certificate and secret management, token options, API exposure, and least-privilege permission design.
- creating App Registration in Azure Entra ID:
- application and tenant structure,
- single-tenant vs multi-tenant,
- application manifest configuration:
- editing properties and usage scenarios,
- Redirect URIs:
- configuration for SPA, web apps, mobile,
- certificates vs secrets:
- differences and application,
- rotation of secrets and certificates,
- security best practices,
- token configuration:
- token versions (v1 vs v2),
- optional claims,
- token lifetime,
- Expose an API:
- defining scope’s,
- api:// identifiers,
- API Permissions:
- delegated vs application permissions,
- the least privilege principle,
- usage scenarios.
2. Enterprise Application – access management
Access control for Enterprise Applications combines application configuration with user, group, and role assignment rules. Participants work through User assignment required, App Roles defined in the manifest, API access for multiple consuming apps, and SCIM-based provisioning to external systems.
- creation and configuration of Enterprise Applications,
- assigning users and groups:
- User assignment required,
- App Roles:
- defining roles in the manifest,
- assigning roles to users and groups,
- API access control:
- access per role and group,
- a scenario of multiple applications consuming the API,
- User provisioning (SCIM):
- automatic synchronization of users,
- integration with external systems.
3. Authentication flows
Choosing the right authentication flow depends on application type, trust boundaries, and how identity moves between components. The section compares Authorization Code with PKCE, Client Credentials, On-Behalf-Of, and Device Code Flow, then uses a decision matrix to address common mistakes and security trade-offs.
- Authorization Code + PKCE:
- application for SPA and mobile applications,
- Client Credentials:
- service-to-service communication,
- daemon-type applications,
- On-Behalf-Of (OBO):
- identity propagation between services,
- Device Code Flow:
- selection of the appropriate flow:
- decision matrix,
- most common errors,
- security threats.
4. Managed Identity
Managed Identity provides Azure workloads with resource access without storing client secrets in code or configuration. The material covers system-assigned and user-assigned identities, permission grants to services such as Key Vault, Storage, SQL, and Microsoft Graph, plus platform limits and fallback with DefaultAzureCredential.
- Managed Identity types:
- system-assigned,
- user-assigned,
- configuration in Azure:
- App Service,
- Azure Functions,
- AKS,
- Virtual Machines,
- granting permissions to resources:
- Key Vault,
- Storage,
- SQL,
- Microsoft Graph,
- elimination of secrets:
- migration from client secret to Managed Identity,
- limitations and fallback:
- no cross-tenant,
- no on-prem support,
- DefaultAzureCredential.
5. Securing API endpoints
Protecting API endpoints starts with strict token validation, including issuer, audience, scopes, roles, and azp or appid claims. It also explains delegated versus application permissions, endpoint-level authorization patterns, and common risks such as over-permissioning, missing scope checks, and consent phishing.
- token validation:
- issuer,
- audience,
- scopes,
- roles,
- azp / appid,
- Delegated vs Application permissions in API:
- scp vs roles,
- access control at the endpoint level,
- security threats:
- over-permissioning,
- lack of scope validation,
- consent phishing,
- implementation patterns:
- validating middleware,
- [RequiredScope],
- [Authorize(Roles=...)],
- Best practices:
- separate frontend/backend registrations,
- minimum permission scope,
- admin consent workflow.
6. Microsoft External ID (CIAM)
Customer-facing identity requires a different setup than standard Entra ID, especially around sign-up, sign-in, and self-service journeys. The focus here is on configuring user flows, extending authentication with custom logic, and adapting branding and UX to external user scenarios.
- differences compared to standard Entra ID:
- User flows:
- registration,
- sign-in,
- self-service,
- Custom authentication extensions,
- branding and customization of the user experience.
7. Multi-service access architecture
In a multi-service model, the relationship between API publishers and consumers determines how scopes, roles, and application assignments are structured. The section covers central API design, access mapping across Enterprise Apps, and governance mechanisms such as Access Reviews, audit logs, and consent grant monitoring.
- API Publisher / API Consumer model,
- Central API:
- definition of scopes and roles,
- integration of multiple applications (Enterprise Apps):
- assignment of groups and roles,
- access management:
- who has access to what (role/scope),
- Governance and monitoring:
- Access Reviews,
- audit logs,
- monitoring of consent grants.