Docebo Connect for Microsoft Teams: a Spanish SME setup

For a Spanish SME running Docebo as the LMS and Microsoft Teams as the day-to-day collaboration surface — which is the default stack for any company on Microsoft 365 — the integration question is not “should we connect them” but “what does connecting them actually deliver, and what data leaves which boundary.” Microsoft Teams sees over 320 million monthly active users globally, and for the SME’s L&D function it is the place where training notifications either land in the workflow people are already in or fail to land in the inbox they have already given up on. Docebo Connect for Microsoft Teams is the integration that closes the gap, and the technical detail worth understanding before installing it is small but consequential.

Adaptive Cards — what they are and why they outperform plain webhook posts

The most-used Docebo Connect feature for Microsoft Teams is Adaptive Cards — Microsoft’s structured-message format that renders as an interactive card inside a Teams channel or chat, rather than a plain text notification. The distinction matters because Adaptive Cards can carry buttons, fields, and dynamic content; a plain webhook post is a one-line message that the user reads and dismisses. The Adaptive Card is the surface where the user can act on the notification without leaving Teams.

For an SME’s L&D recipes, the practical Adaptive Card payloads are: course enrollment notifications with an “Enroll” button that posts back to Docebo to confirm the seat, completion celebrations that include the badge image and a “View certificate” button, deadline reminders with the assignment title, due date, and a “Start training” link straight into Docebo’s player, and channel-posted achievements that include the learner’s name and the milestone (1,000 XP earned, certification renewed, leaderboard position).

The technical detail that catches teams is that Adaptive Cards are templated JSON, not free-text messages. The Docebo Connect recipe author writes the card schema once, parameterises the dynamic fields (learner name, course title, due date), and the recipe substitutes them at runtime. The benefit is consistency: every notification of the same type renders identically across the team’s channels, which is what makes the system feel designed rather than ad-hoc. The cost is the upfront work to design the card layouts — an SME without a brand designer can use Microsoft’s Adaptive Cards Designer tool to start from a template and tune.

For a Spanish SME under INCIBE supply-chain expectations, the Adaptive Card schemas themselves are part of the documentation surface. They live in version control alongside the recipes, they are reviewed via PR, and they are auditable evidence of “what data flows from Docebo to Teams in each notification type” — which is the kind of question a quarterly review will ask.

Channel-based enrollments and training bot commands — the two-way integration patterns

Beyond notifications-out, Docebo Connect for Microsoft Teams supports two patterns where the integration acts on Teams events to drive Docebo state.

Channel-based enrollment triggers on a user joining a specific Teams channel and automatically enrolls them in a Docebo course or learning plan. The recipe is straightforward: the trigger is “user added to channel X”, the action is “enroll user in course Y in Docebo”, and the matching key is the user’s email or Microsoft 365 ID. The pattern is the right answer when the SME organises projects or teams as Teams channels and onboarding into a project means the new member needs the project’s training catalogue. The discipline is to keep the channel-to-course mapping in version-controlled configuration rather than hard-coded in the recipe — a 10-channel SME will end up with 10 mappings inside a year, and the configuration file is the audit surface that lets the L&D lead see them all in one place.

Training bot commands let learners check their training status from inside Teams using slash commands. The commands the SME’s L&D lead is likeliest to enable: /training status returns the user’s current enrollments and progress, /training upcoming returns deadlines in the next 14 days, /training certificates returns earned credentials with verification links. The bot lives inside the SME’s Teams tenant, the recipe handles the command-to-Docebo-API mapping, and the response renders as an Adaptive Card in the user’s chat with the bot.

The data-residency point worth flagging for a Spanish SME under GDPR: Microsoft Teams data lives in the Microsoft 365 region the tenant is provisioned to (EU West for most Spain-based tenants), and Docebo data lives in the Docebo region the SME’s instance is provisioned to. The Docebo Connect recipe runtime — Workato’s embedded engine — sits between them and processes the bot command in flight. The recipe should not write learner PII to recipe variables that get logged; the Workato logs are the third data location, and they sit in Workato’s regional infrastructure. The integration owner’s documented decision on which Workato region the SME’s Docebo Connect instance runs in is part of the EU AI Act Article 13 transparency surface for any AI-augmented training workflow.

Setup and the operational discipline — what an SME should document up front

Setting up Docebo Connect for Microsoft Teams requires three pieces of configuration: the Microsoft 365 tenant ID and the OAuth scopes the integration needs (typically Channel.Read.All, ChannelMessage.Send, User.Read.All), a service-account user in Microsoft 365 dedicated to the integration (never a personal account, because credential rotation when the personal-account holder leaves the company is the predictable failure mode), and the Docebo Connect connector configured with the OAuth credentials and the target tenant URL.

The five-minute setup walkthrough lives at help.docebo.com, but the SME’s documentation should add four entries the official guide does not cover. First, the OAuth scope inventory — the exact list of Microsoft Graph permissions the integration uses, with a one-line justification per scope. Second, the channel-to-course mapping configuration — a single JSON or YAML file that defines which channel triggers which Docebo enrollment, version-controlled and reviewed via PR. Third, the Adaptive Card schemas — the JSON templates for each notification type, with screenshots of the rendered output for the team to reference. Fourth, the data flow diagram — a one-page artifact showing which fields move from Docebo to Teams, from Teams to Docebo, and which fields the recipe transforms in flight.

For a Spanish SME accessing Kit Digital IA/BI vouchers — Segment III (10-50 employees) up to €12,000, Segment II (3-9 employees) up to €6,000 — these four artifacts are the deliverable that converts “we connected Docebo to Teams” into “we documented the integration in a way an auditor can review.” The Agente Digitalizador can install the integration, ship the four artifacts, and hand the L&D lead a runbook that survives the first credential rotation without breaking.

Ready to get started?

Working on this yourself? J4SGON S.L. delivers Docebo Connect, HRIS, SSO and migration work for European organisations — see what a scoped engagement covers or describe your project and we will reply with a written scope.