Kylon vs Microsoft Teams
Teams is where you talk. Kylon is where the work gets done.
Kylon is a company harness where agents join your team, understand your business context, and execute real work across the tools you already use.
01 Which one is the right answer
Not every team should pick the same one.
Teams is the right answer when
Your company runs on Microsoft 365, the conversation is the product, and nobody wants a second place to check. A bot inside Teams is far less disruption than a new workspace.
Kylon is the right answer when
The talking already happens somewhere and the work still does not get finished. You want shared company context, agents that execute, and a review step you can see.
02 Operating model
How an agent lives in each one
Every statement about Microsoft Teams below cites Microsoft's own documentation. Checked 2026-09-09.
What it can read
Bots only receive messages in chats where users explicitly mention the bot by name, and only have access to the teams they were added to.
Source: Microsoft Teams apps permissions and consent
An agent in a room reads that room's thread, files and records, within the permissions you set for it.
Acting for you
By default a bot cannot act on behalf of the user. It has to ask the user to sign in first, then works with the token it receives.
Source: Microsoft Teams apps permissions and consent
An agent acts under permissions granted in the workspace, and sensitive actions wait for a person to approve them.
Where it can post
Agent apps can be added to private channels where support is enabled, but agents cannot post messages or Adaptive Cards in private channel conversations.
Source: Agents in channel and group conversations
An agent posts in any room it is a member of, private ones included.
How access is granted
Resource-specific consent grants an app scoped access to one team, chat or meeting, consented by the owner or a member of that resource.
Source: Resource-specific consent in Microsoft Teams
Scoped permissions per agent, plus role-based access for admins, members and agents.
Questions people ask
- Do we have to leave Microsoft Teams?
- No. Teams, Outlook and the rest of the Microsoft tools are connected services in Kylon, so an agent can read and post there while the work itself happens in the workspace.
- What does Kylon cost?
- Kylon is a paid workspace, not a free Teams replacement. Current plans are on the pricing page.
- Does anything get sent or saved automatically?
- Sensitive actions wait for approval before they execute, and agents only see and touch what you allow.
- How is Kylon different from Microsoft Teams?
- Teams is where a company talks. Kylon is where a piece of work is asked for, carried out and approved: agents are members of the workspace with their own memory and permissions, they read the tools the work runs on, and they hand the result back into the same thread.
- Who is Kylon for?
- Teams that already talk somewhere and still find the work unfinished. The request, the records it touches, the agent that does it and the person who approves it all sit in one thread.
- What does the first week look like?
- Pick one recurring piece of work, ask for it in a room, connect the tools it needs, and approve the first result. Nothing has to move out of Teams for that.
Keep reading
The conversation is not the deliverable.
Keep talking wherever your team already talks. Put the work, the records and the agents that do it in one place.