Microsoft Teams

Send vendor status updates to the IT channel responsible for your business tools. Statusfield uses a Teams incoming webhook; your organization must allow the required workflow. Check pricing for channel availability and integration limits.

Create a Teams destination

1. Open Workflows in Teams and choose a template that posts webhook alerts to a channel.
2. Select the team and channel that should receive vendor updates.
3. Use a webhook that accepts external requests without Microsoft user authentication. Statusfield sends to the signed URL and does not sign in to your tenant.
4. Save the workflow and copy its webhook URL. Treat the URL as a secret: anyone with a usable URL can send requests to it.

Microsoft's incoming webhook instructions cover the current template names and setup screens. Tenant policies can limit the available options.

Connect it to Statusfield

1. Open Integrations and choose Microsoft Teams.
2. Add an integration, give it a recognizable name such as “IT vendor alerts,” and paste the webhook URL.
3. Create the integration. Open its menu and use Test.
4. Confirm the labeled test appears in the intended Teams channel.

The current connector accepts HTTPS webhook URLs on *.logic.azure.com and *.webhook.office.com. If Microsoft supplies a different host, the connector will reject it; do not rewrite the URL to bypass validation. Use another supported alert destination while requesting support for that URL format. Existing legacy URLs are subject to Microsoft's connector lifecycle; use Workflows for new setup.

Assign vendor alerts

Open Notifications, select the relevant monitors, and assign the Teams destination and severity filters. Choose provider components where available. Test delivery before relying on the channel during an incident.

For example, route collaboration-tool updates to the help desk channel. Share a separate status board with staff who only need to check reported status. A Teams integration and a staff board are configured separately; creating either does not automatically subscribe everyone to notifications.

If something fails

• Workflows unavailable: ask your Microsoft 365 administrator whether your account and tenant allow them.
• URL rejected: check that the complete, unmodified HTTPS URL uses a supported host.
• Request unauthorized: check the workflow's authentication setting; a workflow requiring a Microsoft user token cannot accept this connector's request.
• Test sent but no message visible: inspect the workflow's run history, its Teams connection, and the chosen channel. Fix any failed action, then retry the test.
• Test works but no incidents arrive: check active monitoring, plan entitlement, selected components, destination and severity rules. A matching vendor status change may not have occurred.

An incoming webhook request is only part of the delivery path. Confirm the message in Teams. A labeled test is delivery evidence, not a real outage. Keep an alternative communication channel for incidents affecting Teams itself.

Continue with the IT workflow or quickstart.