Agent365 Sample LangChain Agent Not Responding in Microsoft Teams After Successful Deployment

[keshavk-msft]

Description

I attempted to set up and deploy the Agent365 LangChain sample agent following the official setup instructions. The deployment and publishing steps completed successfully, and the agent is visible in the Microsoft 365 Admin Center → Agents.

However, when interacting with the agent in Microsoft Teams, the agent does not respond to any messages.

The chat window loads correctly and accepts input, but no response is returned from the agent.

I verified that the agent is deployed and published successfully and that the blueprint configuration has been completed in the Teams Developer Portal.

Expected behavior

After deployment and configuration, the agent should respond to user messages when accessed through Microsoft Teams.

SDK Version

v1.1.104-preview+80f983b74e

Language/Runtime

Node.js 20

OS

Windows 11

How to Reproduce

1. Clone the Agent365 samples repository.

2. Follow the setup instructions for Application Registration in Microsoft Entra ID.

3. Create an App Registration with the following delegated permissions:

   • AgentIdentityBlueprint.ReadWrite.All
   • Directory.Read.All
   • Application.ReadWrite.All
   • AgentIdentityBlueprint.UpdateAuthProperties.All
   • DelegatedPermissionGrant.ReadWrite.All

4. Grant admin consent for all permissions.

5. Run the following commands from the repository root:

a365 config init
a365 setup all
a365 deploy
a365 publish

6. After publishing, retrieve the blueprint ID:

a365 config display -g

7. Configure the agent in Teams Developer Portal:

https://dev.teams.microsoft.com/tools/agent-blueprint/<agentBlueprintId>/configuration

Set:

• Agent Type: Bot Based
• Bot ID:

8. Save the configuration.

9. Go to Microsoft 365 Admin Center → Agents and confirm the agent is published.

10. Open the agent in Microsoft Teams and send a message (e.g., "Hi").

Output

There is no response from the agent in Teams chat.

Screenshots

Code of Conduct

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