Notices in Microsoft Teams
Fortis connects Varqeni to a Teams channel of your choice with an incoming webhook during setup.
How it works
- Incident cards name the cause, the confidence, the incident id and where the evidence is stored.
- Autopilot cards say Autopilot resolved, Autopilot action did not recover, Autopilot refused, nothing sent or Needs a person.
- Downstream reader cards name the reader group and say Varqeni reports this and does not restart readers.
- Pipeline watch cards say a watch started, that drift was seen, or that it closed with its verdict.
- Data check cards say whether rows were lost or duplicated. An automatic check is posted only when rows were lost or duplicated.
- When the person on call is paged, a Resolved card follows when the system recovers. Without paging, recoveries are not posted, except when a downstream reader catches up.
What you should see: Cards are coloured by how much they need you: green when nothing is wrong or a fix worked.
What it can and cannot do
Can
- Post a card for each new incident, each autopilot outcome and each downstream reader that stops or recovers.
Cannot
- Answer questions from Teams yet, or let someone off the on-call rota act from a card.
Pages
With the Varqeni app in your team, a page arrives as a card from Varqeni that mentions the person on call and carries Acknowledge, Approve the recommended fix (with a Yes, run confirm step on the card), Page the next person, More (Decline, Resolve by hand) and Open in console. Teams tells Varqeni who pressed a button; that person must be on the on-call rota, and only approvers can approve. Everything that follows, including the outcome of a fix, is posted in the card's thread. Tested live in the Fortis lab on 20 October 2026: a page acknowledged from Teams, and a fix approved from Teams that ran and was verified in about 5 seconds.
Choose the channel
Someone on the on-call rota writes @Varqeni use this channel in the channel where pages should go. Without the app, pages go to the channel's webhook with an Open in console link.
If it does not work
- Not getting cards? See No cards in Teams.
Related articles
- What you are told, and whenVarqeni tells a person once per incident, every autopilot outcome, and nothing for a single bad check.
- Paging and escalationVarqeni pages the person on call only when it cannot settle an incident itself, and escalates when nobody answers.
- Microsoft TeamsVarqeni posts notices to a Teams channel, and pages you can acknowledge or approve from the card.
- A downstream reader stopped or is falling behindVarqeni tells you when something that reads your change data from Kafka stops or keeps falling behind. It does not restart readers.
Still stuck? Contact support or email info@fortisdatagroup.com.