Getting Network request failed when signing in to Microsoft 365

[mAbduqayum]

Description

I am getting the following error when trying to sing in to microsoft 365 in teams-toolkit:

{"errorCode":"network_error","errorMessage":"Network request failed","subError":"","name":"ClientAuthError","correlationId":"032e352e-baa5-4fea-ab42-b19b80acdb2b"}

To Reproduce

Steps to reproduce the behavior:

1. Go to VS Code
2. Click Team-Toolkit extension
3. Click Create New Bot: basic chatbot, typescript, default path, any_name
4. In Team-Toolkit extension try to sign in Microsoft 365.
5. See error:

Expected behaviour

It should sign in successfully. I don't have any issues when doing the same step in github codespaces.

• VS Code: 1.99.0
• OS: Ubuntu 24.04.1
• teams-toolkit: 5.14.1

[m365-agent-toolkit-assistant]

👋 Hi @mAbduqayum,

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:

Known Issue Overview:
Users have experienced similar network_error when trying to sign in to Microsoft 365 using the Teams Toolkit in different environments. This issue can be caused by various network configurations, proxy settings, or authentication flow discrepancies specific to the Teams Toolkit.

Immediate Troubleshooting Steps:

1. Check Network and Proxy Settings:
   Ensure that your machine is not behind a proxy or restrictivity configured firewall that might block the authentication request.

2. Clear Cached Authentication Data:
   Delete any cached authentication data that might be causing issues:

   • Remove files in ~/.fx/account
   • Clear the cache folder at ~/.fx/cache

3. Verify Connectivity:
   Test whether other tools (like msal auth-node sample) can connect successfully using the same network.

4. Evaluate Developer Tools Logs:
   Open developer tools in VS Code to observe any detailed error logs or network traces that might give more context.

5. Try with a Different User or Profiles:
   Use a new user profile on the same machine to check if the issue persists, as sometimes there are user-specific configuration problems.

Actionable Recommendations:

1. Check Proxy and Firewall:
   Ensure proxies are correctly configured or temporarily disabled to test connectivity.

2. Use CLI-Based Authentication:
   As an alternative route for immediate progress, you can use TeamsFX CLI for authentication and development tasks:

   teamsfx account login --m365

3. Validate Machine Network Setup:
   Use the following command to ensure your network and proxy settings are correct:

   curl -v https://login.microsoftonline.com

Reference Known Issues:

• GitHub Issue #11976 discusses network-related issues specifically for Teams Toolkit and offers proxy troubleshooting tips.
• Examining similar issues provides insights that include handling authentication workflows, updating dependencies, and configuring network settings correctly.

Additional Steps:

• If none of the above methods resolve the issue, please reinstall the Teams Toolkit extension or re-setup the environment from scratch as sometimes configuration files may have issues.

If the issue persists after applying these steps, please provide detailed error logs and network traces for further analysis.

---

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!

[sayali-MSFT]

@mAbduqayum ,Thank you for your inquiry about your Teams app development issue!

We are checking the issue. We will get back to you shortly.

[sayali-MSFT]

@mAbduqayum ,We are currently unable to reproduce the issue you’re experiencing.
We are checking this with internal team and let you know the update.

[mAbduqayum]

@sayali-MSFT I've installed windows and nixos in my system now. In Windows, it works, though occasionally I get this error.
In my NixOS, the issue is persistent.

[HuihuiWu-Microsoft]

Hi @mAbduqayum Do you have issue with logging in other tools/extension? I suspect this might be a network configuration issue for your NixOS.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.