Teams CLI New - API Options describe in help, not available "microsoft-entra"

[pkbullock]

Describe the bug

The built in help guidance for the tool describes an api auth type of "microsoft-entra" however when creating a new agent with API options, this is not a valid option.

Run teamscli new -h in the output, this is show in the output:

When building out the interactive or non-interactive options, this is not correct:

Using 3.0.7 of CLI.

Changing to OAuth fixes the issue, but is this option equivelant to the same option?

[m365-agent-toolkit-assistant]

👋 Hi @pkbullock,

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:

Thank you for providing the details. From your description, it seems you are encountering an issue where the teamscli new command's help output lists an api auth type of microsoft-entra, but this option is not recognized when actually running the command to create a new agent.

Given the specific nature of your problem, here are some steps and potential solutions to help resolve this issue:

1. Verify CLI Version Compatibility:
   Ensure that you are using the latest version of the Teams CLI. Sometimes, documentation updates may be ahead of the actual feature release in the CLI. To update the Teams CLI to the latest version, run:

   npm install -g @microsoft/teamsfx-cli

2. Check for Known Issues:
   It's possible that this could be a known issue that has been reported. You can check the Teams Toolkit GitHub repository for any similar issues or updates: Teams Toolkit GitHub Issues.

3. Use Alternative Authentication Methods:
   Since changing to OAuth resolves the issue, it indicates that OAuth is a valid and equivalent option for authentication. The microsoft-entra option might be a new or deprecated feature not yet fully implemented or documented correctly. For now, you can use OAuth as an alternative.

4. Provide Feedback:
   If you believe this is a documentation error or a bug, consider opening an issue on the Teams Toolkit GitHub repository to provide feedback to the development team. Include details such as the CLI version, error messages, and screenshots to help them understand and address the issue: Submit an Issue.

5. Manual Configuration:
   If you need to use microsoft-entra specifically, you can try configuring it manually by editing the project files created by the CLI. This might involve modifying configuration files to include microsoft-entra as the auth type and ensuring that all necessary settings are correctly applied.

6. Documentation Review:
   Review the official Teams Toolkit documentation for any updates or corrections regarding the use of microsoft-entra for API authentication: Teams Toolkit Documentation.

If you need further assistance or clarification, please provide more details about the error messages you encounter when using microsoft-entra, and I can help you troubleshoot further.

---

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!

[Meghana-MSFT]

@pkbullock - Could you please share the document that you are referring to while working with above commands? We checked the Teams toolkit CLI doc but could not find the above command.

[huimiu]

Hi @pkbullock, thanks for reaching out. This seems to be an issue with the teamsapp -h command. The 'microsoft-entra' authentication hasn't gone GA yet. It will be GA in February.

For now, you can set a system environment variable with TEAMSFX_API_PLUGIN_AAD=true to try the 'microsoft-entra' option.

[huimiu]

The 'microsoft-entra' authentication is now GA, feel free to give it another try. Let's close this issue first, please let us know if you have any other questions. Thanks!