Integration guide
Microsoft Teams
Review a pricing digest in the agreed team.
Teams reporting needs configured delivery transport and a real pilot test in your team. This page does not connect an account or send a card. Confirm the owner, permissions and a real acceptance test before relying on a connection.
Start with a retail decision
Choose the review
Prepare a reviewed pricing digest as an Adaptive Card for the agreed team.
Make the evidence comparable
Verify recipient permissions, card size and a real delivery with the configured transport.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
Output scope to review: Reviewed Adaptive Card for an approved team/channel
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Tenant · team/channel · approved destination · report type · reviewed card content | Deliver an agreed output | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
Teams reporting needs configured delivery transport and a real pilot test in your team. This page does not connect an account or send a card.
Do not send passwords, API keys or customer records through the contact form.