Bring Fronterio to where your team already works

Most enterprise AI failures happen because the platform you're trying to drive adoption with isn't where your team works. They use Teams. They use Copilot. They use Outlook. The last thing they want is yet another browser tab. The Fronterio Teams Agent solves this by bringing the AI Consultant + governance workflows directly into Microsoft Teams as a chat bot.

From Teams, your team can ask any question the AI Consultant would normally answer in the dashboard — 'how do we register a new agent?', 'what's the EU AI Act risk classification for our new chatbot?', 'draft a Transparency Notice for our customer support agent'. The bot answers in-context, with the same evidence-grounded responses, the same citations to your audit log, the same partner-consultant escalation cards.

Beyond chat, the bot supports proactive notifications. When an Article 73 incident timer hits 48 hours, the bot DMs the responsible person. When a high-risk agent gets approved, the bot announces in the governance channel. When a quarterly Post-Market Monitoring report is ready, the bot offers it as a download. The platform comes to your team instead of your team having to remember to come to the platform.

The same bot backend now ships as a Microsoft 365 Copilot custom engine agent. Manifest v1.21 with `copilotAgents.customEngineAgents` lets users discover Fronterio inside Microsoft 365 Copilot Chat alongside their other agents. Same install, two surfaces — and AppSource submission unlocks the Custom Engine Agent badge in the Copilot agent store.

Proactive messaging works through the `teams_conversation_references` table. When a user installs the bot the conversation reference is stored with their Microsoft tenant ID and conversation token. The platform can then push messages to that user's Teams chat from any Fronterio backend event — incident timers, approval workflows, weekly digests.

Setup is admin-only and dashboard-driven (no terminals). The runbook in docs/ops/fronterio-everywhere-activation.md § 1-2 walks through Azure AD app registration, manifest sideload, AppSource submission, and Copilot Chat enablement — each step a Microsoft admin clicks through with copy-paste-ready values.