Microsoft Teams

A Microsoft Teams integration connects your company's Microsoft 365 tenant to Mobius through the Mobius bot. People talk to your organization's assistant in Teams: in a 1:1 chat with the bot, or with an @mention of the bot in a group chat or a channel. The bot also sends each person their Mobius notifications, such as a routine result, an approval waiting on them, or a question, with a link back to it in Mobius.

Picture an operations lead at Northwind who wants to know which vendor contract renews next. She asks the bot in Teams and gets the answer in the same chat, with no browser tab to open. At 8am the next day, a routine writes up the day's action items from the team's to-do table. A chat from the bot shows up in Teams, and Open in Mobius takes her straight to the result. Teams controls whether a desktop or phone notification appears.

The bot joins Teams like another member of the team. It only receives messages sent to it: a 1:1 chat with the bot, or an @mention of it. Mobius asks for no Microsoft Graph permissions and no admin consent for Teams.

People answer an approval or a question from a notification by opening the link. The bot doesn't take those answers in Teams. An @mention of the bot in a channel or group chat can also start a routine, which then runs and replies inside that chat. A 1:1 chat with the bot never starts one. See Events.

Note: Teams is enabled per organization; ask Mobius support to turn it on. Until it is on, Microsoft Teams doesn't appear in your integrations or in Settings > Notifications.

Capability map

Before you start

Setting up Teams takes two people, who can be the same person:

• A Teams administrator for your Microsoft 365 tenant, who uploads the Mobius app and installs it for people. If a service provider runs your Microsoft 365 tenant, they usually do this part.
• An organization administrator in Mobius, who is also a regular member (not a guest) of the Microsoft 365 tenant, to link the tenant.

You also need the Mobius Teams app package, a .zip file. In Mobius, go to Build > Integrations > Microsoft Teams, open How linking works, and click Download app package. Anyone in your organization can download it and send it to your Teams administrator. If you offer Mobius to your own clients under your brand, ask us for a package with your name and icon on the bot.

Teams in Microsoft's government clouds (GCC, GCC High, and DoD) is not supported.

Set up Teams for your organization

The Teams admin steps happen in the Teams admin center (admin.teams.microsoft.com).

1. In the Teams admin center, open Teams apps > Manage apps, click Actions > Org-wide app settings, and under Custom apps turn on Let users install and use available apps by default and Let users interact with custom apps in preview.
2. On Manage apps, click Upload new app and choose the Mobius package. It needs no approval, and it shows up under Built for your org within a few hours.
3. Open the Mobius app, go to Users and groups > Availability, and choose everyone or the users and groups who should use the app.
4. On the same tab, open Installs and install the app for those users or groups. This is what lets the bot message someone first. It can take up to 24 hours to reach everyone.
5. Add the app to one team that everyone is in, such as an all-company team. Mobius reads that team's member list to find people who have never messaged the bot. This step is optional, and we recommend it.

Now link the tenant to your Mobius organization:

1. In Teams, open a 1:1 chat with the Mobius bot and send link.
2. The bot replies with a link. It works once, for the next 15 minutes.
3. Ask Mobius support to approve the Microsoft tenant ID for your Mobius organization. Your Teams administrator can confirm that ID.
4. Open the link in a browser where you're signed in to Mobius as an organization administrator. Your Teams sign-in name does not have to match your Mobius sign-in email.
5. Check the Microsoft tenant it shows, then confirm.

The bot replies in Teams with "Linked to" and your organization's name. Mobius can now send notifications to people in your tenant. To let people talk to an assistant in Teams, choose the assistant that answers.

Linking the tenant connects you to the Teams account that sent link only when its sign-in name matches your Mobius sign-in email. Otherwise, the page asks what that Teams account does for you, and connects nothing unless you choose: it gets your notifications only, or it also acts as you in private conversations with a team assistant. Choose either only if the account is yours. The same applies when an organization admin refreshes an existing tenant link.

link only works in a 1:1 chat. In a channel or group chat, the bot asks you to message it directly. If the link won't open, the bot's reply also includes a code you can paste on the Microsoft Teams page in Build > Integrations.

Each Microsoft 365 tenant can be linked to one Mobius organization. To move a tenant to a different organization, disconnect it in the first one.

How people are matched

Mobius matches a person's Teams account to their Mobius account when their Teams sign-in name, or their Teams email address on the same domain, is the email they sign in to Mobius with. For most companies that's everyone, with no action from anyone. Mobius finds people as they message the bot, from the member list of a team the app is in, and by looking up the address when it first has something to send them.

A few accounts are never matched automatically:

• Guests in your tenant.
• A Teams account that is already matched to someone else. Mobius never moves it to another person.
• An address that belongs to more than one member of your Mobius organization.

If you aren't matched, connect your Teams account yourself:

1. In Teams, open a 1:1 chat with the Mobius bot and send link.
2. Open the link while you're signed in to Mobius.
3. Check that the Teams account it shows is yours. If its address isn't the email you use for Mobius, choose what it does for you: Notifications only, or It acts as me in private conversations. Then confirm.
4. The bot replies in Teams with what the link did.

Connecting your own account only needs a regular Mobius membership, and it only works once your organization has linked the tenant.

Talk to your assistant in Teams

Once Teams is linked to Mobius, people can ask your organization's assistant questions in Teams, where they already work. An assistant is an AI helper with saved instructions and tools; the Mobius app calls it an agent. The assistant answers in the same chat, and it remembers what was already said there. See agent messaging for how this works across Slack, Telegram, email, and Teams.

One assistant answers in your Teams organization. Teams gives each person exactly one 1:1 chat with the bot, so there is one place to ask and one assistant that answers there.

Use your own accounts privately

In your 1:1 chat, a team assistant can use your own accounts that you have given it access to. The assistant knows it's you when your Teams sign-in address is the email you use for Mobius, or when you connected that Teams account and chose that it acts as you in private conversations. You must still be allowed to use that assistant. A Teams account you connected for notifications only can't act as you; the assistant replies there with how to link. Your chat and the facts the assistant remembers for you stay private to you. Other people use the same assistant with their own accounts and their own memory.

When the assistant needs an account you have not connected:

1. Open the setup link it sends in your Teams chat. Sign in to Mobius as the same person, in the same organization.
2. Choose one of your existing accounts or connect a new account. The page gives the assistant private access to that account.
3. Wait for the page to confirm the saved account and assistant access.
4. Return to the same Teams chat and send your request again. Connecting an account never runs the earlier request automatically.

You do not need permission to edit the assistant to grant your own account. If it lacks the service's tools, an organization administrator must add those first. You can manage connected accounts in Build > Integrations.

Setup links expire after 15 minutes and work only for the person and organization they were issued for. Ask the assistant for a new link if one expires. Cancelling or closing setup does not run your request; any account already saved remains in your account settings.

Use your 1:1 chat for your own mail, files, and remembered facts. Channels and group chats never use your own accounts or your memory. See Privacy in Teams.

Choose the assistant that answers

An organization administrator chooses the assistant, because the Teams connection belongs to the whole organization. Linking Teams ends on this choice; to make it later:

1. Open Build > Integrations and open the Microsoft Teams account.
2. Under Who answers, click Choose agent, or Change if one already answers.
3. Pick the assistant and click Save.

Only assistants shared with everyone in your organization are listed, because everyone in your Teams organization can message the one that answers. If the one you want is missing, share it with everyone from its page first, then choose it.

The assistant you choose can also use the Teams actions, such as posting to a channel. When you choose a different assistant, the previous one loses that access, unless you granted it under Who can use its actions yourself.

Send the bot a message in a 1:1 chat to check: the assistant's answer arrives in the same chat. It answers anyone who messages the bot directly, and anyone who @mentions the bot in a channel or group chat. Teams sends the bot only the channel messages that @mention it.

To stop the assistant from answering in Teams, click Change and choose No agent. No assistant answers until an administrator chooses one again. Notifications continue to arrive.

Where people ask

• In a 1:1 chat with the bot, people send a message. No @mention is necessary.
• In a group chat or a channel, add the Mobius app to the team or the group chat first. Teams sends a message to a bot only when the bot is in that conversation. Then @mention the app in every message, including each reply in a thread. Teams does not send the bot a message that has no @mention, so the assistant never sees it.

Each 1:1 chat, each group chat, and each channel thread is one ongoing conversation. A new top-level post in a channel starts a new conversation, and the assistant answers in that post's thread.

Privacy in Teams

What you say to the assistant in a Teams chat stays in that chat. Privacy in chat apps explains the whole model. What is specific to Teams:

• Your 1:1 chat with the bot is yours. The assistant works for you there, as it does in a private conversation in Mobius. You can read the chat in Mobius: open the assistant and choose Sessions. See agent sessions. Nobody else can open it, organization admins included. What the assistant remembers there goes to your own memory, and files it saves are yours. Sharing the assistant with other people does not share your chat, your own accounts, or your memory.
• Channels and group chats belong to the chat. Read them in Teams. Nobody opens them in Mobius, organization admins included. What the assistant remembers or saves there stays in that chat. The assistant uses company accounts there, never your own accounts.
• No Teams chat is public. Teams has no channel that Mobius can confirm is open to everyone, so nothing said in Teams adds to what the assistant knows everywhere.
• Guests get a notice. The assistant doesn't answer a guest of your tenant, in a chat or a 1:1 chat. It posts one notice instead. After a guest posts in a channel or group chat, the assistant stays quiet there.

Your Teams chat account appears under My chat links in Account settings, and administrators see it under the connection's Chat links. It has no Revoke control: your company directory manages it. Access ends when you leave the organization or lose access to the assistant.

Teams shows the installed bot's name and icon as the sender. Each assistant reply also identifies the answering assistant inside the message. A long answer arrives in ordered parts, each with the assistant's name. System notices and direct message-post actions do not invent an assistant identity.

Notifications and the assistant share one chat

Your 1:1 chat with the bot is the chat where your notifications arrive, and the chat where you talk to the assistant. The two stay separate. The assistant does not see your notifications, so your notifications never become part of what a team assistant knows.

This has two results:

• If you reply to a notification, the assistant gets your reply as a new message, without the notification. Ask a complete question.
• Replying "approve" or "yes" to an approval does nothing to the approval. Click Open in Mobius and answer it there.

If no assistant answers direct messages in your Teams organization, a message to the bot gets this reply, at most once a day for each chat:

No agent answers messages in this chat yet. Notifications will keep arriving here.

It means one of these:

• No assistant is chosen under Who answers on the Teams account.
• The chosen assistant is Disabled.

Your notifications are not affected.

Words the bot keeps for itself

A message that is only link or only help goes to the bot, not to the assistant. link starts the linking steps above, and help explains what the bot does. To ask the assistant about either word, write a full sentence.

Send one message at a time

A message you send while the assistant is still answering in the same chat gets no reply. Teams shows no sign that the assistant is working yet. Wait for the answer, then send that message again. This is a known limit, and we plan to show when the assistant is working.

Choose where notifications go

Each person chooses in Settings > Notifications. Notifications in the Mobius app are always on. Teams and email can each be on, off, or follow your organization's default, which an organization administrator sets on the same page. If Teams can't reach you yet, the Teams row says why: your organization hasn't connected Teams, you aren't matched to a Teams account, or you blocked the bot. Your choice still saves, and applies once Teams can reach you. The same page shows your recent Teams delivery outcomes and a Send test button. A test checks your own connection even if you turned routine notifications off. You can send one test per minute. Sent means the Teams service accepted the message; check the Teams client separately for the message and any desktop or phone alert.

Mobius sends a Teams message when:

• a routine you follow produces a result, or only when it fails if you follow it for failures only. See routines.
• an approval is waiting on you, or an assistant asks you a question. See interactions.

Each message has a title, a short summary, and an Open in Mobius link. If Teams can't reach someone, they still see the notification in Mobius, and by email if they have email on.

Stop notifications

• For yourself: turn Teams off in Settings > Notifications. Blocking the bot in Teams also stops them. After you unblock it, they start again when you message the bot, or within a day.
• For everyone who hasn't chosen: an organization administrator turns Teams off under Organization default in Settings > Notifications. Teams stays connected, and anyone who turned Teams on for themselves still gets notifications there.
• For the whole organization: open Build > Integrations > Microsoft Teams and disconnect the tenant. Mobius stops sending notifications to it, the assistant stops answering there, and Mobius forgets who is who in it.

Note: Disconnecting in Mobius doesn't remove the app from Teams. The bot stays installed and answers that it isn't linked. To remove it entirely, a Teams administrator removes the Mobius app in the Teams admin center.

Actions

microsoft_teams.message.post

Use microsoft_teams.message.post to post a Markdown message into a channel, group chat, or 1:1 chat that the Mobius app is in, for example a routine's daily summary in a team channel. It needs a grant on the Teams connection, like any other action.

• conversation_id names the chat or channel. A channel ID looks like 19:…@thread.tacv2; the channel's Get link to channel URL contains it, and the action accepts it as it appears there.
• The app must have seen the chat or channel first: someone messaged or @mentioned it there, or the app was added there. Otherwise the action refuses with "The Teams app has not seen that conversation." @mention the app there once, then try again. Mobius never posts into a chat that a verified Teams message has not shown it, so an assistant cannot post into another organization's Teams.
• In a channel, leave thread_id empty to start a new post. Set it to a post's ID to reply in that post's thread. The result gives the new post's thread_id.
• A post is not repeated automatically. If the result says the message may have posted, check the chat before you post it again.

A routine started from a Teams message does not need this action: its result goes back to the chat or thread it came from.

Events

microsoft_teams.app.installed
microsoft_teams.app.uninstalled
microsoft_teams.message.received

A routine can start from one of these events. The bot only receives messages sent to it, so microsoft_teams.message.received covers 1:1 chats with the bot and messages that @mention it. Where the message was sent decides where its event goes:

• A channel or group chat reaches only routines whose condition names that chat (meta.conversation_id == "19:...@thread.v2"). A run it starts belongs to that chat: it runs in the chat's own conversation, uses only company accounts, and posts its result in the chat and thread that started it, not to the routine's saved destination. Besides that reply, it can't change anything in another system. The run doesn't appear in the routine's runs or counts for anyone, its owner included, and nobody gets a notification about it.
• A 1:1 chat with the bot reaches nothing outside your conversation with the assistant. It never starts or feeds a routine.

microsoft_teams.app.installed and microsoft_teams.app.uninstalled follow the same rule, by the chat or team the app was added to or removed from.

No Teams event reaches an assistant waiting for an event or a session that subscribes to events, and the integration events list shows a Teams message's provider, type, time, and status, not its text. See Privacy in chat apps.

A routine can also follow Teams conversations:

• Each thread or chat keeps one routine conversation for each channel thread, and one for each group chat.
• Each channel or chat keeps one routine conversation for each channel or group chat. Adding or removing the app in a team joins the team's General channel conversation, not the other channels.

Troubleshooting

The bot says the organization isn't linked to Mobius yet

Nobody has linked your tenant, or it was disconnected. Follow the linking steps in Set up Teams for your organization.

The bot asks you to message it directly

You sent link in a channel or a group chat. Open a 1:1 chat with the bot and send link there.

"This Microsoft Teams organization is already linked to another Mobius organization"

Another Mobius organization holds this tenant. It stays linked there until that organization disconnects it, even if its link stopped working. Disconnect it there first, or contact us.

"The link has expired" or "The link has already been used"

Links work once, for 15 minutes. Send link to the bot again for a new one.

"Mobius support must approve this Teams tenant"

Ask support to approve the tenant ID for your Mobius organization. Your Teams administrator can confirm the ID. A link cannot claim a new tenant until that approval is recorded.

Your message got no answer

Try these in order:

1. If the assistant was still answering an earlier message in the same chat, wait for that answer. Then send your message again.
2. In a channel or group chat, @mention the app in the message. In a thread, every reply needs its own @mention.
3. In a channel or group chat, make sure the Mobius app is in that team or group chat. If it isn't, add it.
4. If the bot replied "No agent answers messages in this chat yet." earlier today, it doesn't send that line again until a day has passed. No assistant answers your direct messages yet.
5. If the bot replied "I don't work in conversations that include people outside your organization." in this chat, a guest posted here, or Mobius couldn't check who is in the chat. The assistant stays quiet. See Privacy in Teams.

If none of these explain it, ask your Mobius administrator to check who answers in Teams.

The assistant doesn't answer someone (for administrators)

Open the Microsoft Teams account under Build > Integrations and check these in order:

1. Who answers names an assistant. If it says no agent answers yet, follow Choose the assistant that answers.
2. That assistant is not Disabled, and is still shared with everyone in your organization.
3. In a channel or group chat, the person @mentioned the app, and the Mobius app is in that team or group chat.

"Mobius could not run this agent turn" or "could not finish this agent turn"

The assistant could not answer the message. When Mobius knows the reason, such as used-up platform credits or an ended trial, the reply says so. Otherwise, for your 1:1 chat, open the assistant in Mobius and choose Sessions to see what happened. A channel or group chat can't be opened in Mobius. Then send the message again.

Replying to an approval did nothing

A reply in Teams doesn't reach the approval. Click Open in Mobius on the notification and answer there.

Someone isn't getting Teams notifications

Check these in order:

1. The app is installed for them. Installs from the Teams admin center can take up to 24 hours.
2. Their accounts are matched. If their Teams sign-in name isn't their Mobius email, they connect their account themselves, as in How people are matched.
3. Teams is on for them in Settings > Notifications.
4. They haven't blocked the bot in Teams. After they unblock it, messaging the bot starts notifications again at once; otherwise they start within a day.

The Mobius app doesn't appear in Teams

Check that custom apps are turned on in Org-wide app settings, that the app's Availability includes the person, and that a few hours have passed since the upload.

FAQ

Can the bot read our team's conversations? No. Teams only delivers messages sent to the bot: 1:1 chats with it and @mentions of it. Mobius ignores everything else. The assistant sees only those messages, not the rest of the channel or chat, and what it hears stays in the chat where it was said. See Privacy in Teams.

Can two assistants answer in one Teams organization? No. Each person has one 1:1 chat with the bot, so one assistant answers there and in every channel and group chat. Give that assistant the instructions and tools it needs for everyone who asks it.

How do code and links look in a Teams answer? Short ordinary answers stay as chat text. Structured answers use cards with distinct headings, nested lists, and literal monospace code. Tables appear as labeled rows so their values remain readable on a narrow screen. Images appear as descriptive links. Long code and table values continue in order across messages.

Cards may appear as “Sent a card” in Teams notification previews. Routine notifications keep their short text and Open in Mobius link.

Can I change the sender name? Assistant attribution comes from the assistant's name in Mobius. The installed sender belongs to the bot's Azure Bot profile. Package branding and that profile are separate settings; changing the package name alone does not guarantee a changed sender label. Mobius does not change the bot profile for each answer.

Does Mobius need our Microsoft 365 administrator to approve permissions? Not for Teams. The app package asks for no Graph permissions. Uploading and installing the app is the approval. The other Microsoft integrations (mail, calendar, and files) do need consent.

Can several brands' packages be installed in one tenant? No. Install one Mobius package per tenant. Two packages that share the Mobius bot confuse Teams.

Next

• See how people talk to assistants everywhere with agent messaging.
• Connect mail, calendar, and files with Microsoft integrations.
• Schedule work that people get notified about with routines.
• Ask people for approvals and answers with interactions.
• See what stays in each chat in Privacy in chat apps.