Salesforce Integration with Teams

Regular Visitor

Hey there, 


I'm having trouble finding out "if" and "how" Salesforce integrates with MS Teams if at all. I was able to find the connector for Salesforce, but had some trouble getting it to run. What is the functionality of this connector and its capabilities?


Can anyone tell me if this is still a working piece of MS Teams or is this something Microsoft has stopped working on altogether? 







25 Replies

@ExchangeFanWhen Microsoft delivers something usable ... we'll build something. This thread is worth keeping an eye on:

@Jamealle Spain here is another one 

@Jamealle Spain teams integraiton for telephony is available form Natterbox where you can achieve integration not available from other providers - for example using Teams and not having to replace the telecoms of Teams to achieve it - see here 

@WayneK  We have delivered Salesforce teams integration allowing you to retain Teams as the communications platform and link to Salesforce.  more at

Hi@Jamealle Spain 


Most enterprise-level applications have a need to integrate with other applications used by the same organization. This integration usually caters to different layers, like Data, Business Logic, Presentation, and Security, depending on the requirement. This helps organizations achieve greater levels of operational consistency, efficiency, and quality.

This article, the first in the series Learning Salesforce Integration, outlines a few of the options available for integrating other client applications with the platform. The main focus is on Web Service integration, including both inbound and outbound to The client application considered in this article is Oracle Siebel CRM.


Possible Ways to Integrate with Salesforce
Speaking further on the different layers and integration features available at each level for an enterprise-level application, we have:

User Interface
Business Logic
User Interface Integration is one great way to surface various applications inside Salesforce with little redesign of each individual app. It provides your users a single point of entry into multiple applications. The most relevant example is Facebook Apps, which appears to be in the Facebook instance but in reality, the content is served from different application vendors.


Business Logic Integration uses Apex Web Services for Inbound and Apex Callouts for Outbound. It typically handles a scenario where business logic is spread across several applications to implement the complete end-to-end business process. An example would be building complex logic on the data received before committing it into Salesforce.

Data Integration uses SOAP APIs and REST APIs. It typically handles data synchronization requirements, where one application in an enterprise acts as the primary source for a particular business object, like an Account. It requires no coding in Salesforce, which is an advantage, but then it cannot implement any custom logic.

As mentioned earlier, our focus for the rest of this document will be on the Business Logic and Data Integration layers, which implement Web Services.


Deep Dive
Business Logic Integration helps extend the business logic present in with outside platforms. In the case of inbound logic integration, it is handled using Apex Web Services.

Apex Web Services allow us to write logic and expose it as a web service with external applications. It gives us flexibility in adding custom logic before modifying the standard or custom objects data. We can apply project-specific business logic while exposing web services.


Data Integration helps us in maintaining consistency in the application data between multiple systems that need to be in sync. One way we can achieve talking about real-time synchronization of data between systems is by using SOAP APIs, among other available options.

SOAP API lets you create, retrieve, update or delete records, such as accounts, leads and custom objects. With more than 20 different calls, SOAP API also allows you to maintain passwords, perform searches and much more. Use SOAP API in any language that supports web services. It provides two WSDLs to choose from –

Enterprise Web Services WSDL – Used for building client applications for a single Salesforce organization. The enterprise WSDL is strongly typed, which means that it contains objects and fields with specific data types. Customers who use the enterprise WSDL document must download and re-consume it whenever their organization makes a change to its custom objects or fields, or whenever they want to use a different version of the API.
Partner Web Services WSDL – Used for building client applications for multiple organizations. As a loosely typed representation of the Salesforce ( Salesforce Online Certification Training )  data model that works with name-value pairs of field names and values, instead of specific data types, it can be used to access data within any organization. The partner WSDL document only needs to be downloaded and consumed once per version of the API.


Thanks in Advance,

Lavanya Sreepada

@Jamealle Spain Microsoft Partners with Salesforce to Deliver Microsoft Teams Integration for Sales and Service. ... We are pleased to announce the availability of the Salesforce in Microsoft Teams pilot. The integration will be offered to Sales and Service Cloud customers with Enterprise or Unlimited edition at no additional cost.

Regards : salesforce course in pune