Microsoft Teams

The Microsoft Teams notifications integration posts build and release events to a Teams channel. When a build completes on merge, a build fails, or a release is deployed, codev sends an Adaptive Card to the channel behind a Teams incoming webhook — with the repository, commit, release candidates, work items, and a button linking back to the run.

You configure it under Settings > Organization > Integrations > Microsoft Teams. Only organization owners can manage it.

What gets posted

codev sends a card for three events:

Event	When it fires	Card
Build succeeded	A build completes after a merge	Commit, release candidates, work items, View build
Build failed	A build fails	The same fields, View failed build
Release deployed	A release finishes deploying	Release name, environment, domain, status, View release

The Notify on setting controls which of these are delivered:

• All builds & releases — every event above.
• Failures only — only failed builds. Successful builds and successful deployments are skipped.

A build event posted to the configured Teams channel — the card carries the commit, work items, and a link back to the run.

A failed build posts the same fields with a View failed build action.

Create the incoming webhook in Microsoft Teams

Teams receives external webhooks through a channel Workflows automation. Creating one takes a minute and does not require admin rights on the team:

1. In Microsoft Teams, open the channel the notifications should post to, click the channel's ⋯ (More options) menu and choose Workflows.
2. Search the templates for webhook and pick Send webhook alerts to a channel.

The channel's Workflows dialog — search for webhook and choose Send webhook alerts to a channel.

1. The team and channel are pre-selected from where you opened the dialog. Confirm them and click Save.

The template's parameters — the team and channel the webhook posts to.

1. On the created workflow's page, click Copy webhook link. This is the URL codev posts to (https://….logic.azure.com/… or https://….powerplatform.com/…).

The created workflow — Copy webhook link yields the webhook URL to paste into codev.

The webhook URL is a channel-posting credential — anyone holding it can post cards to that channel. codev stores it encrypted in the integrations credential store; it is never written into project configuration or returned by project reads.

Classic Office 365 connector webhooks (https://….webhook.office.com/…) also work, but Microsoft is retiring connectors in favor of Workflows. New setups should use the Workflows path above.

Configure the integration in codev

1. Go to Settings > Organization > Integrations and open the Microsoft Teams tile.
2. Paste the Webhook URL. It must be an https:// URL.
3. Leave Enable notifications on, and pick a Notify on mode — All builds & releases or Failures only.
4. Under Availability, select Specific project and choose the project. Notification settings are per project, so a project must be selected.
5. Click Add Integration.

Saving stores the webhook URL as an encrypted credential and writes the enable flag and mode to the selected project's configuration (notifications.teams).

The Teams integration form — webhook URL, enable toggle, notify-on mode, and the project the settings apply to.

Changing the mode later

The enable flag and mode live in the project's configuration under notifications.teams:

{
  "notifications": {
    "teams": {
      "enabled": true,
      "mode": "failures"
    }
  }
}

Edit them from the project's Update Project dialog (the configuration editor), or re-add the integration with the new mode. Setting enabled to false stops deliveries without removing the stored webhook credential.

Troubleshooting

• No cards arrive — check that the project's configuration has notifications.teams.enabled: true and that the integration is scoped to that project. In Failures only mode, successful builds and deployments are skipped by design.
• The workflow was deleted or turned off in Teams — the webhook URL stops accepting posts. Recreate the workflow, copy the new link, and re-add the integration; the old credential is replaced.
• The workflow's run history shows failures — open the workflow in Teams (channel ⋯ > Workflows) and check its Run history; a failed run means Teams received the post but could not deliver the card.

SlackIntegrations