Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Use this guide to build applications that authenticate identities, authorize access, minimize privilege, and protect APIs and tokens by using Zero Trust principles. It's for developers, application architects, identity professionals, and platform teams that design or govern application access.
Start with the task that matches your current decision. If you're designing a new application identity, use this sequence: register -> authenticate -> authorize -> minimize permissions -> protect APIs and tokens -> validate continuously.
Register and authenticate applications
Establish the application's identity boundary, supported account types, and authentication method.
- Integrate applications with Microsoft Entra ID and the Microsoft identity platform to build apps that IT professionals can secure in the enterprise.
- Register applications by using least privilege and assume-breach principles.
- Choose supported identity and account types for single-tenant, multitenant, and personal Microsoft account scenarios.
- Authenticate users for Zero Trust by verifying explicitly and applying least privilege.
Choose delegated or application permissions
Choose whether the application acts on behalf of a user or uses its own identity, then design authorization and consent accordingly.
- Acquire authorization to access resources.
- Develop a delegated permissions strategy for applications that act on behalf of a signed-in user.
- Develop an application permissions strategy for services and background processes that act without a user.
- Request permissions that require administrative consent.
- Apply authorization best practices.
- Coordinate developer and administrator responsibilities for registration, authorization, and access.
Reduce excessive privilege and protect workload identities
Limit access to what the application needs, and use managed identities where possible.
- Reduce overprivileged permissions and apps.
- Provide application identity credentials when there's no user by using managed identities for Azure resources.
Protect APIs and tokens
Treat tokens, API permissions, and downstream calls as part of the application's security boundary.
- Manage tokens for Zero Trust.
- Customize tokens.
- Configure group claims and app roles in tokens.
- Protect APIs through registration, permissions, consent, and access enforcement.
- Review an API protected by the Microsoft identity consent framework.
- Call an API from another API when the application works on behalf of a user.
Operate and validate continuously
Reevaluate access as risk, session context, application behavior, and organizational policy change.
- Secure applications with Continuous Access Evaluation.
- Understand Zero Trust compliance for applications.
- Use Zero Trust identity and access management development best practices throughout the software development lifecycle.
- Apply standards-based development methodologies.
Next steps
- Develop applications by using Zero Trust principles.
- Build Zero Trust-ready apps with Microsoft identity platform features and tools.
- Establish a Development Security discipline.
- Apply development security implementation patterns.
- Govern agent identities and privileged access.
- Secure AI agents at scale with Microsoft Agent 365.
- Integrate identity security solutions with Microsoft products.