Not able to run/debug custom tab app using teams-toolkit

[Sarikagangwar7300]

I have created a React-Fluent-ui tab project using teams toolkit. When I am trying to run/debug my project using teams-toolkit, it prompts me to sign in into Microsoft 365 first, when trying to sign in getting

"
Sorry, a security policy is preventing access
An organization security policy requiring token protection is preventing this application from accessing the resource. You may be able to use a different application.

Error Code: 53003
Request Id: e3902560-3074-4d1e-b645-96fb0ca93300
Correlation Id: bf044236-ffa4-47a8-8f10-901bfab5b809
Timestamp: 2025-03-12T07:09:30.500Z
App name: Teams-Toolkit
App id: 7ea7c24c-b1f6-4a20-9d11-9ae12e9e7ac0
IP address: 2401:4900:1f3b:288c:f029:af76:d43b:68ef
Device identifier: c2f4825a-59d2-45b3-a7e8-34439a6df677
Device platform: Windows 10
Device state: Compliant

{"errorCode":"request_cannot_be_made","errorMessage":"Token request cannot be made without authorization code or refresh token.","subError":"","name":"ClientAuthError","correlationId":"b1cbc968-b2a4-47e0-9ebd-1ca3783cf100"} "

In VSCODE I get the below error-
[Error] - Unable to execute action aadApp/create. Error message: Login took too long. Please try again. [Error] - Failed to Execute lifecycle provision due to failed action: aadApp/create. LoginTimeout:Login took too long. Please try again.. Env output: {}

Summary: (×) Error: Lifecycle stage provision failed. (×) Error: aadApp/create failed. (×) Error: Login took too long. Please try again.

To Reproduce
Steps to reproduce the behavior:

1. Go to- vs code, Install Teams toolkit from extension
2. Once installed select the Teams Toolkit icon on the left in the VS Code toolbar, and click on create a new app, select tab after this select React-Fluent-UI then apps name
3. Press F5 to start debugging which launches your app in Teams using a web browser. Select Debug in Teams (Edge) or Debug in Teams (Chrome).
4. Prompts to sign in microsoft 365 account
5. Get the error

Expected behavior
When Teams launches in the browser

Screenshots

VS Code Extension Information (please complete the following information):

• OS: Windows
• latest

CLI Information (please complete the following information):

• OS: Windows
• latest

[teams-toolkit-assistant]

👋 Hi @Sarikagangwar7300,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Based on the information retrieved, here are the potential solutions for your issue:

Problem Overview:

You're encountering an issue when attempting to run/debug a Microsoft Teams custom tab app using the Teams Toolkit. The error is related to organizational security policy requiring token protection, blocking the application from accessing Microsoft 365 resources, resulting in error code 53003.

Steps to Resolve:

1. Check Organizational Security Policies:
   The error indicates that your organization's security policies are enforcing token protection, preventing the app from accessing the required resources. You may need to contact your organization's IT administrator to address this policy constraint.

2. Use Pre-Release Version of Teams Toolkit:
   Sometimes, issues are fixed in the pre-release versions of the toolkit. You can try switching to the pre-release version of the Teams Toolkit extension in Visual Studio Code:

   • Open Visual Studio Code.
   • Go to Extensions (Ctrl+Shift+X).
   • Search for "Teams Toolkit".
   • Click on the extension and select "Switch to Pre-Release Version".

   

3. Avoiding Duplicate Teams App ID:
   If teamsApp/create or aadApp/create fails due to a conflict with another app's ID in your tenant:

   • Modify the TEAMS_APP_ID value in env/.env.local or env/.env.dev to avoid duplication.
   • Alternatively, delete the TEAMS_APP_ID value to let Teams Toolkit assign a unique ID automatically.

Detailed Steps on Provisioning Actions with Teams Toolkit:

The following actions are designed for provisioning within the Teams Toolkit and may help you identify and resolve issues related to the aadApp/create step:

• teamsApp/create
• aadApp/create

You can refer to detailed documentation on provisioning actions here.

Troubleshooting and Common Workarounds:

• Ensure environment variables, like AAD_APP_CLIENT_ID and SECRET_AAD_APP_CLIENT_SECRET, are properly set.
• If the existing Azure AD app registration details are used, configure it in .fx/configs/config.{env}.json properly.
• Update necessary configurations in ./teamsapp.yml and ./teamsapp.local.yml.

References:

• Issues related to aadApp/create in Teams Toolkit GitHub
• Provision cloud resources in Microsoft Visual Studio - Provision actions
• Enable single sign-on for Teams app - Update Teams Toolkit configuration files

If you continue to have issues, providing additional logs and error details could help in further troubleshooting.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[nliu-ms]

Hey @Sarikagangwar7300 , it's a known issue recently found.

It's caused by some security policy in your tenant, preventing us to get token for a specific scope.

Can you please tell me if you're an FTE of Microsoft? So far, we only get issue reports from Microsoft tenant. Thanks!

Duplicate:
#13119

[Sarikagangwar7300]

@nliu-ms I am a vendor employee in Microsoft.

[nliu-ms]

Thanks @Sarikagangwar7300 , let's talk in Teams, the fix plan has not been decided.