In this article, we’ll walk through the configurations required to enable WorkIQ, Cowork, and the integration with Dynamics 365 Finance & Operations, covering each of the components involved in the architecture: Microsoft 365 Admin Center, Power Platform Admin Center (PPAC), Dataverse, Dynamics 365 Finance & Operations, and Microsoft Copilot.
The goal is to gain a complete view of the process, understand the purpose of each configuration, and reach the end with an environment ready for Copilot to work securely and under proper governance with our business data.
🌱 PREREQUISITES
Before enabling features in the Admin Center, PPAC, and Dynamics 365 Finance and Operations, there are a number of foundational conditions that we need to review and fulfill.
Enabling Cowork involves aligning three areas: licensing, billing, and technical configuration. Each of these is usually managed by different people or teams within the organization, so identifying them from the beginning will allow us to move forward in a much more organized way.
Once we have completed this checklist, we’ll be ready to access the administration screens with the necessary foundation in place:
🌿 Microsoft 365 Copilot license active and assigned to each user who will use Cowork: A standard Microsoft 365 license is not enough. The license enables access to the functionality, while consumption is managed separately through Copilot Credits.
🌿 Administrative roles defined: We will need a Global Administrator or Billing Administrator to enable pay-as-you-go billing, configure payment methods, and review user access.
🌿 Azure subscription linked to the Microsoft 365 billing account: You can use an existing subscription or create a new one.
🌿 Usage-based billing: Cowork is billed based on consumption through Copilot Credits: Until pay-as-you-go billing is enabled, Cowork will not be visible to users.
🌿 Spend policy for Cowork and WorkIQ: A user will have access to Cowork if, and only if, they are included within the scope of at least one spend policy that includes Cowork. This policy can be applied to an individual user, a group of users, or everyone.
🌿 «Modern» browserS and access surfaces: Microsoft Edge or Google Chrome are recommended. Cowork is available in m365.cloud.microsoft, Outlook and Teams, the Copilot desktop application for Windows and Mac, and the mobile applications for iPhone and Android.
Now we’re ready to get started…
🌱 ADMIN CENTER
admin.cloud.microsoft.com
🌿 1. ENABLE EXTERNAL MODELS
We can enable Anthropic models as subprocessors and define which users or user groups will have access to these models, or enable access for everyone.
The scope of this configuration is tenant-wide.
2. ENABLE FRONTIER
If we also want early access to test experimental (preview) Microsoft features, we need to enable Frontier (either for all users or for specific users).
3. DATAVERSE DATA AVAILABLE IN MICROSOFT 365 COPILOT
This is the setting that allows Copilot to reason over and act on Dataverse data (Power Apps, Dynamics 365, and Finance & Operations data).
This enables Copilot to search, relate, and reason over the Dataverse tables that each user is already authorized to access.
Copilot can retrieve relevant records, understand relationships between tables, and return responses, summaries, or explanations in natural language.
From the Admin Center, we configure this first step. The second step, which consists of selecting the environments, applications, and tables, will be completed from PPAC (in just a moment):
4. COWORK
If we want Cowork to be able to use Microsoft Edge and browse using users’ authenticated sessions, we need to enable this option.
This allows Cowork to perform actions such as navigating web pages, completing fields, clicking buttons, or extracting data.
This is the path for tasks where no API or connector exists: supplier portals, legacy web applications, customer extranets, or any site that sits behind a corporate login.
Without this configuration, Cowork is limited to what is available through Microsoft Graph, connectors, and plugins.
🌱 PPAC
admin.powerplatform.com
DEFINE WHICH TABLES WILL BE AVAILABLE TO WorkIQ
From PPAC, we need to review which tables we want WorkIQ to be able to search within AI experiences and agents.
To do this, select the environment that contains the data you want to work with and go to Settings.
Select Product > Features.
Here, we must enable Dataverse Model Context Protocol:
Within the advanced settings, we also need to verify that the following capabilities are enabled:
🌿 Dataverse MCP CLI tool
🌿 Microsoft Cowork
(And enable it)
🌱 Microsoft 365 for Finance and Operations
Now we move into D365FnO.
🌿 First, we need to verify that the Dynamics 365 ERP Model Context Protocol Server feature is enabled.
System administration >> Feature management
🌿 We also need to verify that the Cowork ClientId is correctly configured in the Allowed MCP Clients form:
System administration >> Setup >> Allowed MCP clients
This key is usually populated automatically, but if it was not auto-filled, you can enter it manually without any issues. Here it is, ready to copy and paste:
6ab48b67-cd74-4ad4-81af-5932984589be
We also need to verify that it is enabled and set to True.
At this point, the entire ecosystem should already be enabled. So let’s move on to Copilot.
🌱 MICROSOFT COPILOT
Access copilot.microsoft.com from your browser or directly through the application.
First, let’s validate that everything is configured correctly.
At this stage, WorkIQ, External Models, and Cowork should all be available.
Now we enable the connection to our FnO environment within Cowork:
From the settings gear, select your environment:
From Capabilities, we can access information about the available extensions in case we need more detail about what they can do:
And that’s it! Let’s give it a try…
In the next blog of the serie we’ll start the party with real use cases.