Power Platform Admin Plugin for Copilot Cowork

Status: Public Preview — behaviour may change.

What it does

A Microsoft-published plugin that lets people ask Copilot Cowork questions about Power Platform inventory, usage, governance, capacity and licensing. It's read-only: it gives insight and guidance and doesn't carry out admin actions itself. A Microsoft 365 admin installs it from the admin center; each user then connects their own Power Platform account inside Cowork.

Key facts

Install is in the Microsoft 365 admin center under Agents > Tools > Registry, then Power Platform Admin (Preview). Pick the Copilot channel and either all users or specific users and groups.
Installing needs a tenant admin or the Copilot administrator role.
Data access is a separate gate. The account used for the Power Platform for Admins V2 connection needs Global Administrator, Power Platform Administrator or Dynamics 365 Administrator in the target organisation.
Users connect via Customize in Cowork, using an OAuth connection.
Requests surface an Ask Advisor approval card. Users can choose "always allow" for send-message requests, which removes the per-request prompt.
Users can switch the plugin off for their own conversations, but can't uninstall an admin-installed one.
Cowork access itself is controlled separately through a spending policy that includes Cowork; the plugin doesn't grant it.

When to use / skip

Use it as a quick way for Power Platform admins to interrogate the tenant in natural language: which environments exist, what's eating capacity, where sharing looks loose. Skip it as a governance control. It reports on your estate, it doesn't enforce anything, and it's still preview.

Configuration decisions

Install audience: all users is a bad default for an admin-flavoured plugin. A named admin group is usually the right scope.
Whether to leave the "always allow" approval option for users to choose, or coach them to keep the per-request approval.
Who actually holds the three required roles, since that decides who gets real answers.

Gotchas

A user in the install audience without one of the admin roles can install and connect happily, then get nothing useful. Expect support questions that look like plugin faults and are really role gaps.
The plugin installing doesn't mean Cowork is available to that user. Two separate access paths, two separate tickets.
Check which account and organisation you're connecting as before you consent, especially for people who work across tenants.
Preview and read-only: don't build an operating procedure around its answers without checking against the admin center.

Consultant notes

The people who should use this already hold high-privilege roles, so treat the install audience as a privileged-access decision, not a convenience rollout.
Write the "always allow" guidance into your admin runbook before someone clicks it and forgets they did.
In UAT, test with a user who has the role and one who doesn't. The second case is the one the helpdesk will see.
Capacity and licensing answers are a good starting point for a conversation, not a source of truth for a licence true-up.

Worth revisiting when the plugin leaves preview or gains write actions.