Integrations: Microsoft Teams

Post event activity to a Microsoft Teams channel as it happens — registrations created, updated and cancelled, and invitations created, sent and updated.

Teams is one of the activity-notification channels alongside Slack and email. All three share the same triggers, the same bulk-operation coalescing and the same burst digesting, so a channel's volume behaves the same way whichever you use.

Overview

When something happens in your event, getregistered posts an Adaptive Card to the Teams channel you configured:

A registration is created, updated or cancelled.
An invitation is created, sent or updated.

You choose which of those six triggers a channel receives. A single event can have several Teams integrations pointing at different channels with different triggers.

Prerequisites

The organisation-level Teams feature flag must be on. It is off by default and is set by getregistered support on the organisation record — ask your account contact to enable Teams Integration for your organisation. Until it is on, you will be unable to use this feature.

Creating the webhook in Teams

Microsoft has deprecated the old Office 365 connectors. New setups use a Teams Workflow (Power Automate) with an HTTP trigger. Existing connector URLs continue to work — see Existing Office 365 connectors below.

In Teams, open the channel you want notifications in.
Select the … menu next to the channel name, then Workflows.
Search for and choose the template Send to webhook alerts to a channel.
Confirm the Teams account it will run as, then select Next.
Confirm the Team and Channel the workflow posts to, then select Add workflow.
Teams shows an option to Copy webhook link at the top of the window. Copy it now.

The workflow posts as the account that created it. If that person leaves the organisation, the workflow — and so the notifications — can stop. Create it from a shared or service account where you can.

Connecting to your Teams channel in getregistered

Navigate to your event in getregistered admin.
Go to Integrations > Microsoft Teams.
Select New Teams Integration.
Fill in:
1. Webhook URL: The URL copied from the Teams workflow.
2. Channel Name: The name of the channel in your Teams workspace.
3. Notification Triggers: Which activity this channel receives (Registration Created, Invitation Sent etc).
Select Save Teams Integration.

The webhook URL is stored encrypted and is never displayed again after saving. To change it, edit the integration and paste a new one.

Accepted webhook URLs

*.environment.api.powerplatform.com - Power Automate / Workflows | Current, use this for new setups

*.logic.azure.com - Power Automate / Workflows | Current, use this for new setups

*.webhook.office.com - Office 365 connector | Accepted, but deprecated by Microsoft

Any other host is rejected with a validation error when you save.

Existing Office 365 connectors

If you already have a `webhook.office.com` connector URL it will keep working and getregistered still accepts it. Microsoft is retiring connectors, so move to a Workflow when convenient: create the workflow as above and paste the new URL over the old one on the same integration. No other change is needed.

Notification Triggers

Registration Created | Someone registers for the event
Registration Updated | A registration changes (including a name or email edit)
Registration Cancelled | A registration is cancelled
Invitation Created | An invitation is created
Invitation Sent | An invitation is sent or resent
Invitation Updated | An invitation changes other than being sent

At least one trigger is required.

Volume controls

Teams channels get the same protections as Slack, so a busy event does not flood the channel:

Bulk operations post one summary: A bulk confirm of 100 registrations posts a single "100 registrations confirmed" card, not 100 cards.
Organic bursts are digested: If many registrations arrive at once outside a bulk operation — an import, or a rush when registration opens — the first few post individually and the rest collapse into one summary once the burst settles.
Matching track/admission type configurations: Activity can be limited to specific track or admission types to reduce noise in your Teams channels.

Troubleshooting

The Microsoft Teams tile is available, but the configuration page is unavailable -

The organisation-level Teams feature flag is off. Ask your account contact to enable it.

"must be a valid Teams webhook URL" -

The URL is not a valid Teams webhook. Check you copied the whole URL from the workflow's HTTP trigger.

Nothing arrives in the channel -

Check, in order:

The organisation flag is on
The integration lists the trigger you expect
The workflow still exists in Teams and its owning account is still active. A workflow whose creator has left the organisation stops running.

Fewer messages than expected -

Expected, if the activity came from a bulk operation or an organic burst — see Volume controls. Look for a summary card instead.