Authentication work in Azure API Management Service

Hey Divya Chawla,

So when you remove the signup page from the Azure API Management developer portal, here's what happens:

What "removing signup" actually means:

You're basically turning off self-service registration. The signup page just disappears from the portal - users can't create their own accounts anymore. Instead, you have to manually add users through the Azure portal or use automated provisioning (like Azure AD integration).

How it works on the frontend:

The developer portal is just a website - when you disable signup, the portal template removes that page from the navigation and blocks the route. If someone tries to directly navigate to /signup, they'll get redirected or see a 404.

The key thing is: removing signup doesn't change how authentication works. Users still sign in the same way - either with:

• Username/password (for manually created accounts)
• Azure AD / Entra ID
• OAuth/OpenID Connect providers you've configured

Common setup after removing signup:

Most people do this when they want tighter control over who gets API access. You typically:

1. Disable the signup page in the portal settings
2. Set up Azure AD integration so only people in your organization can sign in
3. OR manually create accounts for external partners/customers
4. Users still go to the developer portal and click "Sign In" - just no "Sign Up" button

If you're asking about the technical details:

The developer portal is customizable - it's built on templates. When you disable signup:

• The UI hides/removes signup links
• Backend validation checks ensure new user creation is blocked
• Sign-in functionality stays completely unchanged
• Existing users can still authenticate normally

Is there a specific scenario you're trying to set up? Like are you trying to restrict access to just your company's users or something else?

Best Regards,

Jerald Felix