Skip to main content
Topics#Headless360Pregunta de Vimitra Raman
Vimitra Raman (Wargitsch) preguntó en #Headless360
20 ago, 07:41

Looking for hands-on guidance: Salesforce Headless 360 + Microsoft Teams integration

Hi everyone,

 

I’m currently working on a Salesforce Headless 360 demo and have been asked to implement/document three use cases using Microsoft Teams:

  1. Add/update meeting notes on an Event related to a Lead or Opportunity
  2. View the sales pipeline in Microsoft Teams
  3. Create a new Lead directly from Microsoft Teams

I have already enabled the Salesforce Microsoft Teams integration in my demo org and configured the required Salesforce permission set. However, I’m finding that the Teams setup is more involved than connecting Salesforce with MCP-compatible clients such as Claude or ChatGPT.

I’m specifically looking for hands-on tutorials, workshops, sample implementations, or documentation showing how to use Salesforce Headless 360 with Microsoft Teams for conversational/action-based use cases.

A few questions:

  • Is there currently a Salesforce hands-on workshop or demo specifically for Headless 360 + Microsoft Teams?
  • What is the recommended architecture for connecting Teams to Salesforce Headless 360?
  • Should we use the native Salesforce Teams integration, Agentforce, Microsoft Copilot Studio, MCP, or another approach?
  • Is an intermediate agent/application required for these types of use cases?
  • Has anyone successfully implemented creating/updating Salesforce records from Teams using Headless 360?
  • Are there any sample repos, demo orgs, videos, or step-by-step guides available?

I’ve found the Salesforce Headless 360 workshops for Hosted MCP and Claude, but I’m specifically looking for a comparable hands-on Teams implementation.

Any guidance or examples from someone who has already implemented this would be greatly appreciated.

Thanks! 

 

#Headless360

2 respuestas
  1. Himanshu Shekhar (AQBEE Innovations Pvt. Ltd.)
    20 ago, 07:51

    Hi Vimitra - the friction you are hitting is real, and it comes down to one core difference: Microsoft Teams is not an MCP host, so unlike Claude or ChatGPT it cannot just auto-discover the Salesforce MCP tools. In Teams you have to supply the action layer yourself - a bot/agent that sits between the Teams chat and Salesforce. That is why it feels heavier than pointing an MCP client at your org. 

     

    There are three legitimate paths, and the right one depends on how conversational each use case really needs to be: 

     

    1) The packaged Salesforce integration for Microsoft Teams (what you have already enabled). It is great for surfacing and logging: search/view/pin Salesforce records in a channel or meeting, and log activities/notes back to a related record. So it already covers most of your meeting-notes and view-pipeline cases with no code - pin a pipeline report or list view, and log the meeting notes to the Event/Opportunity from the meeting tab. What it does NOT do well is free-text conversational actions like creating a lead by chatting. 

     

    2) Microsoft Copilot Studio (formerly Power Virtual Agents) - usually the most practical way to get the conversational, action-based flows into Teams. You build topics/actions that call Salesforce via the Salesforce connector or an HTTP call to your Apex/Flow REST endpoint, then publish the Copilot to Teams. Create-a-Lead and update-notes map cleanly to Copilot Studio actions. 

     

    3) Agentforce agent + a bot bridge. If you want the reasoning/agent experience (not just fixed topics), stand up an Agentforce agent with invocable actions (Flow or Apex) for create-lead / update-notes / query-pipeline, then surface it in Teams through a bot channel (Copilot Studio, or a Bot Framework/Azure Bot relay calling the agent API). Teams does not yet have the one-click channel that Slack is getting, so this bot bridge is the current pattern. 

     

    How I would map your three demo use cases: 

    - Meeting notes on an Event (Lead/Opp): packaged integration for the manual log path; a Copilot Studio or Agentforce action for the conversational 'update the notes' path. 

    - View sales pipeline: packaged integration - pin an Opportunity report or list view. Zero code, best ROI for a demo. 

    - Create a Lead from Teams: Copilot Studio action, or an Agentforce invocable action hitting the Salesforce API. This is the one that genuinely needs the bot layer. 

     

    Building blocks to search for in Help/Trailhead: 'Salesforce integration for Microsoft Teams' (setup + activity logging), 'Agentforce agent actions with Flow or Apex', and Microsoft's 'Copilot Studio Salesforce connector / publish to Teams'. Those three together give you the whole path, and they are the pieces the demo really rests on regardless of the branding. 

     

    If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

Escribir una respuesta...
0/9000