Azure AD (Microsoft Entra ID) application where I have exposed an API using Expose an API section.

Question

Hi Team, I am working on an Azure AD (Microsoft Entra ID) application where I have exposed an API using Expose an API section. Currently, I can see that only one Application ID URI can be configured for the app. My requirement is to understand:

• Is there any supported way to add multiple Application ID URIs to a single Azure AD application?
• If not, what is the recommended Microsoft approach to handle scenarios like:
• Multiple consumers
• Different environments (UAT / Prod)
• Multiple access paths for the same API I am aware of scopes and app roles, but I want to confirm if having more than one Application ID URI in the same app registration is possible or not. Any official guidance or best practices would be really helpful.Hi Team,

I am working on an Azure AD (Microsoft Entra ID) application where I have exposed an API using Expose an API section.
Currently, I can see that only one Application ID URI can be configured for the app. My requirement is to understand:

-

Is there any supported way to add multiple Application ID URIs to a single Azure AD application?

-

If not, what is the recommended Microsoft approach to handle scenarios like:

-

Multiple consumers

-

Different environments (UAT / Prod)

-

Multiple access paths for the same API

I am aware of scopes and app roles, but I want to confirm if having more than one Application ID URI in the same app registration is possible or not.
Any official guidance or best practices would be really helpful.

Answer 1

Hello Neeraj gautam,

No, setting up multiple Application ID URIs for a single app registration is not supported by Microsoft Entra ID (Azure AD). Only one Application ID URI, which serves as the aud (audience) claim in access tokens and uniquely reflects the API resource, may be assigned to each app.

• Use a single Application ID URI for multiple customers, and use scopes and/or app roles to manage access.
• Different environments (Dev, UAT, and Prod): Create different app registrations with unique Application ID URIs for each environment.
• Multiple access paths (URLs, gateways): The networking or routing layer handles access paths, not identity; maintain the same app registration and Application ID URI.

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know