Microsoft Copilot for M365: What It Can and Cannot Do With Your Business Data

Microsoft 365 Copilot promises to "work alongside you, embedded in the Microsoft 365 apps you use every day." For organizations already invested in Microsoft 365, Copilot feels like a natural extension.

But enterprises are discovering limitations. Copilot works within Microsoft 365—but business data lives across many systems, and cross-system understanding is where Copilot struggles.

What Copilot for M365 Does

Microsoft 365 Copilot integrates with:

Microsoft 365 apps: Word, Excel, PowerPoint, Outlook, Teams Microsoft Graph: Your emails, files, chats, calendar, contacts SharePoint and OneDrive: Documents you have access to

Copilot capabilities:

• Summarize email threads
• Draft documents and presentations
• Answer questions based on your Microsoft 365 data
• Generate meeting notes and action items
• Analyze Excel data

This is real productivity value for Microsoft 365 workflows.

Where Copilot Falls Short

Cross-System Blindness

Copilot sees Microsoft 365. Your business lives in many systems:

What Copilot can't see:

• Your ERP (SAP, Oracle, NetSuite)
• Your CRM (Salesforce, HubSpot) — unless using Dynamics
• Your HR system (Workday, SAP SuccessFactors)
• Your domain-specific systems
• Your data warehouse

A question like "What's our revenue exposure to Acme Corporation?" requires data from Salesforce (deals), NetSuite (invoices), and SharePoint (contracts). Copilot sees one piece.

No Entity Resolution

Copilot searches for text. It doesn't understand entities.

The problem:

• "Acme Corporation" in a Word document
• "ACME" in an email subject
• "Acme Corp" in a Teams message
• These are unrelated strings to Copilot

Copilot might find some of these. It won't understand they're the same customer and aggregate accordingly.

Document-Level, Not Knowledge-Level

Copilot retrieves documents. It doesn't have a knowledge model.

What this means:

• Good at: "Find documents about the Johnson project"
• Poor at: "Who is accountable for the Johnson project and what's the current status?"

The second question requires understanding project entities, accountability relationships, and status attributes—not just finding relevant documents.

Permission Complexities

Copilot respects Microsoft 365 permissions. This is a feature (security). It's also a limitation.

The challenge:

• Information about Acme might be in documents you don't have access to
• Copilot can only search what you can see
• Complete answers might require cross-permission synthesis

Copilot won't tell you about information you can't access—even if a complete answer requires it.

Real-World Experience

Organizations report consistent patterns:

Works well for:

• Email summarization
• Meeting notes and follow-ups
• Document drafting assistance
• Calendar management
• Simple SharePoint search

Struggles with:

• Questions requiring cross-system data
• Entity-level understanding (customers, products, projects)
• Historical context across conversations
• Aggregation across documents and systems
• Verification of factual claims

The pattern: document-level tasks succeed; knowledge-level tasks fail.

Case Study Scenarios

Scenario 1: Customer Preparation

Request: "Prepare me for my meeting with Acme Corporation tomorrow"

What Copilot provides:

• Recent emails mentioning "Acme"
• Documents in SharePoint with "Acme" in the name
• Calendar events with Acme contacts

What Copilot misses:

• Acme's current contract status (in your contract management system)
• Open support tickets (in your ticketing system)
• Revenue trends (in your CRM/ERP)
• Recent service issues (in your operations system)

Result: Partial preparation, missing critical context.

Scenario 2: Project Status

Request: "What's the status of Project Mercury?"

What Copilot provides:

• Recent documents mentioning "Project Mercury"
• Teams conversations about Mercury
• Emails with Mercury in the subject

What Copilot misses:

• Project status in your PM tool
• Budget actuals vs. plan (in finance systems)
• Resource allocation (in HR systems)
• Deliverable completion (in project systems)

Result: Fragments of information without authoritative status.

Scenario 3: Policy Question

Request: "What's our policy on remote work for contractors?"

What Copilot provides:

• Documents that mention remote work and contractors
• Potentially multiple conflicting or outdated policies

What Copilot can't do:

• Identify which policy is current
• Know that the 2023 policy supersedes the 2022 version
• Understand policy hierarchy and exceptions

Result: Multiple documents returned without authoritative answer.

The Architecture Gap

Copilot is a powerful tool for Microsoft 365 productivity. It's not a knowledge layer for your enterprise.

Complementary Architecture

To get comprehensive business intelligence:

Keep Copilot for Microsoft 365 productivity:

• Email drafting and summarization
• Document creation
• Calendar management
• Teams integration

Add a knowledge layer for business understanding:

• Entity resolution across all systems
• Cross-system relationship mapping
• Business rules and logic
• Verified current state

Integration approach:

• Knowledge layer connects to all systems (including Microsoft 365)
• Provides context that Copilot can't
• Either as separate interface or integrated augmentation

Questions to Ask

If evaluating Copilot for your organization:

1. What percentage of business knowledge lives in M365? If most critical data is elsewhere, Copilot's value is bounded.

2. Do you need cross-system understanding? If questions require synthesizing data from multiple systems, Copilot alone won't work.

3. Do you need entity resolution? If the same entities appear differently across documents, Copilot won't connect them.

4. What's your accuracy requirement? For high-stakes questions, document retrieval isn't enough—you need verified knowledge.

The Pragmatic Approach

Deploy Copilot for what it does well:

• Microsoft 365 productivity
• Document-level tasks
• Email and calendar management

Plan for the gaps:

• Cross-system data integration
• Knowledge infrastructure for entity understanding
• Verification and governance for critical information

Don't expect Copilot to understand your business. It understands your documents. Those aren't the same thing.

---

See how Phyvant provides cross-system business understanding → Book a call