Study guide
4.2 App Registrations, Permission Scopes & Service Principal Credentials
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
4.2 App Registrations, Permission Scopes & Service Principal Credentials
Key Takeaways Explain This Topic AI
An app registration creates a global application object in the home tenant; each tenant that uses the app gets its own service principal carrying the local grants.
Client secrets are capped at a 24-month lifetime in the Entra portal, and the application authentication methods policy can block secrets entirely in favour of certificates.
Exposing an API means defining an Application ID URI plus scopes for delegated access and app roles for application-only access.
Application Administrator and Cloud Application Administrator can manage credentials on apps, which makes them privileged roles that belong in PIM.
Application.ReadWrite.OwnedBy limits an automation account to the apps it owns instead of every application in the directory.
Last updated: August 2026
The Object Model: Application vs Service Principal
When you create an app registration , Microsoft Entra ID creates an application object in the tenant where you registered it (the home tenant). The application object is the global template: display name, sign-in audience, redirect URIs, credentials, requested permissions, and any API surface the app publishes.
A service principal is the local instance of that application in a tenant. It is created automatically the first time the app is consented to or assigned. Everything tenant-specific lives on the service principal: permission grants, user assignments, sign-in enablement, and Conditional Access targeting.
- Concept Application object Service principal
- Where it lives Home tenant only Every tenant that uses the app
- Portal blade App registrations Enterprise applications
Holds credentials Yes (secrets, certificates, federated credentials) Only for managed identities and legacy SPs
- Holds grants and assignments No Yes
- Deleting it Orphans the service principals Ends the app’s access in that tenant only
A multi-tenant SaaS app therefore has one application object at the vendor and one service principal in each customer tenant. That is why removing a vendor’s access is a service principal operation in your tenant, not a request to the vendor.
Credentials: Secrets, Certificates, and Federated Identity
Credential type Lifetime control Security posture
Client secret Maximum 24 months in the Entra admin center; 6 months is the default suggestion Weakest — a bearer string that leaks through source control, logs, and screenshots
Certificate You control validity; private key can live in Key Vault or an HSM Strong — proof of possession, no shared string to leak
Federated credential (workload identity federation) No stored credential at all Strongest for external workloads — an external OIDC issuer such as GitHub Actions or an EKS cluster exchanges its own token for an Entra token
Two controls belong in an AZ-500 answer about credential hygiene:
The application authentication methods policy (an Entra ID application management policy) can block password credentials outright or restrict their maximum lifetime, tenant-wide or per application. This is how you enforce "certificates only" rather than relying on developer discipline.
Managed identities , covered in the workload identity section, remove credentials entirely for anything running on an Azure resource. On the exam, prefer a managed identity whenever the workload runs in Azure; prefer workload identity federation when it runs outside Azure; use a certificate only when neither is possible; use a client secret last.
Rotation is an operational requirement, not an optional one: expired credentials cause outages, and long-lived ones cause breaches. Monitor upcoming expiry with Microsoft Graph ( Get-MgApplication and inspect passwordCredentials / keyCredentials end dates) and alert well before the date.
Exposing an API: Scopes and App Roles
When your own application publishes an API that other applications call, the registration must declare what callers may request.
Expose an API defines:
An Application ID URI , such as api://<appId> or a verified custom domain URI. This is the token audience.
Scopes (delegated permissions), each with an admin consent display name and description, an optional user consent description, and a Who can consent setting of Admins only or Admins and users . Marking a destructive scope as Admins only prevents self-service escalation.
Authorized client applications — pre-authorizing a known client for a specific scope so that its users never see a consent prompt. Use sparingly; each entry is a standing trust.
App roles define application-only permissions (and can also define user roles surfaced in the roles claim). A daemon calling your API receives an app role assignment rather than a delegated scope.
The API permissions blade on the caller side is the mirror image: it lists which permissions the app requests . Requesting a permission does not grant it — the grant only exists after consent.
Least-privilege permissions for automation
An automation account that manages application objects should not receive Application.ReadWrite.All , which reaches every registration in the directory. Use Application.ReadWrite.OwnedBy , which limits writes to applications where the principal is listed as an owner. This is a favourite exam contrast.
Administrative Roles That Can Take Over Applications
Any role that can add a credential to an application can become that application, inheriting all of its permissions. Treat these as privileged:
Role Capability Risk
Application Administrator Create and manage all app registrations and enterprise apps, including credentials Can add a secret to an app holding RoleManagement.ReadWrite.Directory and escalate to Global Administrator
Cloud Application Administrator Same, but cannot manage Application Proxy Same escalation path
Application Developer Register applications even when the tenant blocks general registration Limited, but creates unmanaged identities
Owner on an app registration Manage that specific app, including credentials Scoped, but still a takeover path for that app
Practical controls: turn off Users can register applications in User settings so registration is deliberate, make these roles eligible in Privileged Identity Management (PIM) rather than permanently assigned, and run access reviews over application owners. Auditing application ownership is as important as auditing directory role membership, because ownership is a quiet, permanent escalation route that most reviews miss.