How to Build an AI Agent for Microsoft 365 and Salesforce

The workflow problem

Enterprise sales organizations that run Microsoft 365 alongside Salesforce face a fragmented customer communication problem. Reps conduct business across three Microsoft surfaces – Outlook for email, Teams for internal and sometimes external collaboration, and OneDrive/SharePoint for document sharing – but all of this activity needs to end up in Salesforce as part of the customer record.

The daily reality for an enterprise rep looks like this: they send a proposal via Outlook, discuss pricing in a Teams channel with the solutions team, share a security questionnaire response through OneDrive, and then have a follow-up call scheduled in Outlook Calendar. Each of these interactions generates customer-relevant data. None of it automatically appears in Salesforce.

Salesforce offers the Outlook integration panel, which lets reps manually log emails and events. But “manually” is the key word. The rep has to click “Log to Salesforce” on each email, find the right record, and confirm the association. In practice, this means most emails are not logged. Teams messages, which increasingly contain substantive deal discussions and customer-shared requirements, are not captured at all. Shared documents are uploaded to OneDrive but not linked to the Salesforce opportunity where they belong.

The result is a CRM that captures maybe 30% of the actual customer interactions happening across Microsoft 365, leaving managers blind to deal activity and creating continuity risks when reps change roles or leave the organization.

Why an AI agent, not just automation

Microsoft’s own connectors and Salesforce’s Outlook integration handle basic scenarios: syncing calendar events, providing a sidebar for manual email logging. But these tools operate at the level of individual records and require human action at each step.

An AI agent processes the full context of Microsoft 365 activity and makes intelligent decisions about what to capture and where to route it. When the agent reads an Outlook email thread, it does not just log the latest message – it reads the entire thread, identifies the key decisions and action items, and writes a concise summary to Salesforce. It can distinguish between a substantive negotiation email and a routine scheduling exchange, logging the former in detail and noting the latter briefly.

For Teams, the intelligence is even more critical. Deal-related discussions happen in Teams channels alongside casual conversation, shared GIFs, and off-topic threads. An automation tool that logged everything would be useless. The agent identifies which messages in a Teams channel are substantive deal discussions – pricing mentions, competitive comparisons, customer requirement discussions – and captures those specific exchanges in the Salesforce record with context.

The agent also makes document associations that no sync tool can manage. When a rep shares a file in a Teams channel and says “here’s the updated SOW for Meridian,” the agent understands that this document should be linked to the Meridian Health opportunity in Salesforce, even though there is no metadata connecting the OneDrive file to the CRM record.

How it works with ACP

The Agentic Control Plane connects to Microsoft 365 through Microsoft Entra ID (Azure AD) OAuth and to Salesforce through its standard connected app OAuth flow. The agent receives scoped access to the Microsoft Graph API and the Salesforce REST API.

On the Microsoft 365 side, the agent can read Outlook mail messages and folders, read calendar events, read Teams channel messages in teams it has been added to, and access OneDrive files and metadata. On the Salesforce side, it can query and update all standard CRM objects – Contacts, Accounts, Opportunities, Tasks, Events, and Notes – as well as attach files and create content document links.

You describe the agent’s scope: “Monitor my Outlook inbox for customer emails and log them to the matching Salesforce records. Watch the #enterprise-deals Teams channel for deal-relevant discussions and add notes to the corresponding opportunities. When documents are shared in deal channels, link them to the Salesforce opportunity.”

Here is the agent in action across all three Microsoft surfaces:

Outlook email from procurement@globalfinance.com: “Hi David, we’ve completed our internal review. Budget has been approved for $290K annual. We’ll need to push the start date to May 1 instead of April 15 due to our IT freeze in late April. Please send the revised contract reflecting these changes.”

Agent actions:

• Logged email to Opportunity Global Finance - Enterprise Platform with summary: “Budget approved at $290K/yr. Start date pushed to May 1 (IT freeze). Requesting revised contract.”
• Updated Opportunity Amount: $290,000 (was $275,000)
• Updated Opportunity Close Date: May 1 (was April 15)
• Created Task: “Send revised contract to Global Finance reflecting May 1 start date and $290K pricing” – Due: Tomorrow – Owner: David R.

Teams channel (#global-finance-deal): Solutions Engineer: Just got confirmation from their security team that they need SOC 2 Type II and HIPAA BAA before they can proceed. They also want the penetration test report from our last audit.

Agent: Noted – adding security requirements to the Global Finance opportunity. Updated Salesforce: Next Step now includes “Provide SOC 2 Type II certificate, HIPAA BAA, and penetration test report.” Created Task: “Gather security compliance documents for Global Finance” – Due: This Friday – Owner: David R.

OneDrive share in #global-finance-deal: Solutions Engineer shares “GlobalFinance_Architecture_Diagram_v3.pdf”

Agent: Linked document to Salesforce Opportunity Global Finance - Enterprise Platform as an attachment under Files. File name: GlobalFinance_Architecture_Diagram_v3.pdf.

The agent creates a complete customer record across email, chat, and document sharing without any manual CRM data entry.

Governance and security

Microsoft 365 contains an organization’s entire communication fabric – emails, chats, files, calendars. Granting an agent access to this data requires precise scoping and comprehensive audit trails.

The Microsoft Entra ID OAuth flow uses Microsoft Graph permissions, which are among the most granular in the industry. The agent requests only the specific permissions it needs: Mail.Read for Outlook emails (not Mail.ReadWrite), Calendars.Read for calendar events, ChannelMessage.Read.All for Teams channels, and Files.Read for OneDrive. Each permission is explicitly consented to by an admin during setup. The agent cannot send emails, delete messages, modify calendar events, or access any Microsoft 365 service beyond what is explicitly granted.

For Salesforce, the connected app uses limited API scopes, and field-level security controls which CRM fields the agent can read and write. Sensitive fields like SSN, financial account numbers, or internal-only notes can be excluded from the agent’s profile.

The ACP audit log provides a unified view of every action across both platforms. You can trace exactly which Outlook emails were processed, which Teams messages were captured, which files were linked, and what was written to Salesforce. This traceability is critical for organizations subject to SEC, FINRA, or GDPR requirements around communication archival and data processing.

Teams message access is restricted to channels where the agent’s app has been installed. It cannot access private chats, one-on-one messages, or channels in teams that have not granted it access. This ensures the agent’s reach is explicitly controlled by team owners and IT administrators.

Data minimization is enforced by default. The agent extracts and logs relevant business information to Salesforce but does not store raw email bodies, Teams message histories, or file contents in the ACP platform itself.

Example use cases

• Outlook email logging with intelligence: Customer emails are automatically logged to the matching Salesforce contact or opportunity with AI-generated summaries. The agent identifies pricing, dates, and action items and updates CRM fields accordingly.

• Teams discussion capture: Substantive deal discussions in Teams channels are summarized and added as notes on the corresponding Salesforce opportunity. Casual conversation and off-topic messages are filtered out.

• Document linking: Files shared via OneDrive or Teams are automatically associated with the correct Salesforce opportunity as attachments, creating a complete document trail alongside the deal record.

• Cross-platform activity timeline: The agent builds a unified activity history on Salesforce records that includes Outlook emails, Teams discussions, and shared documents, giving managers a complete view of customer engagement.

• Calendar sync with context: Outlook calendar meetings with customers are logged to Salesforce with attendee details, meeting purpose, and post-meeting follow-up tasks, enriching the CRM beyond what basic calendar sync provides.

Getting started

Bridge Microsoft 365 and Salesforce in three straightforward steps.

1. Sign up at cloud.agenticcontrolplane.com. Create your free workspace.

2. Connect your tools. Authorize Microsoft 365 (an Azure AD admin will need to consent to the requested Graph permissions) and Salesforce (log in and approve the connected app) from the Data Sources page.

3. Describe your agent. Specify what the agent should capture: “Log customer Outlook emails to Salesforce. Capture deal discussions from Teams channels. Link shared documents to opportunities.” The agent begins syncing immediately.