Blueprint creation via CLI only enables Copilot as an available channel

[s-sridharan]

Description

When following the CLI flow to create a blueprint and register a messaging endpoint, the resulting agent only shows Copilot as an available channel. The Teams channel is not activated, which means end users cannot receive messages through the bot/API-based Teams endpoint after hiring an instance.

Expected behavior

Automatic addition of teams as an available channel for the created blueprint so that as per the documentation, post creation of an instance the user receives notification from the agent and can converse with it on teams.

SDK Version

1.1.103-preview

Language/Runtime

.NET 10.0.101

OS

Windows 11

How to Reproduce

1. Run a365 setup all with a valid a365.config.json
2. After setup completes, navigate to the agent blueprint in the Microsoft 365 admin portal
3. Observe the Channels section under the blueprint overview page - it will show only Copilot.

Output

No response

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'bug' because the user reports unexpected behavior where the Teams channel is not activated as expected during the blueprint creation process.
Priority: Assigned P2 because it impacts functionality for end users (Teams channel not available), but it does not render the system completely unusable and has a potential workaround by manually activating the channel.
Copilot: This issue involves debugging and modifying CLI behavior to ensure proper channel activation, which likely requires understanding of business logic, external API integration, and possibly changes across multiple files or services. Copilot is not suited for such tasks.
Assignment: Grant Harris is the most suitable engineer for this issue due to his expertise in backend development, CLI, and .NET, which align closely with the issue's context. Additionally, his contribution count is relatively low, indicating he has capacity to take on this task.
Labels: Applied labels bug, P2 based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: bug
Priority: P2
Confidence: 95.0%

Recommended Assignee: @gwharris7

Analysis:
type rationale: Classified as 'bug' because the user reports unexpected behavior where the Teams channel is not activated as expected during the blueprint creation process.

priority rationale: Assigned P2 because it impacts functionality for end users (Teams channel not available), but it does not render the system completely unusable and has a potential workaround by manually activating the channel.

copilot rationale: This issue involves debugging and modifying CLI behavior to ensure proper channel activation, which likely requires understanding of business logic, external API integration, and possibly changes across multiple files or services. Copilot is not suited for such tasks.

assignment rationale: Grant Harris is the most suitable engineer for this issue due to his expertise in backend development, CLI, and .NET, which align closely with the issue's context. Additionally, his contribution count is relatively low, indicating he has capacity to take on this task.

labels rationale: Applied labels bug, P2 based on issue type and priority

[SUGGESTION] Suggested Approach

1. Investigate the CLI command a365 setup all implementation in the src/Commands directory, particularly focusing on the logic responsible for registering messaging endpoints. Ensure that the Teams channel is being properly configured alongside Copilot during the blueprint creation process.
2. Check the configuration file parsing logic for a365.config.json in the src directory. Verify that the Teams channel settings (if any) are being read correctly and passed to the blueprint creation process. Add validation to ensure all required channels are included in the configuration.
3. Review the API calls made during the blueprint creation process, specifically in the Microsoft.Agents.A365.DevTools.Cli namespace. Ensure that the API request payload includes the Teams channel as an available option when registering the messaging endpoints.
4. Add or update unit tests in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Commands to validate that the Teams channel is correctly added during the blueprint creation process. Include test cases for scenarios where the Teams channel is missing or misconfigured in the input configuration file.
5. Update the documentation in the docs directory to include detailed instructions on how to configure the Teams channel in a365.config.json. Provide examples and clarify any prerequisites for enabling Teams as a channel during blueprint creation.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models