Skip to content

Microsoft Teams integration

EvenTier posts request updates to a Microsoft Teams channel, either as Adaptive Cards through a Teams Workflows webhook or as threaded messages through Microsoft Graph. With Graph, replies in a request's thread are also added to the request as public comments.

Set up in
Admin → Settings → Integrations → Chat notifications
Who can set it up
People with the Manage integrations permission

Adaptive Cards through a Workflows webhook

The simplest setup needs only the URL of a Teams workflow. Pick which events to post: new requests, updates, resolutions and approval decisions. Each one is posted as an Adaptive Card with the request number and title, a summary of the change, the request's details and an Open request button.

  • Limit a destination to some teams, request types or priorities
  • Add an intro or footer line with placeholders such as {{requestNumber}} and {{requestUrl}}

One thread per request through Microsoft Graph

With an app registration connected, EvenTier posts through Microsoft Graph instead of the webhook. The first message about a request starts a thread in the channel, and later updates are posted as replies to it.

Teams replies added to the request

With Graph connected, EvenTier subscribes to change notifications for the channel and renews the subscription before it expires. A reply in a request's thread is added to the request as a public comment. It is posted as the EvenTier user who wrote it, with that user's own permissions.

  • Each notification is checked against the subscription ID and a secret client state
  • Only replies in the configured channel are read. New top-level posts and messages from apps are ignored
  • Senders are matched by the Teams user ID set in Admin → Users, or by email through Microsoft Graph
  • A reply is not added if its sender cannot be matched or cannot comment on the request. People with the Manage integrations permission get an alert, at most once a day

Confidential requests stay out of Teams

Nothing about a confidential request is posted, because everyone in the channel would see it. The check runs when each message is sent, so a request made confidential after an update was queued is left out too.

Profile photos from Entra ID

When a reply arrives, EvenTier reads the sender's Entra ID photo through the integration's app registration and imports it in the background, at most once a day. It never replaces a photo the member uploaded, or one from directory sync, SCIM or single sign-on (SSO).

  • Needs the User.Read.All application permission, which also lets EvenTier match senders by email

Set up Microsoft Teams

  1. 01

    Create a Teams workflow

    Open the channel in Teams, choose Workflows and pick the "Send webhook alerts to a channel" template. Its trigger is When a Teams webhook request is received. Save the workflow and copy the URL it gives you.

    Where:
    Microsoft Teams: the target channel → Workflows
  2. 02

    Add a Teams destination

    Choose Microsoft Teams, name the destination, paste the workflow URL and pick the events to post. To limit it to some teams, request types or priorities, open Show routing and templates.

    Where:
    Admin → Settings → Integrations → Chat notifications → Add chat destination
    Permission:
    Manage integrations
  3. 03

    Or connect through Microsoft Graph

    For threads and reply sync, fill in all five Microsoft fields: tenant ID, client ID, client secret, Teams team ID and Teams channel ID. A destination uses either the webhook URL or the full Graph configuration. When you save, EvenTier creates the change-notification subscription, and Microsoft Graph checks the Teams events URL shown on the destination.

  4. 04

    Send a test message

    Send a test message from the saved destination to check that it posts to the channel.

  5. 05

    Link people to their Teams accounts

    Set each person's Teams user ID in Admin → Users. It is their object ID in Entra. If the app registration has User.Read.All, a sender is also linked automatically when their Entra email or user principal name matches their EvenTier email.

    Where:
    Admin → Users
    Permission:
    Manage users

Data flow

Updates go from EvenTier to the channel. With Graph connected, Microsoft Graph tells EvenTier about new replies, and EvenTier reads each one. The webhook URL and client secret are stored encrypted.

Sent to Teams

  • The request number, title and a link to the request
  • A summary of the change and who made it, and for approvals, the decision
  • Status, priority, request type, team, requester and assignee
  • Your intro and footer templates, filled in

Read from Microsoft Graph

  • Notifications of new replies in the configured channel
  • The text of each reply and its sender
  • The sender's email address and Entra ID photo, with User.Read.All

Never sent

  • Anything about a confidential request
  • Comments and internal notes from the request

Questions about Microsoft Teams

Do I need Microsoft Graph credentials?
Only for threads and reply sync. A Teams Workflows webhook URL is enough to post Adaptive Card alerts to a channel.
Do legacy incoming webhook URLs still work?
Yes, until Microsoft retires them. For a new destination, create a workflow from the "Send webhook alerts to a channel" template and use its URL.
What happens to a reply from someone EvenTier cannot match?
It is not added to the request. The people who manage integrations get an alert that explains how to link the account, and the sender can then post again.
Are confidential requests posted to Teams?
No, because everyone in the channel would see it. The people who can open a confidential request still get email and in-app notifications about it.

Get notified when signup opens.

EvenTier is in private early access. Leave your work email and we will let you know when you can create a workspace.

No card. We use your email only for your early-access invite and launch news. Privacy Policy