Microsoft Sales Copilot Not Working? Fix It Now
Why This Is Happening
I've helped a lot of sales teams get Microsoft Sales Copilot , now officially rebranded as Sales agent , up and running, and I'll tell you the honest truth: the product is genuinely powerful once it works, but the initial setup bites people constantly. You're dealing with a tool that sits at the intersection of Microsoft 365 licensing, your CRM platform (Dynamics 365 Sales or Salesforce), Outlook add-ins, and Teams integrations all at once. When any one of those layers has a permission gap or a misconfigured role, the whole thing silently fails, and Microsoft's error messages almost never tell you which layer is actually the problem.
The most common scenario I see: a sales manager installs Microsoft Sales Copilot, hands it off to the team, and within 24 hours the support tickets start rolling in. "The Sales agent pane isn't showing in Outlook." "I can see it in Teams but it won't connect to my Salesforce account." "I clicked Authorize and nothing happened." Sound familiar? These aren't bugs, they're almost always permission or licensing mismatches hiding behind vague UI messages.
Here's the core of what goes wrong most often. Sales agent requires a Microsoft 365 admin role just to install and configure it. That's your first filter. Then, on the CRM side, your Dynamics 365 users need either the Sales Manager or Salesperson security role, and your admins need either System Administrator or System Customizer. If someone's using a custom security role, which is extremely common in mid-to-large enterprises, additional privileges have to be explicitly added. The documentation calls this out, but it's buried, and most IT teams only catch it after the fact.
There's another wrinkle that trips people up with Microsoft Sales Copilot setup problems: permission changes in your CRM don't propagate instantly. In Outlook, a user has to fully sign out of Sales agent and sign back in before updated security roles are reflected. In Teams, you're looking at up to a 15-minute propagation delay. Nobody tells you that at deploy time, so teams spend an hour re-checking settings that are actually already correct, they just haven't taken effect yet.
It's also worth being upfront about platform limitations. Sales agent doesn't work on Microsoft Dynamics 365 Customer Engagement (on-premises). It's cloud-only. And if your organization is in Government Community Cloud (GCC), including USG or Department of Defense environments, Sales agent simply isn't supported yet. I know that's frustrating if you're in one of those environments, but it's important to know early so you don't spend hours troubleshooting something that's architecturally blocked.
I know this is a lot of moving parts, especially when you're trying to get a sales team productive and people are breathing down your neck. Let's work through it systematically. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you dig into any deep configuration changes, try this. It resolves a surprising number of Microsoft Sales Copilot not working cases in under five minutes.
Step 1: Sign out of Sales agent in Outlook completely. Open Outlook, find the Sales agent pane on the right side, scroll down to the bottom of it, and hit Sign out. Don't just close Outlook, actually use the sign-out option inside the add-in itself. Then close and reopen Outlook entirely.
Step 2: Sign back in and re-authorize your CRM connection. When the Sales agent pane reloads, sign in with your Microsoft work or school account. When it prompts you to connect your CRM, Dynamics 365 Sales or Salesforce, go through the authorization flow fresh. This clears any stale OAuth tokens that silently break the CRM data sync.
Step 3: Check your security role in your CRM right now. Log into Dynamics 365 Sales (or have your Salesforce admin confirm your profile). Verify you have the Sales Manager or Salesperson role in Dynamics 365, or the equivalent Salesforce permissions. If your organization uses custom roles, confirm with your CRM admin that the role has the additional Sales agent privileges applied. If a change was made recently, wait 15 minutes before testing in Teams, or sign out/sign back in for Outlook.
Step 4: Confirm the add-in is actually enabled in Outlook. Go to File → Manage Add-ins (Outlook desktop) or click the puzzle-piece icon in Outlook on the web. Find Sales agent (it may also appear as Microsoft Sales Copilot depending on your version). Make sure it's toggled on. If it's missing entirely, your Microsoft 365 admin may need to deploy it via the Microsoft 365 admin center.
If all four of these check out and things still aren't working, move on to the full step-by-step below. The issue is likely deeper, usually a license gap or a CRM consent problem that requires admin action.
This is the step most IT teams skip because they assume licenses were handled at procurement. Don't assume. Microsoft Sales Copilot license requirements are specific, and having a regular Microsoft 365 or Dynamics 365 license is not enough on its own. You need to confirm that the correct Sales agent licensing is assigned to each affected user.
Here's how to check. As a Microsoft 365 admin, open the Microsoft 365 admin center at admin.microsoft.com. Navigate to Users → Active users, find the affected user, click their name, and select the Licenses and apps tab. Look for the Sales agent license in the list. If it's not there, the user won't have access, full stop.
For exact licensing language, Microsoft directs you to the Microsoft Product Terms or your Microsoft representative. This matters because licensing models change with release waves and your Enterprise Agreement terms may differ from what's listed in general documentation. If you're uncertain, contact your Microsoft account team directly, don't guess at licensing bundles.
One thing I see constantly in enterprise deployments: the license was purchased and assigned to a group, but a subset of users was excluded from the group assignment by accident, typically when someone manually managed licenses instead of using group-based licensing in Azure Active Directory. Go through each affected user individually to rule this out.
If licenses are confirmed but users still can't access Sales agent features, cross-reference with the Copilot international availability report linked in Microsoft's official docs. Your user's geography or tenant region may not yet be supported for specific AI capabilities, even if the base license is assigned. This is particularly relevant for organizations with users spread across multiple countries.
When the license check is clean, you should see the Sales agent pane load in Outlook without a "subscription required" or "contact your admin" message. That's your green light to move to the next step.
If Sales agent isn't showing up in Outlook or Teams at all, the add-in deployment is the first thing to look at. This isn't a user-level action, it requires a Microsoft 365 admin. Individual users can't install Sales agent themselves; it has to be pushed centrally.
Log into the Microsoft 365 admin center (admin.microsoft.com) with a Global Administrator or Exchange Administrator account. Navigate to Settings → Integrated apps. Search for Sales agent or Microsoft Sales Copilot in the app catalog. Select it and choose Deploy.
During deployment, you'll be asked to choose your deployment scope: Just me, Specific users/groups, or Everyone. For a pilot rollout, use specific security groups. For full deployment, choose Everyone, but be aware this triggers a consent requirement. Sales agent needs permission to access content and share data outside Microsoft 365, including with third-party CRM services like Salesforce. Admins and users must consent to connect their Microsoft work or school account with their CRM account before data sharing is active. No consent, no CRM data.
After deployment, it can take up to 24 hours for the add-in to appear in users' Outlook clients. If you're testing immediately, have the user close Outlook completely and reopen it, or test in Outlook on the web first where the propagation is faster.
For Dynamics 365 customers, there's a dedicated deployment path documented under Deploy Sales agent for Dynamics 365 customers. For Salesforce environments, follow Deploy Sales agent for Salesforce customers, the Salesforce path has additional admin steps on the Salesforce side involving Connected Apps and permission sets that are easy to miss if you're following generic instructions.
Successful deployment looks like this: users open Outlook, see the Sales agent icon in the ribbon or the right-hand pane, and can click into it without getting a "this app isn't available" error.
This is the single most common root cause of Microsoft Sales Copilot not working after a seemingly successful deployment. The CRM-side role requirements are non-negotiable, and they're separate from anything in Microsoft 365.
For Dynamics 365 Sales: Regular users need either the Salesperson or Sales Manager security role assigned in Dynamics 365. Admins who need to customize Sales agent, adjusting which CRM fields appear, setting up Copilot AI features, configuring Lead Research and Outreach, need either System Administrator or System Customizer.
To check and assign roles in Dynamics 365, navigate to Settings → Security → Users, find the affected user, and open their profile. Under the Roles section, verify the appropriate role is listed. To add a role, click Manage Roles and select from the list.
If your organization uses custom security roles, which is very common, you have an extra step. Custom roles don't automatically inherit the Sales agent-specific privileges. You need to explicitly add those privileges to the custom role. Check Microsoft's documentation on privilege requirements for the exact list of privileges needed. Skipping this is the most common reason custom-role users see Sales agent load but can't connect to CRM data or see any opportunity information.
For Salesforce: The permission requirements are documented separately under Permissions required for Salesforce administrators in the official docs. The key point is that Salesforce Connected App settings and object-level permissions in Salesforce itself must be configured in addition to anything on the Microsoft side.
After any role change in CRM: for Outlook, the affected user must sign out of Sales agent and sign back in, the role refresh does not happen automatically in the Outlook context. For Teams, wait up to 15 minutes. I know that sounds like a small thing, but I've watched teams spend an hour re-checking configurations that were already correct simply because nobody waited for the propagation delay.
Even with the right licenses and roles, the Sales agent won't show CRM data until the actual connection between Microsoft 365 and your CRM is authorized. This is a two-part consent, admin-level consent, and then individual user consent. Both have to happen.
Admin consent (Dynamics 365): The Microsoft 365 admin needs to authorize the Sales agent to communicate with your Dynamics 365 environment. This is typically handled during the initial deployment wizard in Settings → Integrated apps. If it was skipped or if the environment URL changed (for example, after a tenant migration or a new Dynamics sandbox was promoted to production), you'll need to redo this step.
User-level consent: Each user connecting their Microsoft work or school account to CRM must go through the authorization flow in Sales agent. In Outlook, open the Sales agent pane, click Connect your CRM, select Dynamics 365 Sales or Salesforce, and authenticate. This is where stale OAuth tokens cause silent failures, if a user's Salesforce password changed or an admin rotated API credentials, the old token breaks without any obvious error message in the UI.
To force a clean re-authorization:
# In Outlook: Sales agent pane → Sign out → Close Outlook → Reopen → Sign in → Connect CRM fresh
# In Teams: Remove and re-add the Sales agent app
# Teams → Apps → Manage your apps → Find Sales agent → Remove
# Then re-add from Teams app storeFor Salesforce-specific Microsoft Sales Copilot connection errors, confirm in Salesforce Setup that the Connected App created during deployment still has the correct callback URLs and that the Salesforce admin hasn't revoked the OAuth policy. This trips up a lot of teams after routine Salesforce maintenance windows.
When the CRM connection is working correctly, you'll see live opportunity data, contact records, and CRM field information populating inside the Sales agent pane in Outlook when you open a relevant email. If the pane shows "Connect to CRM to see insights", that's the signal the connection itself hasn't been completed yet.
Sales agent in Teams has its own set of quirks separate from the Outlook integration. The Teams side handles meeting preparation, meeting summaries with keyword and competitor analysis, deal room creation, and shared CRM record links in conversations. When any of these stop working, here's how to diagnose them.
Sales agent not appearing in Teams at all: First, confirm the app was deployed by your admin. In Teams, go to Apps in the left sidebar and search for Sales agent. If it doesn't appear in search, it hasn't been deployed to your tenant or your account specifically. Your Microsoft 365 admin needs to push it via the Teams admin center at admin.teams.microsoft.com → Teams apps → Manage apps.
Meeting insights not generating: For Sales agent to capture meeting summaries, action items, competitor mentions, and keyword analysis from a Teams meeting, the meeting has to be organized through or linked with Sales agent. Check that the meeting was scheduled using the Sales agent meeting preparation flow, or that the CRM contact/opportunity was linked before the meeting started. Post-meeting summaries won't generate retroactively if the meeting wasn't flagged ahead of time.
Deal room creation failing: Creating a Teams deal room (a collaboration space with CRM data and files) requires that both the Teams and Dynamics 365 or Salesforce permissions are correctly configured. If deal room creation fails with a generic error, check that your Teams admin hasn't applied a policy blocking new team creation for your user account. In the Teams admin center, review Teams policies to confirm users in your group are allowed to create teams.
CRM record sharing in Teams conversations not working: This feature requires the Sales agent app to be pinned or installed in the specific Teams channel or chat. Navigate to the channel, click the + tab button, find Sales agent, and add it. Once added, users can paste CRM record links directly into that conversation and they'll render with context.
After any Teams-side configuration change, give the system up to 15 minutes before concluding it didn't work. That propagation window for permission and role changes is real, and testing too quickly gives a false failure signal.
Advanced Troubleshooting
If the step-by-step above didn't resolve your Microsoft Sales Copilot issues, you're likely dealing with an enterprise-layer problem, Group Policy, tenant configuration, a network proxy, or a more complex CRM integration scenario. Here's where to dig next.
Microsoft Sales Copilot in Enterprise and Domain-Joined Environments
In domain-joined corporate environments, Outlook add-ins are frequently controlled by Group Policy. Even if Sales agent is deployed correctly from the Microsoft 365 admin center, a GPO can silently block it from loading. Open the Group Policy Management Console (gpmc.msc) and look under User Configuration → Administrative Templates → Microsoft Outlook [version] → Security → Trust Center for any policies governing add-in loading. The specific policy to check is List of managed add-ins, if this policy is enabled and Sales agent isn't in the list, it won't load regardless of admin center settings.
You can also check this directly from the Outlook Trust Center: File → Options → Trust Center → Trust Center Settings → Add-ins → Manage: COM Add-ins → Go. If Sales agent appears here but is unchecked, a policy may be forcing it disabled.
Event Viewer and Outlook Logging for Add-in Failures
For Outlook add-in crashes and load failures, Event Viewer is your friend. Open eventvwr.msc and navigate to Windows Logs → Application. Filter by source Outlook and look for Event ID 45 (add-in disabled due to slow load time) or Event ID 1000 (application fault). If Sales agent is being auto-disabled because Outlook marked it as slow, you can re-enable it via File → Slow and Disabled COM Add-ins in Outlook, but you should also investigate whether the underlying latency issue is a proxy or network timeout between Outlook and Microsoft's endpoints.
Network and Proxy Considerations
Sales agent makes outbound HTTPS calls to Microsoft 365 endpoints and to your CRM platform. If your organization uses a web proxy or firewall with SSL inspection, the Sales agent add-in can fail silently because its traffic is being intercepted and the certificate chain validation fails. Check that your proxy is configured to allow-list Microsoft 365 URLs (listed in Microsoft's official endpoint documentation for Microsoft 365) and your CRM's API endpoints. If SSL inspection is stripping headers or altering OAuth responses, Sales agent connections to CRM will fail in ways that look exactly like permission errors.
Tenant-Level Configuration for Copilot AI Features
Some of Sales agent's AI features, email draft generation, BANT assessment, opportunity summaries, require that Copilot AI features are enabled at the tenant level. In the Microsoft 365 admin center, go to Settings → Copilot and verify that Copilot capabilities aren't toggled off for your tenant or for specific user groups. This is a separate toggle from the Sales agent deployment itself and is easy to miss during initial setup.
On-Premises CRM, The Hard Stop
I want to be direct here: if your organization runs Microsoft Dynamics 365 Customer Engagement (on-premises), Sales agent does not work with it. Period. This isn't a configuration issue, it's an architectural limitation. Sales agent requires cloud-connected CRM. If you're on-premises and planning a cloud migration, Sales agent support for Dynamics 365 Online should be part of your migration justification.
Prevention & Best Practices
Once you've got Microsoft Sales Copilot running, keeping it running is a different skill set. A lot of the breakage I see in ongoing deployments comes from routine IT changes, password rotations, security role audits, Outlook updates, that nobody flagged as potentially affecting Sales agent. Here's how to stay ahead of it.
Build Sales agent into your CRM role change process. Whenever your Dynamics 365 or Salesforce admin modifies security roles, adds users to custom roles, or runs a permissions audit, that workflow should include a step to verify Sales agent access for affected users. A simple checklist item, "Does this role change affect Sales agent users? If yes, notify them to sign out and sign back in", prevents a flood of IT tickets the next morning.
Test after every Outlook update. Microsoft releases Outlook updates on a regular cadence, and COM add-ins occasionally get disabled automatically if their load time exceeds Outlook's threshold after an update changes the startup sequence. After any major Outlook version update in your environment, spot-check a few Sales agent users to confirm the add-in is still active.
Document your CRM connected app credentials and expiry dates. For Salesforce-connected deployments especially, the OAuth credentials used in the Connected App configuration may have expiry policies. If your Salesforce admin sets a Connected App consumer secret to expire, Sales agent's CRM connection breaks for all users simultaneously. Put this expiry date in your IT calendar with a 30-day advance reminder.
Keep an eye on the Sales agent release planner. Microsoft ships Sales agent updates in release waves, the 2025 release wave 2 is the current cycle as of this writing. New capabilities sometimes come with new permission or configuration requirements. Subscribe to the release planner notifications so you're not caught off guard when a feature update requires a new admin action to activate.
Use the official training resources during onboarding. Microsoft provides dedicated training under Boost sales performance with Sales agent for users. Getting sellers to spend even 20 minutes with that material before they start using the tool dramatically reduces "it's not working" tickets that turn out to be "I didn't know how to use it" situations.
- Add a "Sales agent access check" step to your CRM role change approval process, catches propagation issues before users notice them
- Create a dedicated Microsoft 365 security group for Sales agent users so you can manage license assignments and app deployment targeting from one place
- After any Outlook update rollout, run a quick add-in health check by asking 2-3 sales reps if the Sales agent pane is still visible
- Document your CRM OAuth credentials and set calendar reminders 30 days before any expiry to avoid a mass connection failure
Frequently Asked Questions
What is Microsoft Sales Copilot / Sales agent and what does it actually do?
Microsoft Sales Copilot, now officially called Sales agent, is an AI assistant built for sales teams that plugs directly into Microsoft Outlook and Microsoft Teams. It connects to your CRM (either Dynamics 365 Sales or Salesforce) and surfaces relevant deal information, contact data, and AI-generated insights right inside the productivity tools your sales reps already use daily. Practically speaking, it helps sellers draft personalized emails using CRM context, get AI-generated summaries of opportunities and email threads (including a BANT assessment), prepare for customer meetings with a snapshot of key details, and create deal room collaboration spaces in Teams. Think of it as your CRM data following you into your inbox instead of you having to jump between tabs all day.
Why is my Sales agent pane blank or not loading in Outlook?
A blank Sales agent pane in Outlook almost always comes down to one of three things: the add-in was auto-disabled by Outlook due to slow load time, your CRM connection has a stale or expired OAuth token, or your security role in Dynamics 365 or Salesforce doesn't have the required privileges. Start by going to File → Slow and Disabled COM Add-ins in Outlook to see if Sales agent is listed there, if it is, re-enable it. Then fully sign out of Sales agent from within the pane, close Outlook, reopen it, and go through the CRM authorization flow fresh. If the pane still doesn't load after that, have your IT admin check your license assignment in the Microsoft 365 admin center and your CRM security role assignment.
I updated my Dynamics 365 security role but Sales agent still shows the old permissions, why?
This is a propagation delay, and it's expected behavior documented by Microsoft. In Outlook, Sales agent doesn't automatically pick up CRM role changes, the affected user needs to explicitly sign out of Sales agent from within the Outlook pane, then sign back in. In Microsoft Teams, role changes can take up to 15 minutes to propagate on their own without requiring a sign-out. So if you just made the role change, wait 15 minutes for Teams, and do a sign-out/sign-in cycle for Outlook. If it's been longer than that and the permissions still aren't reflecting, check whether the role change was saved correctly in Dynamics 365 by having the admin verify it independently.
Does Microsoft Sales Copilot work with Dynamics 365 on-premises?
No, this is a hard limitation, not a configuration issue. Sales agent is not supported with Microsoft Dynamics 365 Customer Engagement (on-premises). It only works with cloud-based CRM platforms, specifically Dynamics 365 Sales (cloud) and Salesforce Sales Cloud. If your organization runs an on-premises Dynamics deployment, you'll need to migrate to Dynamics 365 Sales in the cloud before Sales agent is an option. This is something worth factoring into your cloud migration roadmap if you're evaluating Sales agent as a capability.
Can I use Microsoft Sales agent if my organization is in a Government Community Cloud (GCC) environment?
Not currently. Microsoft Sales agent is explicitly not supported in Government Community Cloud (GCC), GCC High (USG), or Department of Defense (DoD) environments. This isn't something that can be worked around through configuration, it's a product availability decision. If your organization is in one of these environments and needs AI-assisted sales tooling, you'll need to monitor Microsoft's official release planner for when GCC support becomes available, or evaluate alternative solutions. Check the Copilot international availability report in Microsoft's documentation for the latest supported geographies.
What admin role do I need to install and set up Microsoft Sales agent for my organization?
You need a Microsoft 365 admin role to install and deploy Sales agent, regular users cannot install it themselves. Specifically, a Global Administrator or Exchange Administrator in the Microsoft 365 admin center handles the app deployment side. On the CRM side, Dynamics 365 admins need either the System Administrator or System Customizer security role to customize Sales agent settings like field configurations and AI feature setup. For Salesforce environments, separate Salesforce admin permissions are required on that platform. If you're using custom security roles in either CRM, additional Sales agent-specific privileges need to be manually added to those roles, it doesn't happen automatically.