> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/workflows/creating-workflows/configuring-connector-thinklet/microsoft-teams-connector-thinklet.md).

# Microsoft Teams connector thinklet

Configure Microsoft Teams connector thinklets to take specific actions within your workflow.

{% hint style="info" %}
Refer to the [Permissions](https://learn.microsoft.com/en-us/graph/api/presence-get?view=graph-rest-1.0\&tabs=http#permissions) section in the Microsoft documentation to view the required authorizations.
{% endhint %}

## Action: Get user MS Teams status <a href="#microsoftoutlookconnectorthinklet-action-sendanemailtoonerecipient" id="microsoftoutlookconnectorthinklet-action-sendanemailtoonerecipient"></a>

**Get user MS Teams status** retrieves user availability and activity statuses in MS Teams.

The Microsoft Teams connector thinklet relies on the [Get presence](https://learn.microsoft.com/en-us/graph/api/presence-get?view=graph-rest-1.0\&tabs=http#permissions) API endpoint provided by Microsoft Graph.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-fc536f96b3a42009454d83801e5b564c6cfdda7f%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* **Parameters:** Configure the data used as parameters for this action. Hover over the tooltip icon for more information on how the system maps the parameter and what data is required.
  * **User UUID**: UUID of the Entra ID user whose MS Teams status you want to retrieve.
* **Outputs**
  * **User availability status (**`UserAvailability`**)**: Basic presence information for the user—Available, Busy, Away, and more.
  * **User activity status (**`UserActivity`**):** Additional information about the availability of a user—InACall, Presenting, OutOfOffice, and more.

{% hint style="info" %}
If an invalid user UUID has been supplied or the user no longer exists in the Entra ID, both outputs return `PresenceUnknown`.

When using this connector in a workflow, add a condition branch to verify that the output is not`PresenceUnknown`. This ensures that the system has successfully retrieved the MS Teams presence status.
{% endhint %}

The table below shows the API Service connector details needed when recreating the connector:

<table><thead><tr><th width="272">Field</th><th>Value</th><th data-hidden></th></tr></thead><tbody><tr><td>Resource Path</td><td><code>/users/{{userUuid}}/presence</code></td><td></td></tr><tr><td>Method</td><td>GET</td><td></td></tr><tr><td>Payload</td><td></td><td></td></tr><tr><td>Outputs</td><td><p><code>UserAvctivity $.activity</code></p><p><code>UserAvailability $.availability</code></p></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/user-guide/workflows/creating-workflows/configuring-connector-thinklet/microsoft-teams-connector-thinklet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.