Copilot NewsdeskIndependent commentary
Your source for all things Microsoft Copilot.
Newsdesk original · 2026-09-15

Copilot made an environment. Surprise, IT.

A Copilot workflow can create an environment you won’t find in the usual list. Here’s where the controls actually live—and why IT deserves a heads-up.

Someone tries a Copilot workflow. Microsoft creates a Power Platform environment. It doesn’t appear in the usual environment list, and you can’t delete it.

Just the sort of surprise IT enjoys with its morning coffee.

According to Microsoft, the first use of a Copilot workflows experience by an appropriately licensed user automatically creates one special workflows environment per organization’s tenant, complete with Dataverse.

The environment is absent from the Power Platform admin center’s environment list and Maker portals. Administrators can still see its workflows in the admin center’s inventory.

So the workflows are there. The environment is there. Just don’t look for the environment where you normally look for environments. Very intuitive.

The controls deserve a closer look

This environment has a fixed data loss prevention policy that allows a limited set of connectors, including Teams, Outlook and SharePoint. Other connectors are blocked. Your normal tenant-level and environment-level DLP policies do not apply to it.

Administrators can disable Workflows agents in the Microsoft 365 admin center. Microsoft says that locks down the whole environment and disables all Copilot workflows experiences inside it.

That distinction matters: there are controls, but assuming your usual policies cover this environment would be a mistake.

We want employees experimenting with useful automation. We also want the people responsible for it to know where it lives, what rules apply, and how to stop it when necessary.

Microsoft, put that explanation beside the button. Finding out how something is governed should not be the second project it creates.

Let people experiment. Give IT the map.

Source: Microsoft’s Copilot workflows environment documentation, updated September 1, 2026; checked September 15, 2026. This concerns the special Copilot workflows environment, not every Copilot feature or Power Platform environment. Commentary on documentation; we have not tested it in a tenant.