Microsoft Entra External ID
Architecture

Microsoft Entra External ID deployment guide for security operations

In brief

The deployment guidance continues to cover fraud prevention, account takeover, 30-day log retention, synthetic monitoring, and pricing and billing references.

What Entra admins need to know

Administrators can review the updated guidance when planning security operations for Microsoft Entra External ID. No action is required.

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.

Microsoft Entra External ID deployment guide for security operations

This document outlines security operations considerations to deploy Microsoft Entra External ID, an extensible solution to add customer identity and access management (CIAM) solutions to your apps. This document emphasizes edge-based attacks, particularly bots targeting sign-up, and sign-in endpoints. These vectors are commonly exploited in external identity systems and demand layered, proactive, defense strategies.

Key topics covered include:

International Revenue Share Fraud

An International Revenue Share Fraud (IRSF) is a financially driven attack possible when you expose short message service (SMS) verification on a publicly accessible endpoint. When you enable Microsoft Entra multifactor authentication (MFA) on Microsoft Entra External ID, IRSF attacks are possible. With SMS verification enabled, Microsoft Entra has two built-in protections:

  • Telephony throttling helps mitigate the risk of service outages and performance degradation
  • CAPTCHA for SMS-based MFA helps defend against automated attacks by distinguishing human users from bots. If a user is deemed high-risk, access is blocked, or a CAPTCHA challenge appears before an SMS verification code is sent.

Sign-in protection: Account takeover

Account takeover means a user account is compromised. The attacker changes account credentials, such as email, password, or phone number. These actions prevent the account owner from regaining control. These attacks are accomplished with a password spray.

Use multiple layers of defense to reduce the account compromise rate. Employ a combination of the following security controls.

Auditing and logs

Microsoft Entra External ID stores sign-in and audit logs for 30 days. For retention and analysis, export this information to an external storage or tool.

Configure Azure Monitor as a bridge to export logs. See the following diagram of Microsoft Entra External ID log exports with Azure Monitor. For more information, see Set up Azure Monitor in external tenants.

Monitoring helps ensure the efficient operation of identity and associated systems. These actions include establishing monitoring infrastructure, defining monitoring procedures, setting up dashboards or alerts, and creating a response protocol to handle alerts. See the following note, and a list of what to monitor.

  • Availability - Discover if the service is operational. Sometimes referred to as a heartbeat or health endpoint. Set it up on the monitoring system for it to execute frequently on in-use components. For custom extension APIs, we recommend you implement health endpoint monitoring. If you develop API using .NET, use health checks in ASP.NET Core to expose health endpoints. Monitoring availability is essential, but it might solely indicate service failures.
  • Functionality - Track functionality with synthetic transactions that mimic end-to-end user or system interactions involving dependencies: UI, API calls, logging. Many monitoring tools have features to automate multistep web experiences, like sign-up, profile edit, and MFA.
  • Performance - Track performance with synthetic transactions and server-side instrumentation to gather performance-related telemetry. In distributed systems like identity access management (IAM) with dependencies, identify, and resolve performance issues. Deploy performance probes across customer locations and establish a baseline for identity experiences. Set up triggers and notifications to detect deviations from a baseline. A system isn't beneficial if it's available but performs poorly.

Requests for authentication and identity come with a session correlation ID. When the identity system calls external custom extensions, this identifier is in the authentication context. To diagnose issues, log the identifier in the custom extension.

The following diagram illustrates monitoring and alerting setup. |Browser type: Google Chrome, Microsoft Edge,
Mozilla Firefox, Apple Safari|| |Mobile operating system: Android, iOS||

Continuous system validation

Changes in environments are inevitable. An automated continuous validation environment helps catch issues caused by changes. You can use the same synthetic monitoring infrastructure to set up this validation automation.

Microsoft Entra External ID pricing consists of a core offer and premium add-ons. Core offer billing is based on monthly active users (MAUs), the count of unique external users who authenticate to your tenants in a calendar month. A total comes from a combination of MAUs from workforce and external tenants linked to a subscription.

See more information on the pricing structure and billing model for Microsoft Entra External ID.

Costs and analysis

View incurred costs on the cost analysis area of the subscription/resource group linked to the Microsoft Entra External ID tenant. If the MAU count is below the free tier, the bill is $0. Usage data, below the free tier, appears in the cost analysis.

The following table correlates metric and a Microsoft Graph reference.

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…