Microsoft Entra External ID
Fundamentals

Security Fundamentals

In brief

The page was retitled and rewritten to clarify security controls for external tenants, including authentication approach supportability, access control, Conditional Access, fraud, bot, DDoS, and monitoring protections. Links and descriptions were also updated.

What Entra admins need to know

Administrators can use the revised guidance to assess security controls for customer-facing identity flows.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Security fundamentals for Microsoft Entra External ID external tenants

[!INCLUDE applies-to-external-only]

External-facing identity systems support a wide range of customer experiences. That wide range also makes them attractive targets for common customerCustomer identity and access management (CIAM) attack patternssystems face threats such as credential stuffing, automated bot sign-ups, account takeover attempts, and high-volume traffic spikes. Understanding these threats helps explain why a clear, layered security approach is essential. Microsoft Entra External ID provides foundationalsecurity capabilities you can build on. Thison to address these threats. Use this guide helps you understand how to strengthen that foundation with recommendedprioritize controls and integrations based on common CIAM threat patterns.that help protect your customer-facing applications.

[!INCLUDE authentication-approaches]

This article outlines:

  • The attack vectors that commonly target CIAM systems.
  • The security controls that can help you address them.
  • A prioritized roadmap to guide implementation.
  • Available third‑third-party integrations for fraud, bot, and DDoSdistributed denial-of-service (DDoS) protection.
  • Known limitations specific to external tenants.

Our goal is to offer a practical, actionable roadmap that helps you make informed decisions about how to secure your customer-facing experiences.

Security model for external tenants

A defense‑in‑depth strategy requires combining multiple control layers:

  • Front‑Front-door protection (WAF,through a web application firewall (WAF), bot mitigation, and IP controls)controls.
  • Identity security (MFA,through multifactor authentication (MFA), Conditional Access, and access control) control.
  • Fraud prevention (sign‑through third-party sign-up and sign‑sign-in detection through 3P providers) providers.
  • Application‑Application-level authorizationauthorization.
  • Monitoring and alertingalerting.

Each layer addresses a different class of attacks, reducing the likelihood of compromise and limiting the blast radius.

Priority 1: Immediate implementation

TheseStart with these protections are foundational. They're quick to enable and essential for establishingestablish a securesecurity baseline for your external identity flows. Additional protections introduced in Priority 2 addressadds protections against fraud, bots, DDoS, and more advanced attack patterns.

Security feature Description Threats addressed User impact Implementation effort
Brute force protection Mitigates brute force attacks by limiting the number of sign-in attempts to prevent unauthorized access through repeated password guessing.
Note: Smart lockout focuses on password misuse; broader bot and fraud activity is addressed through additional controls later in this article.
Prevents brute force, account takeover. None — No end-user impact None – Enabled by default
Common networking HTTP protection These built‑in protections help filter malformed traffic, limit abusive request patterns, and mitigate common protocol‑level attacks.
Note: These safeguards support application stability, but high‑volume DDoS and sophisticated bots require WAF or bot‑mitigation integrations described later.
Protects against common network attacks. Low – Sensitive actions only None – Enabled by default
Access Control Ensures users onlyLimits user access what they should by applying app roles and authorization rules.
Note: Access Controlcontrol enforces authorization, not user verification -so combiningverification. Combine it with MFA and adaptive controls enhances overallto strengthen security.
Enforces authorization in applications. Medium– User adoption Medium – Setup required
Enable multifactor authentication (MFA) for all users MFA adds a second verification step beyond passwords, significantly reducing the risk of account takeover.
Note: MFA limits stolen‑credential attacks but must be paired with fraud detection and monitoring to prevent automated or malicious sign‑up attempts.
Adds second factor authentication. High – User adoption Medium – Setup required
Passkeys (FIDO2) Phishing-resistant, passwordless authentication that uses face, fingerprint, PIN, or a security key. A passkey satisfies MFA in a single gesture and can also serve as a primary, passwordless sign-in method. Prevents phishing, password theft, and credential replay. Low – Familiar gestures Medium – Setup and credential management UX required
Activity logging & User insights Activity logs and insights provide visibility into sign-ups, sign-ins, error patterns, and anomalies. They help you identify unusual trends and investigate issues quickly, supporting early detection, and informed decision making. Enables threat detection. None — No end-user impact Medium – Setup required
Security feature Description Threats addressed User impact Implementation effort
Conditional Access CustomizableConfigure policies that triggerto require MFA to defend against threats like phishing and account takeovers.manage sessions. Check control availability for your authentication integration, including sign-in frequency (SIF). See What is Conditional Access? and Developer guide to Conditional Access authentication context for more information. Provides risk-based access control. Medium – User adoption Medium – Setup required
Credential and secret management Prefer certificates over client secrets for app authentication to External ID because certificates are more secure and harder to compromise. Secures app credentials. None — No end-user impact Medium – Setup required
Token lifetime management Configure the token lifetime to reduce your app’s exposure to compromised tokens. Limits exposure. High – Requires frequent refreshes Medium – Setup required
Custom Domain with Web Application Firewall (WAF) Use Cloudflare, Akamai or Azure WAF for tenant security against DDoS attacks. Provides DDoS and bot protection. Medium – User adoption High – WAF integration
Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…