Microsoft Teams app

The Claresia Teams app is the end-user surface for Microsoft Teams. It renders Claresia skill responses as Adaptive Cards inside Teams chat and channels, with the standard Hub deep-link footer.

Install

The app is published to the Teams Admin Center App Catalog under Claresia · Agent Operations Platform.

To install for your tenant:

Open Teams Admin Center → Teams apps → Manage apps
Search for “Claresia”
Click Allow to enable for your tenant
(Optional) Set up an App Setup Policy to pin Claresia in the Teams left rail for specific user cohorts (e.g., your pilot users)

Permissions requested

Permission	Why
`User.Read`	Read the user’s profile to map to archetype
`Files.Read.Selected`	Allow the user to attach a file as a skill parameter (per-file consent)
`ChannelMessage.Send`	Post Claresia skill responses to channels (where invoked)
`Bot:` access to Bot Service	Backend chat bot for skill invocation

Claresia uses least-privilege — no Directory.Read.All, no Sites.Read.All, no Mail.*. The app does not crawl your Teams content.

Skill invocation patterns

`@Claresia` mention in a chat

User types @Claresia and picks a skill from the autocomplete:

@Claresia /pipeline-hygiene

The bot prompts for parameters (Adaptive Card form), runs the skill, posts the response back as an Adaptive Card with the standard footer.

Action button on a channel message

Right-click a message → More actions → Claresia → [skill]. The skill runs with the message body as context. Useful for boss.standup-notes (run on a team’s daily standup channel).

Tab-mode (channel tab)

Add a “Claresia” tab to a channel (e.g., a team’s #sales-pipeline channel). The tab opens the per-team Claresia view: pipeline hygiene, latest deal summaries, team-aggregated maturity bar.

Personal app

Each user gets a personal Claresia app in their left rail. Shows their personal skill picker, recent invocations, and maturity progress bar.

Adaptive Card shape (per skill response)

{
  "type": "AdaptiveCard",
  "version": "1.5",
  "body": [
    {
      "type": "TextBlock",
      "text": "Incident Postmortem — INC-2026-04-1873",
      "size": "Large",
      "weight": "Bolder"
    },
    {
      "type": "TextBlock",
      "text": "...skill output body in markdown...",
      "wrap": true
    },
    {
      "type": "FactSet",
      "facts": [
        { "title": "Cost", "value": "$0.04" },
        { "title": "Latency", "value": "2.3 s" },
        { "title": "Tokens", "value": "4,823 in / 1,421 out" }
      ]
    }
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "View record",
      "url": "https://hub.dainese.claresia.com/records/rec_abc123"
    },
    {
      "type": "Action.Submit",
      "title": "Re-run with different incident",
      "data": { "intent": "rerun", "skill_id": "gatespic.incident-postmortem" }
    }
  ]
}

See Adaptive Cards reference for the full schema.

Authentication

The Teams app uses Single Sign-On via Entra ID:

The Teams client passes the Entra access token to the Claresia bot
Claresia exchanges it for a tenant-scoped JWT (no separate login required)
All skill invocations carry the user’s user_id for telemetry + audit

If your tenant requires MFA on Claresia sign-in, the user is prompted once per session via Entra Conditional Access; subsequent invocations within the session window run silently.

Mode C considerations

In Mode C (BYOC):

The Teams app is still installed from the Microsoft App Catalog (the bot is hosted by Claresia)
The Hub emission flow runs in your Power Platform environment and writes to your customer-cloud Hub
Telemetry envelopes (skill_id, ts, success, latency, tokens, cost) reach Claresia Cloud; no payload data leaves customer cloud

Manifests + branding

App manifest source: Claresia - Roadmap/cc-067-teams-app/manifest/teams-app-manifest.json
Icons (color + outline): Claresia - Roadmap/cc-067-teams-app/manifest/

For per-tenant white-labeling (e.g., a customer that wants the bot to appear as “Dainese AI Assistant” in Teams), see Command Center → Surfaces → Teams → Branding. Requires the Microsoft 365 Developer License (Teams Custom Branding).

Common gotchas

Symptom	Cause	Fix
`@Claresia` doesn’t autocomplete	App not installed for the user	Teams Admin Center → assign app to user / cohort
Skill invocation hangs	Bot Service throttled	Wait 30s; if persistent, check `status.claresia.com`
Adaptive Card renders blank	Card schema version mismatch (Teams client < 1.5)	Update Teams client; or report to CSM
User sees skills they shouldn’t	Cached old archetype mapping	Run Republish in Command Center → Distribution → Microsoft