Issue following doc Consume multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework

[JMTeamway]

Category

• Bug

Describe the bug

I can not complete the tutorial as the screens and options I see in my Azure differs from what is mentionned in the article.

Steps to reproduce

Follow the tutorial : https://docs.microsoft.com/fr-fr/sharepoint/dev/spfx/use-aadhttpclient-enterpriseapi-multitenant

Expected behavior

At the point where we make the Azure AD application multi-tenant (https://docs.microsoft.com/fr-fr/sharepoint/dev/spfx/use-aadhttpclient-enterpriseapi-multitenant#make-the-azure-ad-application-multi-tenant), just after the 'On the Azure Active Directory Settings blade, choose the Manage Application button.' step, the documentation shows the following configuration screen with a 'Settings' toolbar button :

On my side, I see this screen, without any toolbar or button :

Additional context

The account I'm using is global admin.

[msft-github-bot]

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

[JMTeamway]

Hi @bcameron1231 ,

I put you in copy of this ticket as you helped me on the very similar one #5727 .
I think this documentation is not up to date and I can't make it to the end myself.

I noticed another issue #5751 about updating this doc. I will participate with pleasure to the doc update if I can end up successfully the implementation.

Thanks for your help if you can !

[frags51]

Any updates on this?

[frags51]

Also There is a bit of inconsistency in what is shown in screenshots vs what is written, for permissions. Please provide the exact name of the app etc in both screenshot/docs, and also how exactly to request for permissions from another tenant (manifest file), aadHttpClient code etc.

[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.