Skip to content

What's actually in your default environment (and why it matters before Copilot)

Every tenant has a default environment where anyone can build. Here is what usually accumulates there, and five checks you can run in an afternoon.

29 Sept 20265 min read

Every Microsoft 365 tenant has a default environment, and every user in the tenant can build in it from day one. That is by design: Microsoft wants people to start making apps and automations without asking permission. The consequence is that in many organisations the default environment has quietly become the place where business-critical apps live.

Before you switch on Copilot, it is worth knowing what is in there. Not because the default environment is dangerous in itself, but because it is where governance gaps concentrate.

What accumulates in the default environment

Open the Power Platform admin center and look at the inventory for the default environment. In most tenants we see, you will find a mix of the following.

  • Personal experiments that were never deleted: a flow that copies emails to a SharePoint list, a canvas app left over from a training course.
  • Departmental apps that grew into something the team now depends on, built by one person who has since changed roles.
  • Flows running under a personal account, which fail the day that person leaves or changes their password.
  • Apps connected to sensitive sources such as HR lists, finance spreadsheets or a SQL database, with no review of who can reach them.
  • Apps shared with broad audiences, sometimes with a whole security group, because it was the quickest way to get them working.

None of this is unusual. It is what a platform designed for easy building looks like after a few years of use.

Why it matters before Copilot

Copilot and Copilot Studio agents work with the data and connectors your tenant already exposes. An agent built in the default environment can use the same connectors and knowledge sources that makers already use. If the connectors are not governed and the data is not labelled, the agent inherits the gaps.

There are three questions worth answering before a rollout.

  1. Who can build and publish agents, and where? If the answer is "anyone, in the default environment", that is the first thing to change.
  2. Which connectors can an agent or flow use? Without a data loss prevention (DLP) policy that separates business from non-business connectors, a single flow can move data between systems that should never meet.
  3. Who owns what is running? An app or agent with no owner cannot be reviewed, patched or switched off.

How to look at it this week

You do not need a project to get a first picture. Your Power Platform administrator can do the following in an afternoon.

  1. Open the inventory in the Power Platform admin center and filter the default environment by apps and flows.
  2. Sort by owner and look for names of people who no longer work at the company.
  3. Check which DLP policies apply to the default environment, and whether any exist at tenant level.
  4. List the connectors used by the largest apps and flag anything that touches HR, finance or customer data.
  5. Check whether Managed Environments is switched on anywhere, and who decided that.

If one of those steps takes more than an afternoon, or turns up something unexpected, you have your answer on whether a closer look is needed.

What good looks like

A well-governed tenant does not ban the default environment. It treats it as a personal productivity space and keeps production apps elsewhere. In practice that means:

  • a small set of named environments for development, testing and production
  • a DLP policy on the default environment that is stricter than elsewhere
  • default environment routing, so new makers get their own space instead of a shared one
  • an owner recorded for every app, flow and agent that matters
  • a short, plain-language guide for makers on where to build what

Moving things is the delicate part. Apps have users, flows have connections, and solutions have dependencies. That is why we move things in waves, and why we start with a read-only scan rather than a clean-up.

The short version

The default environment is not the problem. Not knowing what is in it is the problem. Look first, decide second, and move things only when you know who depends on them.

If you would like a second pair of eyes, our Governance Scan does exactly this review in 2-3 weeks. It is read-only, and it ends with a ranked list of what to fix first.

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.