Centro

Setup guide

How to connect Microsoft Teams and Salesforce

Three supported methods, with setup steps, prerequisites, and what each one can do.

βœ“You will need admin rights in Salesforce and in the Teams admin center.
Before you start β€Ί

There are three supported ways to connect Microsoft Teams and Salesforce: the native Salesforce for Microsoft Teams app, a Power Automate flow, or a purpose-built integration such as Centro. This page walks through the setup for each, what it can and cannot do, and how to choose. It is written for a Salesforce admin or IT lead who has admin rights in both systems.

Before you start

You will need:

  • βœ“Sales Cloud or Service Cloud on Enterprise, Performance, or Unlimited edition, and a Salesforce admin with access to Setup
  • βœ“A Microsoft 365 tenant with a Teams admin who can approve apps in the Teams admin center
  • βœ“A decision on who owns the integration after go-live: Salesforce admin, Teams admin, or both
1

The native Salesforce for Microsoft Teams app

This is the free app Salesforce publishes to the Microsoft Marketplace. It lets users mention Salesforce records in chats and channels, pin a record as a channel tab, and see Salesforce context inside a Teams meeting.

Setup steps

  1. 1In Salesforce Setup, enter Teams in the Quick Find box and select Teams Integration. Turn on Let users access Teams Integration features and acknowledge the agreement.
  2. 2Select Assign Permission Set and assign the User for Teams Integration permission set to everyone who will use Salesforce in Teams. Choose how much record data to show when a user mentions a record.
  3. 3In the Teams admin center, allow the Salesforce app for your org or for a policy group.
  4. 4Each user installs the Salesforce app in Teams, signs in to Salesforce, and links the two accounts.
  5. 5Test by opening a chat and mentioning a record, then pinning an opportunity to a channel.

Quick facts

Runs in: Teams chats, channels, and meetings

Owned by: No admin setup

Pricing model: Included

Limits: No automation, every user needs a Salesforce license

What it does well

  • βœ“Zero cost beyond your existing licenses
  • βœ“Record previews and mentions in chats and channels, and inline edits on records you pin or mention
  • βœ“Meeting integration for Sales Cloud users

Where it stops

  • βœ•No automation. It does not create channels, post updates when a record changes, prompt users for input, or run anything from Salesforce Flow.
  • βœ•Every user needs a Salesforce license and a linked account. There is no way to include a non-licensed teammate.
  • βœ•Channel to record linking is one channel to one record, set up by hand.
  • βœ•Supports standard and custom objects that have an activity timeline. Test any object that does not, and any Financial Services Cloud object you rely on, before rollout. Record details shown on cards are stored in your Microsoft 365 Teams storage.
2

Power Automate

Power Automate is Microsoft's automation service. The Salesforce connector gives you triggers such as "when a record is created" and actions such as "create a record," which you can chain to Teams actions such as "post a message in a channel."

Setup steps

  1. 1In Power Automate, create a new automated cloud flow.
  2. 2Add the Salesforce connector as the trigger and sign in with a Salesforce integration user. The Salesforce connector is a Premium connector, so the flow needs a Power Automate Premium per-user license or a Process per-flow license.
  3. 3Choose the object and trigger condition, for example Opportunity, when a record is modified.
  4. 4Add a condition step to filter on the field change you care about, for example Stage equals Closed Won.
  5. 5Add a Microsoft Teams action, such as post a message in a chat or channel, and map the Salesforce fields into the message.
  6. 6Save, run a test record through, and check the flow run history.

Quick facts

Runs in: Power Automate cloud flows

Owned by: Microsoft admin

Pricing model: Premium per-user or per-flow license

Limits: One flow per use case, request limits per license

What it does well

  • βœ“Good for one-way notifications from Salesforce into Teams
  • βœ“Uses a tool your Microsoft admin already knows
  • βœ“No new vendor

Where it stops

  • βœ•Each notification is its own flow. Ten use cases means ten flows to build, license, and maintain.
  • βœ•Writing back to Salesforce from Teams requires building a form or adaptive card, plus a flow to handle the response.
  • βœ•Every action in a flow counts as a Power Platform request, including failed runs and retries. A Premium per-user license allows 40,000 requests per 24 hours, so busy notification flows on one service account can hit the ceiling.
  • βœ•No native concept of a channel tied to a record, so channel creation and membership are manual or another flow.
  • βœ•Salesforce field-level security is enforced through the integration user, so every flow runs with that user's access, not the reader's.
3

Centro

Centro is a Salesforce-native integration for Microsoft Teams. It runs as a managed package in your org and an app in Teams. Automation is built in Salesforce Flow, not in Teams, so your Salesforce admin owns it.

Setup steps

  1. 1Install the Centro managed package from AppExchange into a sandbox first, then production.
  2. 2In the Teams admin center, approve the Centro app from the Microsoft Marketplace (listing WA200008222).
  3. 3Connect the Salesforce org to your Microsoft tenant from the Centro setup page in Salesforce. This is an admin-level consent, done once.
  4. 4Assign the Centro permission set to users. Users who do not have a Salesforce license can be reached through Centro's automation user.
  5. 5Build your first automation in Salesforce Flow using Centro's flow actions: create a Teams channel from a record, post a message, add members, or prompt a user for an update.
  6. 6Optional: turn on CentroBot so users can ask questions and update records from Teams by prompt.
Full install steps on the support site
The Microsoft Teams sidebar listing Salesforce record-named chats for individual opportunities, with one opportunity conversation open beside its Centro record card.

What it does well

  • βœ“Two-way: Salesforce changes post to Teams, and Teams responses write back to Salesforce
  • βœ“Channel lifecycle management: create, name, add members, archive, all driven by record data, with any number of conversations linked to any record
  • βœ“Works with any object, standard or custom, including Financial Services Cloud
  • βœ“No Apex, no Block Kit, no Power Automate. Everything is declarative in Flow.
  • βœ“Salesforce data is read and written through the Salesforce API and is not copied to a separate database. See /security.
  • βœ“Agentforce and CentroBot in Teams for prompt-driven record updates and questions

Where it stops

  • βœ•It is a paid product. See /pricing.
  • βœ•Requires a Salesforce admin comfortable with Flow.

Which method fits

RequirementNative appPower AutomateCentro
Mention and preview records in TeamsYesNoYes
Post to Teams when a record changesNoYes, one flow per use caseYes, in Flow
Update Salesforce from TeamsInline edit on a pinned or mentioned recordBuild a form and a second flowYes, prompts and forms built in
Create and manage channels from recordsNoManual or custom flowYes
Include teammates without a Salesforce licenseNoRead only, via the flow userYes, via the automation user
Custom objects and Financial Services CloudObjects with an activity timelineYes, per flowYes
Who maintains itNo admin setupMicrosoft adminSalesforce admin
CostIncludedPower Automate premium licensesPer-user subscription

If you only need record previews and hand edits in chat, install the native app and stop there. If you need a handful of one-way notifications and already have Power Automate premium licenses, build the flows. If you need channels tied to records, two-way updates, or non-licensed teammates in the loop, that is what Centro is built for. Evaluating for a bank, wealth manager, or insurer? See the financial services comparison. Book a demo.Β See every comparison on one page.

Frequently asked questions

Is there a free way to connect Microsoft Teams and Salesforce?

Yes. The native Salesforce for Microsoft Teams app is free with a supported Salesforce edition. It handles record mentions and previews but does not automate anything.

Can I connect Salesforce and Teams without code?

Yes. All three methods on this page are no-code. The native app is configuration only. Power Automate uses a visual flow builder. Centro automations are built in Salesforce Flow.

Does connecting Salesforce to Teams copy my data to a third party?

It depends on the method. Centro reads and writes through the Salesforce API and does not keep a separate copy of your records. Check the data flow of any integration you evaluate. Centro's is documented at /security.

Can Salesforce post to a Teams channel when an opportunity changes?

Not with the native app. Power Automate can do it with a flow per trigger. Centro does it from a Salesforce Flow action.

Do all my Teams users need a Salesforce license?

For the native app, yes. For Centro, no. Centro's automation user lets non-licensed teammates receive updates and respond to prompts.

Need channels tied to records and two-way updates?

If you need channels tied to records, two-way updates, or non-licensed teammates in the loop, that is what Centro is built for.