Microsoft Teams

A Microsoft Teams integration connects your company's Microsoft 365 tenant to Mobius through the Mobius bot. When an assistant has something for someone, such as a routine result, an approval waiting on them, or a question, the bot sends that person a direct message in Teams with a link back to it in Mobius.

Picture a routine that reads the team's to-do table at 8am and writes up the day's action items. The person who follows it doesn't have to be signed in to Mobius to find out. A chat from the bot shows up in Teams, its pop-up shows the title, and Open in Mobius takes them straight to the result.

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.

Today the bot sends notifications. It doesn't pass replies on to assistants, so people answer an approval or a question by opening the link.

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.

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. Ask us for it. If you offer Mobius to your own clients under your brand, ask 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 get notifications.
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. Open the link in a browser where you're signed in to Mobius as an organization administrator.
4. 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.

Linking the tenant doesn't necessarily connect your own Teams account. If your Teams sign-in name is the email you use for Mobius, it does. If not, the same page shows the Teams account the link came from and lets you choose to connect it. That choice is off until you turn it on.

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, choose to connect it, and confirm.

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

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.

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 the whole organization: open Build > Integrations > Microsoft Teams and disconnect the tenant. Mobius stops sending notifications to it and 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.

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.

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.

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. Messaging the bot again unblocks it for Mobius.

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 stores those as events and ignores everything else.

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

• 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.