Send updates to Microsoft Teams

SprintBee has no Teams app to install. Microsoft retired Office 365 Connector webhooks in 2026, and the supported replacement is a Power Automate Workflows webhook that you create yourself, inside your own tenant. You build one Workflow for the channel you want notified, then paste its URL into your Workspace's settings. No Entra registration, no tenant-admin consent, no app store.

Before you start#

You need four things:

• A paid plan. Channel notifications are included on Pro, Pro Plus and Pro Ultra. On Free the Notifications panel appears but has nothing to configure.
• Owner or Admin of the organization that owns the Workspace. Members without a management role cannot open these settings.
• Permission to create a flow. Any Microsoft 365 plan that includes Teams is enough — the "webhook request received" trigger is a standard connector, so neither Teams Premium nor a premium Power Automate licence is required. Only the person creating the Workflow needs access; everyone else just reads the channel.
• The channel you want the messages posted in.

Create the Workflow in Teams#

The quickest path starts in the channel itself. Do this once per channel.

1. In Teams, hover over the target channel, open the ⋯ (More options) menu, and 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, name the flow, and select Create.
4. Copy the webhook URL shown when setup finishes.

If you close that dialog before copying, the same URL is still available: open the flow in Power Automate and expand its trigger step.

Create it from Power Automate instead#

Some tenants hide the Workflows entry in Teams. The same flow can be built from the portal:

1. Sign in to make.powerautomate.com and choose Create → Instant cloud flow.
2. Search for webhook and pick the Send webhook alerts to a channel template — its trigger is When a Teams webhook request is received.
3. Choose the team and channel that should receive the messages.
4. Save the flow, open the trigger step, and copy its HTTP POST URL.

Add the webhook to your Workspace#

1. Open Workspaces and select the Workspace.
2. In the Settings group of the sidebar, choose Integrations & notifications.
3. Under Notifications, find the Microsoft Teams card and paste the URL into Webhook URL.
4. Select Save, then Send test message. A card from Flow bot should appear in the channel within a few seconds.

The URL is encrypted at rest and never shown again — the field stays empty afterwards, and typing a new URL replaces the stored one. SprintBee accepts only an https:// address on a logic.azure.com or api.powerplatform.com host; a channel link or an old Connector URL is rejected before it is saved.

What SprintBee posts#

Messages arrive as Adaptive Cards from the generic Flow bot identity rather than a branded SprintBee sender, and they carry no interactive buttons. That is the trade for a setup with no app installation: act on a card by following the room link it includes.

Event	The card says
Async voting window opened	How many items are ready, and when voting closes
Voting closes soon	How many participants still have not voted
Reminder sent	A moderator nudged the people who have not voted, or a scheduled escalation fired
Voting window closed	How many items were auto-accepted, and how many need discussion
Estimate recorded	The item, its result, and the value written to the backlog
Retro summary ready	Topics discussed or parked, and Improvement Actions committed

Estimate-recorded cards are off until you turn them on: once a webhook is saved, tick Estimate recorded on the Microsoft Teams card. It fires far more often than the window events, so it is opt-in per provider. Retro summaries post when a facilitator closes a Retro and includes the channel in its delivery.

When messages stop arriving#

What you see	What it means
Enter a Power Automate Workflows webhook URL	The pasted address is not on a recognised Workflows host. Copy the trigger's HTTP POST URL again rather than a channel link.
The webhook URL must use https	Workflows URLs are always https://. Check for a truncated paste.
Recent notifications may be failing to deliver	Three sends in a row failed. Usually the flow was deleted, switched off, or its URL regenerated. Recreate it and paste the new URL.
Test message reports success, nothing appears	The flow is turned off in Power Automate, or the channel it targets no longer exists.
Cards arrived for weeks and then stopped	Anyone with edit access can regenerate the URL or delete the flow. Rebuild it and save the new URL.

Saving a webhook clears the failure counter, so the warning disappears on the next load once delivery recovers.

Turn Teams notifications off#

Select Turn off on the Microsoft Teams card. That removes SprintBee's stored URL and stops every event above; the Slack setting is untouched.

The Power Automate Workflow itself keeps existing until you delete it in your own tenant. Leaving it in place is fine — nothing posts to it — and it means reconnecting later is one paste rather than a rebuild.