Microsoft Teams notifications setup

Overview

SprintBee doesn't ship a Teams bot for notifications. Instead, a room moderator creates a Power Automate Workflow in their own Microsoft 365 tenant and pastes its webhook URL into the room's Notifications settings — the same paste-a-URL pattern as the Slack webhook, just with a Teams-flavored URL and message format.

Once configured, the window lifecycle posts an Adaptive Card to that Workflow for three events: the voting window opening, the window closing soon (with a count of participants who still haven't voted), and the window closing (with a split of auto-accepted vs. needs-discussion items).

Slack and Teams webhooks are independent settings on the same room — you can configure one, both, or neither.

This integration is available on Pro plans. Free plans don't see a working notifications section in room settings.

Why a Workflow instead of a Teams app

Microsoft retired Office 365 Connector incoming webhooks in 2026. The supported replacement is a Power Automate "Workflows" webhook that you create yourself, inside your own tenant — there's no app installation, tenant-admin consent, or Microsoft Entra registration required.

The tradeoff is that messages arrive from the generic "Flow bot" identity rather than from a branded "SprintBee" app, and the card has no interactive buttons. In exchange, setup takes a couple of minutes and needs no IT approval beyond whatever your org already requires for Power Automate.

Create the workflow from Teams

The quickest path starts right in the channel you want notified — do this once per channel.

1. In Teams, hover over the target channel and click the ⋯ (More options) menu, then choose Workflows.
2. Pick the "Send webhook alerts to a channel" template.
3. The team and channel are pre-filled from where you launched it — confirm them, sign in or approve the connection if prompted, then name the flow and click Create.
4. Teams shows the workflow's webhook URL as soon as setup finishes — copy it now. If you miss it, you can find the same URL later in Power Automate under the flow's trigger step.

Alternative: from the Power Automate portal

Some tenants hide the Workflows app in Teams. If you don't see it, create the same flow from make.powerautomate.com instead:

• Go to make.powerautomate.com and click "Create" → "Instant cloud flow".
• Search for "webhook" and choose the "Send webhook alerts to a channel" template (trigger: "When a Teams webhook request is received").
• Pick the team and channel you want voting-window notifications posted to.
• Save the flow. Open the trigger step and copy its "HTTP POST URL" — this is the webhook URL SprintBee will post to.

Connect it to a SprintBee room

Notifications are configured per room, alongside the Slack webhook.

1. Open the room, go to Settings → Notifications.
2. Under "Microsoft Teams", paste the webhook URL you copied and click Save. The URL is encrypted at rest and never shown again in full.
3. Click "Send test message" to confirm the Workflow accepts the card — you should see a message from "Flow bot" appear in the chosen channel within a few seconds.
4. Repeat for Slack if you also want notifications there; the two are independent.

Troubleshooting

Most setup problems fall into a few known categories:

• "Enter a Power Automate Workflows webhook URL" — the pasted URL isn't a recognized Workflows host. It must be an https:// URL under logic.azure.com or api.powerplatform.com; a plain Teams channel link or an old Office 365 Connector URL won't work.
• "Recent notifications may be failing to deliver" warning — SprintBee tracks consecutive failed sends per provider and surfaces this after three in a row fail. This usually means the Workflow was deleted, turned off, or the URL was regenerated. Recreate the flow (from Teams or the portal) and paste the new URL.
• No message appears after "Send test message" succeeds — check that the flow itself is turned on in Power Automate (flows can be individually disabled) and that the channel you selected still exists.
• Messages stopped after working before — Power Automate Workflow URLs can be regenerated or the flow can be deleted by anyone with edit access to it; recreate the flow and update the URL in room settings if that happens.

FAQ

Who do messages come from? The generic "Flow bot" identity, not a branded SprintBee app — this is a Microsoft limitation of the Workflows webhook path, not a SprintBee choice.

Can I use the same Workflow for multiple rooms? Yes — paste the same URL into as many rooms as you want posting to that channel.

Does this support interactive buttons (accept/dismiss from the card)? No. The card is read-only; act on it by opening the room link it includes.

Can I disconnect it? Yes — click "Turn off" under Microsoft Teams in the room's Notifications settings. This only removes SprintBee's stored URL; the Power Automate Workflow itself still exists until you delete it separately.

Is this the same as the Teams Meeting App? No — this is a one-way notification webhook. It's unrelated to any in-meeting Teams app.

Do I need a paid Microsoft 365 plan or Teams Premium? No — any Microsoft 365 plan that includes Teams works, including Business Basic. Teams Premium isn't required.

Does the "webhook request received" trigger need a premium Power Automate license? No — it's a standard connector included in the Power Automate rights seeded with Microsoft 365, not a premium connector.

Does everyone in the channel need Power Automate access? No — only the person who creates the Workflow needs it. Everyone else just sees the channel messages once it's posting.

Can our IT department block this? Yes — tenant admins can disable the Workflows app in Teams as a policy setting. That's an admin choice, not a licensing restriction; ask your admin to re-enable it if it's missing from the ⋯ menu.