Welcome to this week’s edition.

Over the last 3 to 4 years, I’ve worked with multiple customers introducing Copilot and Power Platform into their business.

Sometimes Microsoft vouchers kicked things off. Sometimes a company bought hundreds or thousands of licences. Sometimes they only wanted Copilot connected to an existing platform or on-prem solution to get access to Microsoft 365 data and services.

The architecture changes a lot depending on the use case, licensing model, scale and how deeply Copilot should be integrated.

But the annyoing part usually starts when Copilot is already there.

A lot of companies rolled it out with the mindset:

“Let people test it first, we’ll govern it later.”

Let’s get briefly into it ~

Most firms just test it and leave their agents somewhere & later usually means:

At that point, the first question is not even “How do we migrate?”

It is:

What do we actually have?

Which agents are still used?

Which ones are personal?

Which ones have quietly become enterprise applications?

Who owns them?

Which data sources do they access?

And which ones should simply disappear?

The migration approach I now use is basically:

Inventory → Classify → Assign Owners → Build the Target Model → Pilot → Test → Release → Scale

Every existing agent gets classified as personal, enterprise or obsolete.

Anything that becomes an enterprise agent needs a named Agent Owner and Data Owner, a documented audience, reviewed connectors and data sources and a proper lifecycle through DEV → TEST → PROD.

Microsoft does not let you delete the Default Environment.

So the goal is to contain it, stop treating it as the production workspace and give makers a better place to build.

One thing I learned from doing this repeatedly:

Do not try to migrate everything at once!

Take one representative enterprise agent through the entire lifecycle first.

Build it in DEV.

Move it through TEST with real business testers.

Deploy it to PROD.

Run the smoke test.

Even test the incident and hotfix path once.

Then automate and migrate the rest.

Since I kept running into the same problems with different customers, I turned the templates and processes I use into a full Enterprise Copilot Studio Migration Playbook.

It covers:

If you are leading customers through a Copilot rollout, or you are currently staring at a Default Environment full of agents nobody properly owns, the full PDF is linked below. 👇

See you in the next one.

–Rami