Managing external identities to enable secure access for partners, customers, and other non-employees
A single controlled Microsoft Graph request should isolate the failure; if Graph can reach the Conditional Access endpoint, create the app-scoped MFA policy through Graph, but if Graph also returns HTTP 429, capture its headers and escalate the tenant-side throttling.
1. Test the management endpoint
Run a read-only test against the external tenant, using an organizational account—not a personal Microsoft account:
Install-Module Microsoft.Graph -Scope CurrentUser
Import-Module Microsoft.Graph.Identity.SignIns
Connect-MgGraph -TenantId "<external-tenant-id>" `
-Scopes "Policy.Read.All","Policy.Read.ConditionalAccess"
Get-MgIdentityConditionalAccessPolicy | Format-List Id,DisplayName,State
Microsoft documents these commands for listing Conditional Access policies.^1^
Interpret the result as follows:
- Policies are returned: the Graph policy endpoint is reachable, making the portal path more likely to be the affected component. This does not prove every backend call used by the portal is healthy.
- HTTP 429: the management endpoint is also throttling. Record
Retry-After,request-id,client-request-id, UTC time, tenant ID, and HTTP status. - 403: investigate role, consent, or Graph permissions rather than throttling.
- 401: verify that authentication occurred against the external tenant.
Graph Explorer or the browser developer tools’ Network tab is the most reliable way to inspect the raw response headers:
GET https://graph.microsoft.com/v1.0/identity/conditionalAccess/policies
Microsoft Graph can apply global and service-specific throttles, so avoid repeatedly polling this endpoint.^2^
2. If the read succeeds, create a narrowly scoped MFA policy through Graph
The administrator needs Security Administrator or Conditional Access Administrator, plus delegated Policy.Read.All and Policy.ReadWrite.ConditionalAccess. Delegated personal Microsoft accounts are unsupported for this operation.^3^
Use the broker application's Application (client) ID, shown under Entra ID → App registrations → broker application → Overview. Initially target one test customer and exclude emergency-access accounts:
Connect-MgGraph -TenantId "<external-tenant-id>" -Scopes `
"Policy.Read.All","Policy.ReadWrite.ConditionalAccess"
$params = @{
displayName = "Broker portal - test MFA"
state = "enabled"
conditions = @{
users = @{
includeUsers = @("<test-customer-object-id>")
excludeUsers = @("<emergency-account-object-id>")
}
applications = @{
includeApplications = @("<broker-application-client-id>")
}
clientAppTypes = @("all")
}
grantControls = @{ operator = "OR"; builtInControls = @("mfa") }
}
New-MgIdentityConditionalAccessPolicy -BodyParameter $params
This immediately enforces MFA for the named test customer, so verify the IDs and emergency exclusion before executing it. A successful create returns the new policy; the underlying REST operation returns 201 Created.^3^
After the controlled sign-in succeeds, expand the assignment to the intended users. External tenants support Conditional Access policies that require MFA for a selected application.^4^
One configuration caveat applies: email OTP can be the MFA factor when the local-account primary method is Email with password. Customers using Email with one-time passcode as their primary sign-in method cannot also use email OTP as the secondary MFA factor.^5^
3. Capture portal-side evidence
Because waiting and fresh browser sessions have already failed, collect evidence rather than repeating those steps:
- Open browser developer tools → Network.
- Reproduce Entra ID → Conditional Access → Policies once.
- Select the failed request and save:
- Request URL and method
- HTTP status
-
Retry-After,request-id, andclient-request-id - UTC timestamp
- Sanitized response body
- In the portal, select Notifications (bell) → failed notification → Copy error. Notification details can expose a client request ID, notification ID, timestamp, and internal transaction ID.^6^
- Check Entra ID → Monitoring & health → Audit logs, filtering Service = Conditional Access around
2026-11-18 13:08 UTC. External tenants support audit and sign-in logs, with seven-day activity-log retention.^7^
The documented External ID request-per-second limits concern customer authentication endpoints and token issuance; they do not establish that this admin management failure was caused by customer sign-in traffic.^8^
4. Escalate persistent 429 responses
Microsoft does not document a customer-accessible reset or quota-increase operation for this Conditional Access management path. Check Azure Service Health, then open a single technical incident containing the captured headers, UTC window, tenant ID, affected portal paths, Graph result, and sanitized HAR or screenshots.
External tenants currently cannot directly submit technical support requests. Use Give Feedback from the external tenant’s support page, or switch to an associated workforce tenant and open the Entra support request there.^9^
References
- View applied Conditional Access details in the Microsoft Entra activity logs
- Microsoft Graph service-specific throttling limits - Microsoft Graph | Microsoft Learn
- Create conditionalAccessPolicy
- Multifactor authentication in Microsoft Entra External ID external tenants
- Add multifactor authentication (MFA) to an app
- Troubleshoot password-based single sign-on
- Supported features in Microsoft Entra External ID workforce and external tenants
- Service limits and restrictions - Microsoft Entra External ID | Microsoft Learn
- Find help and get support for Microsoft Entra