Connecting Microsoft Teams to Landfall

Microsoft Teams is a channel Landfall posts incident updates to, through a webhook a Teams workflow gives you. Landfall never reads your Teams messages.

• As a channel: an update a person approves in Landfall posts into one Teams channel. Takes the workflow's webhook URL, which is itself the credential.

What you'll need

• Permission to add a workflow to the Teams channel that should receive updates.
• An admin on your Landfall organization, to save the connection under Integrations.
• A personal Landfall API key. Turning on real egress and sending an update to Teams have no screen yet, so both go through the API.

1. Create a webhook workflow in Teams

1. Channel → More options (...) → Workflows → Send webhook alerts to a channel

   Microsoft is retiring the older Incoming Webhook connectors, so use the Workflows app. Pick the template, name the workflow Landfall, choose the team and channel, and save it.

2. Copy the webhook URL

   After the workflow is created, Teams shows its webhook link. Copy it. Anyone holding the URL can post to the channel, so keep it like a password.

2. Add it to Landfall

1. Integrations → Chat → Microsoft Teams

   Open Integrations in the left menu and select the Microsoft Teams tile under Chat. Paste the link into Incoming webhook URL. The field is a secret: Landfall never shows it back.

   app.landfalls.ai · Integrations · Microsoft Teams

   

2. Test connection

   A Teams webhook has no read or ping call, so the test posts a real message to the channel: Landfall connected ✓ (health check). A working URL shows ✓ connected and the line posted a test message to the Teams webhook.

3. Save integration

   The URL goes to Landfall's secrets backend. The panel and the Microsoft Teams tile read Configured.

4. Turn on real egress (API only)

   Real egress is off for every organization by default, and until it is on an approved update is recorded in the room and not delivered. The test message above is the one exception. An admin turns egress on with a personal API key from Your settings → API keys. The switch covers every chat connection in the organization, and the change is audited.

   TerminalCopy

   curl -X PUT https://api.landfalls.ai/o/<your-org>/oncall/egress \
     -H "Authorization: Bearer lf_key_…" \
     -H "Content-Type: application/json" \
     -d '{"enabled": true}'

5. Send an update to Teams (API only)

   The incident's Comms tab drafts to #incidents, which is a Slack channel. An update for Teams is drafted to the channel teams through the comms API, then approved and sent by a person. The draft call returns the messageId and version the next two calls need.

   TerminalCopy

   BASE=https://api.landfalls.ai/o/<your-org>/incidents/<incident-id>/comms/messages
   
   curl -X POST $BASE -H "Authorization: Bearer lf_key_…" \
     -H "Content-Type: application/json" \
     -d '{"channel": "teams", "body": "Checkout errors are back to normal."}'
   
   curl -X POST $BASE/<messageId>/approve -H "Authorization: Bearer lf_key_…" \
     -H "Content-Type: application/json" -d '{"version": "<version>"}'
   
   curl -X POST $BASE/<messageId>/send -H "Authorization: Bearer lf_key_…"

What it looks like

Each update arrives in the channel as an Adaptive Card holding the update's text. A Teams webhook cannot edit a message it posted, so every update is a new card, and any action in an update is written out as text for the reader to act on in the war room.

What Beacon can read

Not applicable. The connection only sends, so Teams is not in the signal catalog and Beacon and joined agents cannot query it. See Integrations architecture for the sources that are.

Opening incidents from Teams

Not applicable. A Teams webhook has no path back to Landfall, so a Teams message cannot open an incident. A chat message can open a room from Buzz, and alerts open rooms through the Triggering integrations pages, such as Alertmanager.

Troubleshooting

Reference

See Integrations architecture for how every Landfall integration shares this connector shape.