Microsoft Entra External ID
Architecture

Deployment External Operations

In brief

The documentation now states that application management policies aren't available in external tenants and recommends expiration settings for client secrets. Fraud-protection integrations are described for Microsoft-hosted sign-up flows, with the native API tutorial reference removed.

What Entra admins need to know

This clarifies which credential controls and sign-up flows apply when planning an external tenant deployment.

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.

#customer intent: I need to understand subscriptions and billing, consumer app security, and how to prevent fraud tactics in Microsoft Entra External ID.

Special attention goes to processes to safeguard the sign-up and sign-in journeys from automated fraud, such as credential stuffing and International Revenue Share Fraud (IRSF). Find information on the importance of monitoring and alerting, continuous validation, usage tracking, and anomaly detection. These are actions essential for early threat detection and response. See the following diagram of a security operations flow.

Diagram of a security operations flow.

Tenant security with edge protection from DDoS and bot attacks

In the following diagram, see the custom domain example.

Diagram of a custom domain.

WAF configuration considerations

Security considerations Details
Prefer certificates over secrets When possible, use X.509 certificate credentials instead of password secrets. While secrets are easier to set up, certificates offer stronger security and can be the default method to acquire tokens.
Currently, managed identities and workload identities aren't available in Microsoft Entra External ID.
EnforceManage credential usage policieslifetimes Configure application authentication methodApplication management policies to restrict or block the use of secrets.aren't available in external tenants. If you use client secrets, set expirations to minimize exposure.
Avoid credentials on public client apps For applications that are public client apps, ensure no credentials are configured on the app registration. An example is apps with user sign-in via public endpoints. These apps shouldn't require client secrets or certificates.
Audit credentials regularly To ensure credentials are used, and haven't expired, periodically review credentials assigned to applications. Remove stale or unused credentials, avoid credential sharing between applications, and limit credentials per app.
Scan application code for sensitive data To detect application credentials, use static analysis tools like a credential scanner. Use the tool for other sensitive information in source code. Build artifacts before they're committed or deployed.
Consideration Details
Scale - Match RPS coming from Microsoft Entra External ID
- Respond within the timeout window with HTTP codes as per custom extensions guidance
Security - Ensure requests come from Microsoft Entra External ID. Microsoft datacenter ranges are documented. To lock the incoming requests, use ranges.
- To protect API from attacks such as DDoS, use a WAF in front of REST API. This effort ensures attacks are mitigated if REST API endpoint is targeted.
- To raise alerts for REST API or API experiencing security related challenges such as DDoS, use audits and logging with monitoring.
Resiliency - Scale up and down seamlessly
- To ensure a low or no effect on quality of service, recover REST API service and fault tolerance

|Reputation email filtering|To mitigate the risk of fraudulent email accounts, implement domain validation. Restrict sign-up from email addresses with poor reputations, or known associations with malicious activity. Microsoft Entra External ID supports custom extensions during sign-up. To evaluate the reputation of the email domain, invoke a REST API during the sign-up flow. Based on the reputation score, the system allows or blocks the sign-up request.| |IP email filtering|To reduce the risk of fraudulent account creation, we advise you to restrict sign-ups from anonymous proxies or IP addresses tied to Autonomous System Numbers (ASNs) outside your organization's business regions. This strategy helps reduce exposure to high-risk or untrusted traffic sources.
Microsoft Entra External ID supports custom authentication extensions to invoke during the sign-up process. Use these extensions to call a REST API to assess the reputation or geolocation of the IP address initiating the sign-up request. Use this process during email one-time password (OTP) verification.| |Excessive OTPs from one IP address or ASN|Implement monitoring and alerting when a high volume of email OTP requests originates from the same IP address, ASN, or location. For example, trigger an alert if email OTPs come from a single IP or similar geo-coordinates in a short time.| |Sign-up protection (Security Store)|Use Microsoft-built native integrations with Arkose Labs and HUMAN Security to detect and block bot-driven sign-ups and fake account creation.creation in Microsoft-hosted sign-up flows. Configured through the Microsoft Security Store in the Microsoft Entra admin center.|

To strengthen defenses,For Microsoft-hosted sign-up flows, Microsoft Entra External ID integrates with industry-leading non-Microsoft fraud protection providers through the Microsoft Security Store. Native, Microsoft-built integrations are available for Arkose Labs and HUMAN Security, which deliver comprehensive bot detection to detect bots and prevent fake-account-prevention capabilities during the sign-up flow.account creation. For configuration steps, see Integrate Microsoft Entra External ID with Arkose Labs and HUMAN Security for fraud protection.

For native authentication API flows, see Tutorial: Integrate third-party bot protection with Native API sign-up flows.

International Revenue Share Fraud

Security control Description
WAF: Bot protection To trigger OTP messages during sign-up, enable the frontline of defense against IRSF attacks, typically driven by bots that generate high-volume traffic.
Regions that require MFA telephony verification opt-in Help prevent telephony-based fraud: Microsoft doesn't automatically enable phone-based MFA verification for some country or region codes. To support sign-in from these regions, an administrator submits a support request to opt in and enable telephony verification for those codes. To allow traffic from deactivated regions, activate them with the Microsoft Graph API. For more information, see Regional opt-in for MFA telephony verification with external tenants.
Excessive SMS OTPs from one IP address or ASN. Implement monitoring and alerting for a high volume of SMS one-time password (OTP) requests originating from the same IP address, ASN, or geographic location. For example, trigger an alert for excessive SMS OTPs from a single IP or geo-coordinates in a short time. This scenario can indicate an IRSF attack.
To improve accuracy and reduce noise, refine the alert criteria. Focus on unsuccessful OTP requests by users. In IRSF scenarios, attackers typically don't complete authentication. Then want to generate SMS traffic to phone numbers for financial gain. Use this approach to see potentially malicious activity while minimizing false positives.

Sign-in protection: Account takeover

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.

Diagram of log exports with Azure Monitor.

This configuration requires projecting a Microsoft Azure resource group with the resources from the enterprise tenant to the Microsoft Entra tenant.

The following diagram illustrates monitoring and alerting setup.

Diagram of the setup for monitoring and alerting.

Service degradation and failure alerting setup

|Sign-in|| |Sign-up|| |MFA by type: Email OTP, telephony OTP|| |Browser type: Google Chrome, Microsoft Edge,
Mozilla Firefox, Apple Safari|| |Mobile operating system: Android, iOS ||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 syntacticsynthetic monitoring infrastructure to set up this validation automation.

Synthetic transactions can reference applications and APIs used for token acquisition, validation, and integration components such as API managers and service buses. We recommend you maintain versions of supported services, operating systems, and runtime environments. Each component continuously reports test success or failure. This action ensures identity services availability and early detection of potential failures.

Dashboards: Operational telemetry and security insights

Microsoft Entra External ID has built-in dashboards with useful telemetry from key areas such as authentication trends, MFA usage, and protections related to SMS verification. Use insights to maintain visibility into your identity system health and threat posture. For your deployment and operational strategy, we recommendedrecommend you incorporate regular metrics monitoring. Detect anomalies, assess risk exposure, and ensure the effectiveness of security controls. Use the following table to see metrics and details. For more information, see Gain insights into your app users' activity.

Metric Details
Authentications The Authentications dashboard summary has daily and monthly authentications in the tenant.
- Daily authentications for 30 days
- Daily authentications by operating system
- Monthly authentications for 12 months, by location
MFA usage The MFA Usage dashboard summary has monthly MFA authentication performance for applications. View the following trends:
- Users registered for MFA
- MFA types used, with success and failure count for 12 months
- CAPTCHA triggers and activity for 30 days
Telecom To understand telecom MFA performance, use the dashboard metrics for actionable insights into SMS MFA usage. Note the following states.
Allowed - Users who received an SMS during sign-in or sign-up.
Blocked - Users who didn't receive an SMS. If telecom MFA is blocked, users are notified to try alternate authentication.
Challenged - This feature is for unusual behavior. See it when a CAPTCHA challenge appears before the SMS goes. The following metrics also appear:
- Users unable to complete CAPTCHA - Track users that didn't pass the CAPTCHA challenge. If warranted, you can assess if the CAPTCHA is too difficult for legitimate users. Make needed adjustments to balance security and accessibility.
- Users that completed CAPTCHA - Review users that completed the CAPTCHA challenge. Get insight into how CAPTCHA protects users from automated attacks while it enables legitimate users to authenticate.

Microsoft Entra External ID core offer and add-ons

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.

In the Microsoft Entra admin center, for the Microsoft Entra External ID tenant, use the usage and insight dashboard to view utilization details, even when usage is below the free tier.

Metric Graph reference Description
activeUsers activeUsersMetric
authentications authenticationsMetric
mfaCompletions mfaCompletionMetric
signUps userSignUpMetric
summary insightSummary
userCount userCountMetric

In the Microsoft Entra admin center, under Monitoring and health, select Usage & insights. View user data, over time, and other areas such as authentication, and MFA usage.

Diagram of the usage and insights dashboard.

Next steps

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…