Revised 08/21/2026
Although both use Microsoft AI technology, they are licensed, deployed, and managed differently. Understanding these differences can help organizations determine which AI capabilities are available, how they are enabled, and whether access can be restricted to specific users.
Microsoft Copilot is a Microsoft-provided feature that can be used alongside akoyaGO; Microsoft manages its functionality, behavior, configuration, and support.
- Summary
- Microsoft 365 Copilot
- Dynamics 365 and Power Platform Copilot Features
- Comparing the Two Models
Summary
Organizations can deploy Microsoft AI capabilities in different ways depending on the product being used.
Key Points
Microsoft 365 Copilot is licensed and assigned to individual users. Organizations can provide access to selected staff members without enabling it for the entire tenant. Microsoft recommends using pilot groups as part of the deployment process. Microsoft 365 Copilot includes AI capabilities in applications such as Word, Excel, Outlook, PowerPoint, Teams, OneNote, and Microsoft 365 Chat. Access is primarily controlled through user license assignments. Dynamics 365 and Power Platform Copilot features are separate from Microsoft 365 Copilot and are typically enabled through environment, tenant, or feature-level configuration settings within the Dynamics and Power Platform administration experience. Even when a Dynamics 365 Copilot feature is enabled, existing security roles and permissions may still limit user access. Users can only access data they already have permission to view. Microsoft licensing, deployment, and administration requirements vary by Copilot product and feature. Organizations should review Microsoft's documentation for the specific Copilot capability they intend to implement.
Bottom Line: Organizations that want to introduce AI gradually often begin by assigning Microsoft 365 Copilot licenses to a limited group of users, while separately evaluating Dynamics 365 and Power Platform Copilot features that may require tenant-level or environment-level configuration.
Capability | Can Be Enabled for Specific Users? | Can Be Enabled Tenant/Environment Wide? |
Microsoft 365 Copilot | Yes | Not typically deployed through tenant-wide licensing |
Microsoft 365 Copilot Pilot Groups | Yes | No |
Dynamics 365 Copilot Features | Depends on feature | Commonly Yes |
Power Platform Copilot Features | Depends on feature | Commonly Yes |
Security Role Access to Copilot Features | Yes | No |
Microsoft 365 Copilot
Microsoft 365 Copilot is Microsoft's AI assistant for productivity applications including:
Word, Excel, PowerPoint, Outlook, Teams, OneNote, and Microsoft 365 Chat.
Microsoft 365 Copilot uses Microsoft Graph and organizational content that users already have permission to access to provide AI-assisted productivity experiences. Microsoft documents Microsoft 365 Copilot as a licensed Microsoft 365 service that can be assigned to users through Microsoft 365 administration tools.
Deployment Model
Microsoft 365 Copilot licenses can be assigned to:
Individual users, Groups of users, Pilot programs, and selected departments.
Organizations may deploy Microsoft 365 Copilot to a subset of users rather than the entire tenant. Microsoft's deployment guidance specifically recommends pilot testing with a selected group of users before broader rollout.
User-Specific or Tenant-Wide?
Setting | Scope |
Microsoft 365 Copilot license assignment | User-specific |
Group-based license assignment | User-specific (via group membership) |
Pilot deployments | User-specific |
Microsoft 365 security and compliance configuration | Tenant-wide administrative settings |
Dynamics 365 and Power Platform Copilot Features
Dynamics 365 and Power Platform products include their own Copilot capabilities.
Examples may include:
AI-generated record summaries, Natural language queries, AI-assisted form creation, AI-assisted workflow generation, AI-powered analysis, and recommendations.
Microsoft documentation and Dynamics training materials indicate that organizations must typically enable these features within their Power Platform or Dynamics environment before users can access them.
Important: The specific Copilot features available vary by product, licensing model, and Microsoft's release schedule.
Deployment Model
Unlike Microsoft 365 Copilot, many Dynamics 365 Copilot features are controlled through environment settings within Power Platform and Dynamics administration tools. Depending on the feature, administrators may:
Enable a Copilot capability for an environment, enable preview features for a tenant, Control access through security roles, and Control access through application permissions.
Because individual Dynamics Copilot features are managed differently, organizations should review Microsoft's documentation for the specific feature being enabled.
User-Specific or Tenant-Wide?
Setting | Scope |
Enable Copilot feature in a Dynamics environment | Typically environment-wide |
Enable Power Platform Copilot capability | Often tenant-wide or environment-wide |
Security role permissions for accessing functionality | User-specific |
Access to records and data used by Copilot | User-specific through existing security roles |
Important: Enabling a Dynamics 365 Copilot feature for an environment does not necessarily mean every user can use it. Microsoft security roles and permissions continue to govern access to data and functionality.
Comparing the Two Models
Area | Microsoft 365 Copilot | Dynamics 365 / Power Platform Copilot |
Primary Use | Productivity apps | Business application experiences |
Examples | Outlook, Teams, Word, Excel | Record summaries, AI assistance within Dynamics |
Licensing | User-based licenses | Varies by product and feature |
Can be enabled for specific users only? | Yes | Depends on feature and security model |
Requires tenant or environment configuration? | Yes | Yes |
Controlled by license assignment? | Primary Method | Not always |
