microsoft / microsoft/Agent365-Samples

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

Open
#238 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
108
Forks
59
PR merge metrics
No merged PRs in 30d

Description

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
  1. After publishing, retrieve the blueprint ID:
a365 config display -g
  1. Configure the agent in Teams Developer Portal:
https://dev.teams.microsoft.com/tools/agent-blueprint/<agentBlueprintId>/configuration

Set:

  • Agent Type: Bot Based
  • Bot ID:
  1. Save the configuration.

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

  3. 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
Image Image Image
Code of Conduct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the Agent365 LangChain sample using a365 config init, a365 setup all, a365 deploy, and a365 publish. Check the blueprint ID from a365 config display -g and review the Teams Developer Portal agent-blueprint configuration. Done means the published agent returns a response to a message in Microsoft Teams.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.