How to Add an AI Employee to Microsoft Teams

Key Takeaways

• Viktor works natively in Microsoft Teams. Not a Slack product with a Teams afterthought: you install the app, open a chat, and delegate work the same way a Slack team does.
• Install is a normal Teams app install. Find Viktor in the Teams app store and add him. If your organization restricts app installs, your IT admin approves him once in the Teams admin center.
• The interaction model is chat, not a dashboard. You message Viktor in a 1:1 chat or @mention him where you work. Tasks, follow-ups, and deliverables all happen in the conversation.
• Everything an AI employee does elsewhere applies in Teams. Connected tools with real read and write access, scheduled recurring work, and finished deliverables like PDFs, spreadsheets, and presentations.
• Keep one chat per task, not one endless thread. Starting a fresh conversation for each new piece of work keeps context clean and responses sharp.
• Review-first still applies. Sensitive actions like outbound email start as drafts you approve inside Teams, so delegation never means losing control.

Your company runs on Teams. Most AI employees don't.

For the last two years, almost everything interesting in the "AI that does real work" category shipped Slack-first. Great if you are a startup on Slack. Useless if you are one of the hundreds of thousands of businesses whose entire day, including every meeting, every chat, every file, happens inside Microsoft Teams.

That gap is why the most common question we heard from Teams-based companies was some version of "when can we have this?". The answer is now: Viktor runs natively in Microsoft Teams. This guide covers how to set him up, what changes compared to a generic chatbot, and the handful of Teams-specific habits that make the difference between a demo and a working AI employee.

What "AI employee in Teams" actually means

An AI employee is not a chat window that answers questions. It is a teammate you delegate work to inside the chat tool you already use. In Teams, that looks like this: you open a chat with Viktor, write what you need the way you would brief a colleague, and he goes off and does it, using the tools you have connected.

Pull last week's deals from HubSpot, compare them against the pipeline
snapshot you made last Monday, and send me a one-page PDF summary
before my 3pm review.

The work happens in the conversation. Viktor asks clarifying questions if the brief is ambiguous, shows drafts for anything sensitive, and delivers finished files back into the chat. There is no separate app to check, which is precisely the point of putting an AI employee where your team already spends the day. We wrote up the reasoning in why your AI employee should live where you work; the short version is that context, delegation, and accountability all live in chat, so that is where the AI belongs.

Setting up Viktor in Microsoft Teams

Setup is a standard Teams app install, with one branch depending on how your organization manages apps.

Step 1: Install the app

Find Viktor in the Microsoft Teams app store and add him. He appears in your sidebar like any other chat. If you can install apps freely in your organization, this takes about a minute.

Step 2: If your organization gates apps, loop in IT once

Many companies, sensibly, require admin approval for new Teams apps. Your IT admin approves Viktor in the Teams admin center under Manage apps, and can choose whether Viktor is available for people to add themselves or installed for a wider group directly. This is a one-time step per organization, and it is the same governance path IT already uses for every other Teams app.

Step 3: Say hello and connect your first tool

Open a chat with Viktor and describe what you want help with. Connecting tools happens conversationally: ask him to connect your CRM or your email, and he sends you a secure authorization link for that tool. With 3,200+ integrations available, the practical question is not "is my tool supported" but "which two tools should I connect first". Start with the ones your most annoying weekly task lives in.

Step 4: Give him a real task, not a test question

"What can you do?" produces a brochure. "Build me a spreadsheet of all invoices from June, flag anything overdue, and set up the same report every Monday at 8am" produces evidence. AI employees are judged fairly only on delegated work.

Teams-specific habits worth knowing

Teams and Slack differ in small mechanical ways, and two habits matter more in Teams than anywhere else.

Start a new chat per task. In Teams it is tempting to keep one conversation running for weeks. Resist it. A fresh conversation per task keeps the context focused on the work at hand and keeps responses fast and precise. Think of it like giving a colleague one brief per project instead of a single years-long email thread.

Use group chats and channels for shared work. Viktor participates where he is added, so a group chat with your sales team plus Viktor turns "someone should pull those numbers" into an @mention. Work that the whole team should see belongs in shared surfaces; personal drafting belongs in your 1:1 chat.

One more practical note: your usage and settings are available on the web at app.viktor.com, where Teams users sign in with the same Microsoft account they use in Teams.

How this differs from Copilot and generic Teams bots

Microsoft's own AI story in Teams is real and improving, so the honest comparison is not "Viktor versus nothing". It is about what kind of thing you are adopting.

The distinction that matters for a 10-50 person company: Copilot's agent platform rewards organizations with the IT capacity to build and govern agents. An AI employee rewards teams that just want to hand work to someone today. Both are legitimate; they solve for different buyers. For the head-to-head, see Viktor vs Microsoft Copilot.

What Teams-based companies actually delegate first

The pattern from Teams-native businesses, which skew toward professional services like accounting, construction, healthcare, and consulting, is strikingly consistent. First delegations are almost always one of these:

• Recurring reports. "Every Monday morning, pull the numbers and post the summary." Scheduled work is the fastest habit to form because it shows up without being asked.
• Document production. Proposals, client summaries, and internal one-pagers built from data in connected tools, delivered as finished files in chat.
• CRM hygiene. Updating records, chasing stale deals, and summarizing pipeline changes, because nobody ever became a partner by doing data entry.
• Email drafting with review. Viktor drafts, you approve, it sends. The review-first flow means the first week of trust-building costs nothing.

Notice what is not on the list: nobody's first delegation is "answer questions about AI". The value shows up when a task you dreaded stops being yours.

Frequently Asked Questions

Is Viktor actually native in Microsoft Teams, or a mirrored Slack bot?

Native. Viktor runs directly in Microsoft Teams, and Teams workspaces are full workspaces, not satellites of a Slack installation. Day to day, delegating work in Teams feels the same as it does in Slack.

What does IT need to approve?

Viktor is a published, validated app in the Teams app store. If your organization restricts app installs, an admin approves Viktor once in the Teams admin center under Manage apps and decides who can add him. There is no infrastructure to host and no custom app package to sideload.

How does Viktor connect to our other tools from Teams?

Conversationally. Ask him to connect a tool and he sends a secure authorization link where you grant access, typically through that tool's own sign-in. Access can be revoked at the tool's side at any time, and how to connect any tool to your AI employee walks through the details.

Can Viktor do scheduled work in Teams?

Yes. Recurring tasks like a Monday-morning pipeline summary or a daily support digest are one of the most common first uses. You describe the schedule in plain language once, and the work shows up on time after that.

Does the whole company see what I ask Viktor in a 1:1 chat?

No. Your 1:1 chat with Viktor is between you and him, the same way a private conversation with a colleague would be. Shared visibility happens where you choose it, in group chats and channels.

My chat with Viktor got slow after weeks of use. What happened?

Very long single conversations accumulate context that stops helping and starts weighing things down. Start a new chat for new work. One conversation per task is the habit that keeps a Teams-based AI employee sharp.

We have some people on Slack and some on Teams. Which do we pick?

Pick where the team actually talks. Viktor works in both, and the capability set is the same. The AI employee should follow your communication culture, not dictate it.

The gap is closed

For a long time, running your company on Microsoft Teams meant reading about AI employees instead of hiring one. That excuse is gone. Install Viktor from the Teams app store, or forward this post to whoever owns your Teams admin center, and give him one real task this week.

Add Viktor to Microsoft Teams and delegate your first task

Related reading:

• Viktor vs Microsoft Copilot
• Why Your AI Employee Should Live Where You Work
• How to Connect Any Tool to Your AI Employee