Microsoft Teams integration

If Microsoft Teams is where your team already lives, SIMRelay drops in directly. Incoming SMS appears as adaptive cards in the Teams channels you choose, with the original sender, message body, and timestamp preserved.

Setup

Microsoft Teams supports Incoming Webhooks at the channel level. Open the channel you want SIMRelay to post into, add an Incoming Webhook connector, copy the URL, and paste it into the SIMRelay dashboard for the relevant hosted number. Test from the dashboard before relying on it.

Channel routing

Each hosted number can be mapped to one or more Teams channels. A common setup: production 2FA codes go into a private "ops-secrets" channel that only admins can see; less-sensitive shared-number SMS goes into a wider "shared-inbox" channel.

What's in the card

The adaptive card includes the sender's phone number, the message body, the SIMRelay number it was sent to, the timestamp, and a deep link back to the message in the SIMRelay dashboard. The dashboard link is the audit trail — Teams won't keep the message forever.

Permission model

SIMRelay's permission model is independent of Teams'. You decide which teammates have which roles in SIMRelay; Teams decides who can see which channel. The two layers compound: a SIMRelay teammate without channel access in Teams won't see the cards there, even though they could see the message in SIMRelay's own dashboard.

Limitations

Microsoft's Incoming Webhook connector doesn't support inbound messages (Teams → SIMRelay). If you need bi-directional integration (replying to an SMS by typing in Teams), that's a feature we're tracking but it requires the Microsoft Bot Framework rather than Incoming Webhooks.