microsoft / microsoft/Agent365-Samples
Regarding A365 N8N agent not working
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 108
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Description
GitHub Repo : https://github.com/microsoft/Agent365-Samples/tree/main/nodejs/n8n/sample-agent
Followed this documentation and successfully executed steps from 1 to 6
But in this step
Step 7: Hire an agent as a digital worker
Follow the documentation to hire an agent as a digital worker
Your agent is now ready to handle conversations through Microsoft 365!
Not able to see the agent in teams.
Expected behavior
No response
SDK Version
v1.1.104-preview+80f983b74e
Language/Runtime
Node.js 20
OS
Windows 10
How to Reproduce
Follow this Repo steps:
https://github.com/microsoft/Agent365-Samples/tree/main/nodejs/n8n/sample-agent
Summarized steps:
Create Agent Blueprint - Register your agent identity in Microsoft Teams Developer Portal
Publish to Microsoft Admin Center - Make your agent available for administration (skip deployment step)
Add Client Secret - Configure authentication credentials in Azure Portal
Create n8n Workflow - Build your agent logic using the Microsoft Agent 365 node
Configure Backend URL - Connect your agent blueprint to the n8n webhook
Output
No response
Screenshots
Code of Conduct
- I agree to follow the Microsoft Open Source Code of Conduct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with nodejs/n8n/sample-agent and retrace the documented steps through agent onboarding, publication, and Teams availability. Check where the setup diverges from the issue's expected flow and verify that the agent appears in Teams after completing the listed configuration.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100