An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Hi @Ryan Suarez ,
Thank you for reaching out to Microsoft Q & A !
Your trace shows that Entra authentication succeeds, but APIM rejects the subsequent developer-account registration with 400 ValidationError: User registration is not supported. This appears consistent with an APIM-side registration issue, although the cause for your instance is not yet confirmed.
Could you check API Management → Developer portal → Identities and confirm:
- Whether the Username and password provider has been removed or disabled, leaving Microsoft Entra ID configured.
- Your APIM SKU, and whether existing Entra ID users can still sign in.
This is a configuration check only—please leave your authentication and portal-access restrictions unchanged. Microsoft documents that the username/password provider can be removed when another provider such as Entra ID is configured, so I would not recommend re-enabling basic authentication as a fix. [learn.microsoft.com]
Reference: Configure developer portal authentication — Delete the username and password provider.
If registration remains blocked after confirming these details, an Azure API Management support request would allow instance-specific investigation. Include the APIM resource ID, subscription and tenant IDs, Canada Central region, exact failure timestamp in UTC, any request/correlation IDs, and the complete POST /users HTTP 400 response. Share these through the private support case, excluding tokens, cookies, and client secrets.
Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.