# Microsoft Teams and Outlook

Connect Teams and Outlook so your apps and <Term id="agent">agents</Term> work where your Microsoft 365 users already are.

- **Microsoft Teams** posts results, summaries and alerts to your Teams channels, without anyone opening Klarety.
- **Outlook** reads mail and calendars, sends reports from your own account, and lets an agent work through the inbox it is given.

Both are under **Productivity** and connected by your <Term id="studio">Studio</Term>'s AI with a Microsoft 365 sign-in.

## Before you start [#before-you-start]

- A <Term id="project">project</Term>. Its Studio's AI does the work. See [Create a project](/docs/projects/create-a-project).
- A Microsoft 365 account with access to the Teams channel or the mailbox you want to use. A shared mailbox or team account keeps work out of personal inboxes.
- If the sign-in says administrator approval is needed, ask your Microsoft 365 administrator, or use your own app (see below).

## Connect it [#connect-it]

<Steps>
<Step>
### Open Microsoft Teams [#open-microsoft-teams]
Go to <AppLink to="connectors" />, search for **Microsoft Teams** and open it.
</Step>
<Step>
### Send the request to a project's AI [#send-the-request-to-a-projects-ai]
Under **Connect it with your Studio's AI**, choose the **Project** that should use Microsoft Teams. **What the AI is asked** starts as "Connect Microsoft Teams to this project so it can post results and alerts to Teams channels." Edit it to say exactly what you want, for example: "Post the daily sales summary to the Sales channel in the Commercial team every morning at 9:00". Then select **Send to AI**.

The AI starts at once if the Studio is open, or when it next opens. Select **Open Studio** to go there.

<Screenshot src="/docs/_media/connect-data-with-ai-in-dashboard-data-page.png" alt="Connecting Microsoft Teams with a project's AI from the Connectors page" />
</Step>
<Step>
### Finish the connection [#finish-the-connection]
The AI drafts the connection and never asks for a key in the chat. The draft shows as **Waiting for you**. Select **Connect** to open the **Connect Microsoft Teams** dialog.

Choose the sign-in button for Microsoft. The dialog shows the only site this sign-in is used with. Sign in with the Microsoft 365 account that has the access you need and approve what Microsoft asks for. The connection then shows **Signed in as** your account.
</Step>
<Step>
### Choose what the AI may do [#choose-what-the-ai-may-do]
Under **What the AI may do with it**, choose **Can read** (nothing there changes) or **Can read and change** (the AI may also add, change and remove things). Then select **Connect**.

<Screenshot src="/docs/_media/slack-connector-how-to-connect-in-ui.png" alt="The Connect Microsoft Teams dialog with the access choice" />
</Step>
<Step>
### Test it and tell the AI [#test-it-and-tell-the-ai]
The dialog says **Microsoft Teams is connected**. Select **Test it**, then **Tell the AI** so it carries on.
</Step>
</Steps>

You can also start inside a project: in **Settings**, **Keys**, describe it in **What do you want to connect?** and select **Ask AI to connect**.

For Outlook, open **Outlook** instead and follow the same steps. For example: "Read new mail in the invoices mailbox and add each invoice to the invoices table."

<Callout type="info" title="Posting and sending need change access">
  Posting to a channel or sending mail needs **Can read and change**. Reading mail and calendars needs only **Can read**.
</Callout>

## What you get [#what-you-get]

- **Results where people work.** An agent can end its run by posting to a Teams channel: a summary, a table of exceptions, or an alert when a number crosses a line. See [What agents do](/docs/agents).
- **Mail as data.** Outlook emails can become rows in a <Term id="nexus">Nexus</Term> table you query in the <AppLink to="data.sql" />.
- **Calendar-aware work.** An agent can read events and free time before it plans or writes a brief.

## Test, pause and reconnect [#test-pause-and-reconnect]

A project's connections are listed in its **Settings**, under **Keys**, with their status.

<Screenshot src="/docs/_media/manage-connections-by-toggle-on-off-per-project.png" alt="A project's connections in Settings, Keys" />

| Status | What it means |
| --- | --- |
| **Waiting for you** | Drafted by the AI. Select **Connect** to finish it. |
| **Works** | Connected and usable by the project. |
| **Needs reconnecting** | The key or sign-in stopped working. Select **Reconnect**. |
| **Paused** | Nobody can use it until you select **Resume**. |

From the same row: **Test**, **Pause**, **Turn off here** (this project stops using it) or **Remove** (deletes the key, and every Studio using it stops reaching Teams or Outlook).

A connection belongs to the project it was made in. Owners and admins see all of them under **Your connections** on <AppLink to="connectors" />. It stays off for other projects until an admin switches it on under **Projects that may use** it.

## If the test fails [#if-the-test-fails]

**Test** reports one of these:

- It works: the project reached the service.
- The key was rejected: select **Reconnect** and enter a new one.
- The service cannot be reached: check that it is up and accepts outside connections, then test again.
- Internet is off: the project's internet is **Off**. Turn it on in its **Settings**. With **Only allowed**, the Studio reaches only its connections and the sites you add.
- It is not connected yet: select **Connect**.

Specific to Microsoft 365:

- **Limited: permissions were not granted.** Some actions will fail. Select **Reconnect** and approve everything the job needs.
- **Was signed in as an account. Sign in again to keep using it.** A password change or an expired grant ended it. Select **Reconnect**.
- **Nothing appears in the channel.** Check the account you signed in with is a member of that team and can post in the channel, and that the connection has **Can read and change**.

## Use your own sign-in app [#use-your-own-sign-in-app]

If your organization only allows sign-ins through its own registered app, choose **Use your own app instead** in the connect dialog. Register an app with the provider, add the **Return address for your app** Klarety shows, then paste its **Client id** and **Client secret** and select **Save your app**. The secret is sealed and never shown again.

## Where your key goes [#where-your-key-goes]

The key or sign-in is encrypted with a managed key service the moment you select **Connect**, and not even the AI can read it. The Studio never holds the key. If the one site it is sent to is not the service's own address, Klarety warns you and asks you to type the site to confirm.

## Next steps [#next-steps]

- [OneDrive and SharePoint](/docs/connectors/onedrive-sharepoint)
- [What agents do](/docs/agents)
- [How connectors work](/docs/connectors)