Application ID URI unclearness

[rychlym]

[Enter feedback here]

1. I am not sure - the On the Azure AD application blade, from the toolbar, select the Settings button - there is no Settings button - instead the I found the Application ID URI to be able to change in the App registrations clicking the Application ID URI in the overview.
   Simiraly - the "Multi-tenanted field" i have found in the App registrations/Authentication/ Supported account types - Accounts in any organizational directory (Any Azure AD directory - Multitenant) radio button.

2. I am agan not so sure - there is a sentence - change the ID of your Azure AD app, so that it begins with https://yourtenant.onmicrosoft.com - what the "yourtenant" means here - there are several tenants in the, so does not look it should be one from these tenants. Should it be then the Publisher domain (seen in the App registrations/Branding) or it does not matter at all, just need to be an unique identifier?

3)There is a code of the webpart class establishing
this.context.aadHttpClientFactory
.getClient('https://contoso-api.azurewebsites.net')

then a sentence:
The URI passed into the getClient() method is the Application ID URI of the Azure AD application used to secure the enterprise API.
It is litle confusing, that the parameter 'https://contoso-api.azurewebsites.net' does not match the Application ID URI set in text above to be for example, https://contoso.onmicrosoft.com/contoso-api

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ecbbb69a-f2dd-ed42-d887-14a72494000f
• Version Independent ID: 7e5c254a-fd12-0fc6-fc7d-61f4ef009226
• Content: Consume multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework
• Content Source: docs/spfx/use-aadhttpclient-enterpriseapi-multitenant.md
• Product: sharepoint
• Technology: sharepoint-framework
• GitHub Login: @spdevdocs
• Microsoft Alias: spdevdocs

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[rychlym]

I have to come back to the point 3) The Spfx example started to work for me after the this.context.aadHttpClientFactory.getClient() having the Client ID as the parameter instead of the suggested Application ID URI!
The Application ID URI in the parameter caused troubles with the "Not Authorized" 400 status code, at the API call response time.

[andrewconnell]

The admin experience for Azure Functions & Azure AD have changed quite a bit since doc was written... it's due for a refresh based on the things you found. Thanks for sharing!

[vincepunkrock]

I have to come back to the point 3) The Spfx example started to work for me after the this.context.aadHttpClientFactory.getClient() having the Client ID as the parameter instead of the suggested Application ID URI! The Application ID URI in the parameter caused troubles with the "Not Authorized" 400 status code, at the API call response time.

Thank you for this!! A whole day spent trying to find how this is supposed to work after the recent changes.... only to find it's the doc that is misleading. nice

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.