Sync to teams 403 forbidden

[mdanielcristian]

Select the SPfx solution in the app catalog, click Sync to Teams -> error message "Failed to sync solution to Teams", further investigation in dev tools reveals the following error message: {"error":{"code":"-1, System.Net.WebException","message":{"lang":"en-US","value":"The remote server returned an error: (403) Forbidden."}}}

Some additional details:
-The user is a global admin
-The same solution with the same user was syncing successfully yesterday
-Tried new solution on different tenants, same issue
-I think it has something to do with the new teams admin portal, the old 'Allow sideloading of external apps' in the o365 admin center is off and disabled

and you are directed to the new Teams Admin portal, but everything there is enabled as well

Steps to reproduce

1. Create a new SPfx solution for a Teams Tab following the steps here: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
2. Click Sync to Teams, error occurs instead of the success message

Expected behavior

Sync to teams successfully

Developer environment

• OS: Windows 10, SharePoint Onine
• Framework: SPfx 1.10.0
• Browser(s): any
• Tooling: VS Code

[msft-github-bot]

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

[OliverZeiser]

I am seeing the same error. It was working a few days ago, now it seems to be broken on all tenants....

[canturan]

I have also the same issue. To test it i have created a complete new solution with the SPFx 1.10 solution, deployed it and tried to sync it to the teams. It get the same error message. If i create the manifest manually and upload the app to teams, then everything works without any problem.

Same behavior on all tenants.

[arunkumarperumal]

same issue even with SPFx version 1.9.1, sync to teams was working fine few days ago.

[VesaJuvonen]

Closed #5428 as a duplicate and we have continued investigation on this internally. Thanks everyone for reporting this and other reports also welcome.

[VesaJuvonen]

We have identified the root cause of this issue and are expecting it to get resolved within next 24 hours. We do apologize the issue and delay on getting it fully resolved.

[VesaJuvonen]

We just fixed the issue on the Azure AD side - certainly not optimal, but a mistake in the permissions between the services. My repro environment works without any issues now - which was broken before the fix - but would love few confirmations from you as well.

Notice that if you still get the 403 immediately when I sent this message - give it 30 min and try again... this should be now rolling gradually worldwide as setting is replicated.

Thanks for your confirmation advance.