With Azure API Management can you hide "Try me" function for API for uauthenticated users and limit product subscription count

Question

With Azure API Management can you hide "Try me" function for API for uauthenticated users and limit product subscription count

curious7 281

With Azure APIM developer portal:

Question 1: Can you hide the "Try me" button if the user is not logged in or does not have any API/Product subscription
Question 2: Can we stop users from having multiple subscriptions to the same product

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-16T00:43:05.3266667+00:00
Hi @curious7

Welcome to Microsoft Q&A, Thank you for your question.

Hide the "Try me" button The Azure API Management Developer Portal is fully customizable. There is no built-in setting that automatically hides the "Try me" button based on whether a user is signed in or has a product subscription. If you need this behavior, it can be implemented through Developer Portal customization.

Prevent multiple subscriptions to the same product Yes, this is supported. Azure API Management provides a Subscription count limit setting at the product level. By setting the Subscription count limit to 1, you can restrict users to a single subscription for that product.

Thank you!
curious7 281 Reputation points

2026-08-16T11:14:49.7266667+00:00

@Mohammad Altaf Thanks for the information above. For question1 you mentioned that it can be implemented through Developer Portal customisation. I am not a developer so looking for some more guidance for that. Is there a example of this customisation you have seen or something similar that I could take as a starter.
How can this customisation be done?
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-20T17:31:05.6266667+00:00

Hi @curious7

I wanted to follow up and check whether you had a chance to review my earlier comment.

Thank you!

2 answers

Your answer

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-16T00:43:05.3266667+00:00

Hi @curious7

Welcome to Microsoft Q&A, Thank you for your question.

Hide the "Try me" button The Azure API Management Developer Portal is fully customizable. There is no built-in setting that automatically hides the "Try me" button based on whether a user is signed in or has a product subscription. If you need this behavior, it can be implemented through Developer Portal customization.

Prevent multiple subscriptions to the same product Yes, this is supported. Azure API Management provides a Subscription count limit setting at the product level. By setting the Subscription count limit to 1, you can restrict users to a single subscription for that product.

Thank you!
curious7 281 Reputation points

2026-08-16T11:14:49.7266667+00:00

@Mohammad Altaf Thanks for the information above. For question1 you mentioned that it can be implemented through Developer Portal customisation. I am not a developer so looking for some more guidance for that. Is there a example of this customisation you have seen or something similar that I could take as a starter.
How can this customisation be done?
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-20T17:31:05.6266667+00:00

Hi @curious7

I wanted to follow up and check whether you had a chance to review my earlier comment.

Thank you!

Answer 1

Hi @curious7

Azure API Management does not provide a built-in setting to hide only the "Try me" button based on whether a user is signed in or has a product subscription. This type of behavior would require customization of the Developer Portal.

Before considering customization, you may want to review the built-in access control capabilities available in API Management. Access to products and APIs is controlled through Groups, and the built-in Guests group represents unauthenticated users. By reviewing the product's access settings, you can control whether anonymous users can access the product and its APIs in the Developer Portal.

You can review this under:

Azure Portal → API Management → APIs → Products → [Your Product] → Access Control

If the Guests group is removed from the product's access settings, unauthenticated users will not be able to access that product and its associated APIs in the Developer Portal.

If your requirement is to allow users to view API documentation but hide or disable the "Try me" experience until they sign in or obtain a subscription, that scenario would require Developer Portal customization, as there is no out-of-the-box configuration available for this specific behavior.

I hope this helps clarify the available options.

If the assistance was helpful, kindly take a moment to click on Accept Answer and click on Yes. It will be helpful for other community members.

Thank you!

Answer 2

Hi @curious7 -

On the Try me button, you probably don't need custom development for this. The developer portal has visibility controls built in, and you can apply them at two levels.

Product level (simplest). Azure portal → your API Management instance → APIs → Products → select the product → Access control → + Add group. The groups listed there are the ones that can see the product and its APIs.

Guests is the built-in group for unauthenticated visitors. The portal only tells you its membership is system-managed, but the groups doc defines it as everyone who hasn't signed in. If Guests isn't in that list, unauthenticated visitors never reach the API page at all, so the Try me button isn't reachable for them. If it is listed and you don't want that, delete it. Full steps are in this section of the groups doc.

groups002

Page or section level. Open the developer portal admin interface (Developer portal → Portal overview → Developer portal). Select the section containing the test console and click the Change access icon, then restrict it to your signed-in groups. The same works per page — gear icon next to the page name on the Pages tab, then Access. Screenshots of both are in this section of the developer portal overview.

Use View as in the top menu to preview the portal as a Guest before you commit, then Publish.

One thing though, this only works on the managed portal, not a self-hosted one.