An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Hi Aishah,
Based on the current Microsoft documentation and the behavior you've described, I don't believe a standalone Microsoft Entra External ID (CIAM) tenant is currently supported as a native identity provider for the API Management Developer Portal.
The confusion comes from the terminology. Microsoft now uses Microsoft Entra External ID as an umbrella brand that includes:
External Identities (B2B) in a workforce tenant
Customer identities (CIAM) in a dedicated external tenant
Today, APIM's developer portal identity providers still expect either:
A Microsoft Entra ID (workforce) tenant (login.microsoftonline.com), or
The legacy Azure AD B2C configuration, which relies on B2C user flows/policies (for example, B2C_1_signin). Those policy constructs don't exist in CIAM tenants, which explains the signinPolicyName validation error you're seeing.
That's also why configuring the Microsoft Entra ID provider against a ciamlogin.com authority results in AADSTS500208—the workforce provider isn't designed to authenticate CIAM consumer accounts.
At the moment, if you want to use CIAM identities, the supported options are generally:
Use Microsoft Entra External Identities (B2B) within a workforce tenant for developer portal authentication, or
Front the developer portal with a custom authentication layer until native CIAM support becomes available.
Unless Microsoft has announced new support very recently, I don't believe there's a supported configuration that allows a standalone CIAM tenant to be used directly as the APIM Developer Portal identity provider.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.