API Permissions disappear from SharePoint admin center after approval

[thomaskjaerulff]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Describe the bug / error

I have a SPFx web part installed on a sharepoint enviroment with two Microsoft Graph webApiPermissionRequests in the package-solution.json file.

Once the SPFx web part is deployed, I go to the Sharepoint Admin Site API Access Page to approve the Web Api Permission Requests. After approving them, it looks well, but when I refresh the page, or navigate away and back, I can`t see the approved items anymore.

After redeploying the SPFx package to the app catalog site, the previously approved Web Api Permission Requests are shown in the Pending Request section again.

We are seeing this issue on multiple tenants so we believe we are dealing with a general issue.

Steps to reproduce

1. Navigate to the https://tenant-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/webApiPermissionManagement
2. Click on a pending request and approve it
3. Notice that the request has been visually approved and moved to the "Approved requests" group
4. Refresh the page and can not see the approved apis anymore
5. Upload the spfx package to the catalog site again
6. Refresh the WebAPIPermissionManagement Page again
7. The Approved API Items are shown in the Pending Request section

Expected behavior

I expect that after approving the Web Api Permission Requests, they will remain in the Approved section on the Sharepoint Admin Site API Access Page.

[joelfmrodrigues]

Same here!

[joelfmrodrigues]

@thomaskjaerulff could this be a duplicate from #9962 ?
I can also see the Deny endpoint being called as described on the other issue.

[thomaskjaerulff]

Thank you for your comment @joelfmrodrigues. You are absolutely right that this is a duplicate of #9962.
Please keep me posted if you know anything about this issue. We currently have two Premier Microsoft Support cases open on this issue on two different tenants. We see this issue on every tenant we come across, so we are dealing with a general issue that has to be fixed.

[joelfmrodrigues]

@thomaskjaerulff I was able to grant permissions for platform APIs by granting them directly to the relevant Entra ID app registration that is used by SPFx. You can use this blog post from the awesome @michaelmaillot as an example: https://michaelmaillot.github.io/tips/20210302-spfx-api-permissions/
Unfortunately, for my own app this doesn't seem to work at the moment as I can't see it listed under "My APIs" tab, even though I can see the network request retriving it. Perhaps a separate bug on the Azure portal.

[thomaskjaerulff]

Thank you for the information @joelfmrodrigues.
We did see this blog post and we have tried the suggested solution, however this was not working for us.
When approving the Microsoft Graph permissions using this method, our custom API was lost and vice versa.
If you have any other suggestions, kindly let me know.

[thomaskjaerulff]

To follow up on your previous comment @joelfmrodrigues. For further information, when trying to use the m365 CLI as suggested by @michaelmaillot in his great blog post, I receive the error message:

[joelfmrodrigues]

@thomaskjaerulff I had the exact same issue trying to approve my custom API, very frustrating.
I also tried via m365 CLI and PnP.PowerShell, but no luck. At this point, I decided to hold on until there is a reply from MS on the issue as I am not sure if there is something else I can try

[thomaskjaerulff]

@joelfmrodrigues - Keep in mind that this is happening for a standard Microsoft Graph permission also. I will let you know if something comes out of the two Premier Microsoft Support cases I have running.

[joelfmrodrigues]

@thomaskjaerulff there is an update on the duplicated issue :)
#9962

[thomaskjaerulff]

@joelfmrodrigues - Yes, I got a similar response on the two Premier Microsoft Support cases I have open on two different tenants. However they said the fix will be rolled out the 20th.
Having said the above, it is great that the issue will be resolved in the near future.

[VesaJuvonen]

As shared in the #9962, fix should be now out, but we would love to get this confirmed before closing this and the duplicate issue. Thanks for the confirmation advance 🙏