Managing external identities to enable secure access for partners, customers, and other non-employees
Capture one complete failing transaction, correlate it with both tenants’ sign-in logs, and open a Microsoft Entra support request if ciamlogin.com consistently emits esctx with SameSite=None but no Secure, because no supported customer setting is documented for changing a cookie emitted by that Microsoft-hosted domain.
What the cookie evidence establishes
-
esctxis a Microsoft Entra session-context and CSRF-protection cookie. It binds a request to a browser instance to prevent replay and contains no user information.^1^ - Chrome cross-site authentication requires cookies intended for cross-site use to follow the
SameSite=None; Securemodel. Microsoft documents that incorrect SameSite handling can break authentication flows.^2^ - The documentation does not publish a product-specific guarantee describing the exact
esctxattributes on every External ID federation response. However, the header you captured is incompatible with Chrome’s handling ofSameSite=None. - Rejection of a transaction-state or CSRF cookie could prevent the federation continuation. The browser warning alone does not prove that this is the actual stopping condition; External ID can also return HTTP 200 HTML containing a federation validation error.
- The current External ID known-issues article does not list a public issue specifically for
ciamlogin.com,esctx, and a missingSecureattribute.^3^
Your application cannot rewrite a Set-Cookie header issued for Microsoft’s ciamlogin.com domain. Do not attempt to weaken your application cookies or disable Chrome security controls as a production workaround.
Distinguish a cookie failure from a rejected OIDC response
Export a sanitized HAR while reproducing the issue in a fresh Chrome profile:
- Open Developer Tools → Network.
- Enable Preserve log and Disable cache.
- Reproduce the entire flow.
- Capture:
- The authorization request from External ID to the workforce tenant.
- The POST or redirect returning to
/federation/oauth2. - The complete response headers that set
esctx. - The HTTP 200 response body and any JavaScript console error.
- Request IDs, correlation IDs, UTC timestamps, and any
AADSTSor External ID error.
- Remove tokens, authorization codes, secrets, and personal data before sharing the trace.
In particular, look for error 40015 or “No email address was obtained from the external OIDC identity provider.” Error 40015 means upstream authentication succeeded but External ID could not validate the custom OIDC configuration or returned token.^4^
Verify the federation contract
For workforce-tenant federation, Microsoft documents these callback URIs in the workforce tenant’s app registration:
https://<tenant-subdomain>.ciamlogin.com/<tenant-ID>/federation/oauth2
https://<tenant-subdomain>.ciamlogin.com/<tenant-subdomain>.onmicrosoft.com/federation/oauth2
Also verify:
- Supported account types is Accounts in this organizational directory only.
- Delegated permissions include
email,openid,profile, andUser.Read, with admin consent. - The issuer uses the workforce tenant GUID or its
onmicrosoft.comdomain—not another verified custom domain. - The identity provider is attached to the applicable External ID user flow.^4^
If the returned ID token lacks email, go to the workforce tenant’s App registrations → federation application → Token configuration → Add optional claim → ID → email, save, and retest. External ID requires the email claim for this federation scenario. Granting the delegated email permission does not itself guarantee that the ID token emits an email claim.^4^
If the identity-provider issuer or related configuration was changed after it was added to the user flow, remove the provider from that flow, save, add it again, save, and retest so the flow refreshes its configuration.^4^
Logs and escalation
With at least Reports Reader, check both tenants at Entra ID → Monitoring & health → Sign-in logs. Filter by user, application, failure status, and reproduction time; record the correlation ID, error code, failure reason, and additional details.^5^
From the relevant event, select Launch the Sign-in diagnostic. It analyzes the event and provides remediation recommendations.^6^
If the trace confirms repeated malformed Set-Cookie responses and no token/configuration error explains the stop, create a support request from Diagnose and solve problems. Include:
- External and workforce tenant identifiers.
- UTC timestamp and correlation/request IDs.
- Sanitized HAR showing the return from the workforce tenant and malformed header.
- Chrome version and a screenshot of the blocked-cookie issue.
- Whether another supported browser reproduces it.
- A minimal reproduction and affected user-flow/application IDs.
Microsoft Support and the Entra engineering team can correlate these details with service-side tenant and sign-in telemetry.^7^
References
- Web browser cookies used in Microsoft Entra authentication
- How to handle SameSite cookie changes in Chrome browser - Microsoft identity platform | Microsoft Learn
- Known issues in external tenants - Microsoft Entra External ID | Microsoft Learn
- Add a Microsoft Entra ID tenant as an OpenID Connect identity provider
- How to troubleshoot Microsoft Entra sign-in errors
- What is the Sign-in diagnostic in Microsoft Entra ID?
- Microsoft Entra diagnostic logs