> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/getting-started/chatops/microsoft-teams/operational-guidance.md).

# Microsoft Teams Operational Guidance

Day-to-day guidance for running the Arnica Microsoft Teams integration

## Alerts are not arriving after the integration is connected

Connecting Microsoft Teams creates the delivery channel. Arnica sends alerts only when a policy rule tells it to.

1. Confirm that a [secrets detection](/arnica-documentation/hardcoded-secrets/secrets-policy-settings.md) or [code risks policy](/arnica-documentation/code-risks/code-risk-policy-settings.md) includes a notification action.
2. Confirm that the configured recipients are correct.
3. Confirm that the Arnica bot has been added to the target channel.

## A user has the app installed but is missing from the recipient list

Arnica's recipient list is built from Teams users it has already seen, so an installed app is not sufficient on its own.

1. Confirm that a Global Administrator completed [Authorizing Arnica for your organization](/arnica-documentation/getting-started/chatops/microsoft-teams.md#step-2-authorizing-arnica-for-your-organization). Without that consent, Arnica cannot resolve users through Microsoft Graph.
2. Ask the user to open the Arnica app in Teams and send the bot any message. The user appears in the recipient list once Arnica has seen that message.
3. Confirm that the user is a member of the Microsoft tenant. Guest and external accounts without a Microsoft user principal name cannot receive Arnica notifications — route those findings to a channel that includes them instead.

## A channel is missing from the recipient list

Arnica records a channel only after it knows the team that contains it.

1. Add Arnica to the **team** first, as described in [Adding Arnica to a Team or Channel](/arnica-documentation/getting-started/chatops/microsoft-teams/adding-arnica-to-a-team-or-channel.md).
2. Post a message mentioning `@Arnica` in the channel.
3. Re-open the recipient list. The channel is listed as `<team name>/<channel name>`.

To notify a whole team rather than one channel, select the team. Arnica posts to that team's **General** channel.

## Arnica declines a channel invitation

Adding the Arnica bot to public channels may result in Arnica declining the invitation. If Arnica does not post a "Get Started" message in the chat, try inviting the bot to a private team.

## Direct messages are not delivered

1. If your Arnica tenant is hosted in the European Union, confirm that your organization installed the **Arnica EU** app rather than **Arnica**. See [Which Arnica Teams App to install](/arnica-documentation/getting-started/chatops/microsoft-teams.md#which-arnica-teams-app-to-install).
2. Ask the affected users to send the Arnica bot a message once. For Microsoft tenants served from regions outside the Americas, Arnica may not be able to resolve a user by email address alone. Once Arnica has seen a message from the user, it delivers direct messages through the conversation it captured, independent of region.

## The app did not appear for users

A Teams setup policy can take Microsoft up to several days to apply across an organization. Users who need Arnica sooner can install it themselves from the Microsoft Teams Store.

## The Connect with Arnica button does not complete the connection

The connection link is single-use and expires after one day. Send the Arnica bot another message to generate a new welcome card, then select **Connect with Arnica** again.

If the browser opens to a sign-in page for the wrong Arnica environment, confirm which region hosts your tenant — `app.arnica.io` or `app.eu.arnica.io` — and sign in there.

## Removed channels and uninstalled apps are still listed

Deleting a Teams channel or uninstalling the Arnica app does not remove the destinations Arnica saved. Remove the Microsoft Teams integration on the [Integrations page](https://app.arnica.io/#/admin/integrations) to clear the integration record and every Teams contact Arnica saved for that Microsoft tenant. The integration can then be connected again from Teams.

## The integration cannot be edited

The Microsoft Teams integration is removable but not editable. To change the connected Microsoft tenant, remove the integration and complete [Connecting your Arnica tenant](/arnica-documentation/getting-started/chatops/microsoft-teams.md#step-3-connecting-your-arnica-tenant) again.

## Reducing notification volume

If developers receive too many low-priority alerts, tighten the policy conditions:

* Add a severity threshold (for example, High and above).
* Scope rules by repository, product, or finding type.
* Route informational alerts to a shared channel instead of direct messages.

## Related topics

* [Microsoft Teams integration overview](/arnica-documentation/getting-started/chatops/microsoft-teams.md)
* [Adding Arnica to a Team or Channel](/arnica-documentation/getting-started/chatops/microsoft-teams/adding-arnica-to-a-team-or-channel.md)
* [Interacting With the Arnica Teams Bot](/arnica-documentation/getting-started/chatops/microsoft-teams/interacting-with-the-arnica-teams-bot.md)