Odoo and Microsoft Teams

No native module

Verified against the Odoo 19 source: no Teams module in Community or Enterprise. So this is a webhook, a third-party app, or a custom build against Microsoft Graph.

Before choosing among those, work out which of two very different requests you actually have.

Almost always, it is notifications

"Integrate Odoo with Teams" nearly always decodes to "tell the channel when something happens". A large order comes in, a ticket breaches its SLA, a stock item runs out, an approval is waiting.

That is an incoming webhook: a URL on the Teams channel that accepts a POST and renders it as a message. No app registration, no permissions, no OAuth.

From Odoo it is one HTTP call, and the important detail is where you make it. Not inside the user's save, because a slow or unreachable endpoint then blocks their work and a failure rolls back their record. Queue it and send from a scheduled action, or at minimum send after the transaction rather than during it.

Notification content is worth a moment's thought too. A message saying something happened, with a direct link to the record, is useful. A message containing the full detail encourages people to act from the notification instead of opening the system, and then Teams becomes a place where decisions are made and no record exists.

When a real integration is justified

Two cases genuinely need more than a webhook.

Acting from inside Teams. Approving a request or updating a record without leaving the client. This means a Teams app with a bot or message extension, an app registration, permissions and a deployment story. It is a proper project, and it is worth it only when the volume of interactions is high enough that context switching is a measurable cost.

Two-way conversation linking. Keeping a Teams thread and an Odoo record in step. This is where most Teams projects quietly fail, because the two models do not correspond: a record's chatter is an ordered permanent log tied to one object, and a Teams thread is a conversation that drifts, branches and belongs to a channel.

Do not move chatter into Teams

Worth stating directly because it comes up as a proposal.

Odoo's chatter is a durable record attached to the thing it discusses. Open the order in a year and the reasoning is there, visible to whoever has access to that order.

A Teams conversation belongs to a channel and to whoever was in it. It is searchable in Teams, unattached to the order, and invisible to the person who inherits the account later.

The right split is discussion about a record in the record, and notifications in Teams pointing at it. Teams tells you to look; Odoo holds why.

Practical notes

One webhook per purpose, not one per event. A channel receiving every notification gets muted within a week, and a muted channel is worse than no notification because everyone believes it is working.

Store the webhook URL as configuration, not in code. It is a credential of sorts: anyone holding it can post to that channel.

Handle failure quietly. A notification that cannot be delivered should log and move on, never block or roll back the business operation it was reporting.

Expect the URL to change. Channel webhooks get regenerated and channels get archived. A notification path that silently stopped working is the standard failure here, which is why alerting on silence rather than on errors matters, as covered in integration architecture.

The same reasoning applies almost unchanged to Slack.