In short
Create a dedicated environment group and a dedicated data policy for development. Copy production's rules exactly, verify the copy, then change one thing at a time and write each change down. Only then move the development environment in.
Why the shared group bites
Environment group rules, including advanced connector policies, are set at group level. Once an environment is in a group, its own settings for those rules are locked. A classic data policy, likewise, applies to every environment in its scope.
So the moment a builder needs one more connector in development, the only place to grant it is a policy that production also obeys. Most teams either refuse the builder or quietly loosen production. Neither is acceptable.
Copy production, exactly
- Inventory what production uses. List the rules on the production group and, for each, its values. For the connector policy, record every allowed connector and every action switched off on each connector. For classic data policies, record Business, Non-business, the default group and custom connector patterns.
- Create the new group and add the same rules. New rules start with defaults, not with production's values. Treat every rule as wrong until you have checked it.
- Rebuild the allow list and remove the extras. A new connector policy preloads a default set of connectors. Some of them may be ones production deliberately removed. Ours arrived with nine connectors and a legacy Dataverse connector that production did not allow.
- Mirror the blocked actions. This is the step most people skip. In our production policy, ten connectors had actions switched off, from Teams administration actions to raw HTTP requests in Outlook and Azure DevOps pipeline runs. A copy without them is quietly more permissive.
- Match the small toggles. Agent channels, external artefact deployment and IP cookie binding all had different defaults from production in the new group.
- Apply, then move the environment in. Apply the rules to the empty group first, so the environment is governed from the second it arrives.
A copy you have not compared line by line is not a copy. It is a guess with production's name on it.
Do the same for classic data policies
If the tenant still runs classic data policies alongside the connector policy (mixed mode), development needs its own one too. Create it scoped only to the development environment, reproduce production's groups, add what development needs, and only then remove development from the shared policy. In that order, the environment is never ungoverned, because while both apply the stricter result wins.
Name the policy after the group, so anyone can see which rules belong together.
Write the difference down
The value of a separate development group is that the difference from production is small and known. Keep a one-page baseline that lists, for development only:
- every connector allowed in addition to production, and why;
- every action switched on that production keeps off, and why;
- what stays blocked on purpose, and what would justify opening it.
In our case the first difference was a single action: SharePoint's HTTP request. Everything else matched production until a specific agent needed more.
When to automate it
Doing this by hand is fine once. If you will run several groups, the Power Platform API exposes connector policies and environment groups, so a baseline can be copied from one group to another and checked automatically. Until then, keep the comparison as a checklist and repeat it after every change to production.
Checklist
- Development has its own environment group and its own data policy.
- Allow lists match production, including removed defaults.
- Blocked actions match production, connector by connector.
- Rule toggles match production.
- Rules were applied before the environment was moved in.
- Every difference from production is written down with a reason.
Sources
- Environment groups, Microsoft Learn
- Advanced connector policies, Microsoft Learn
- Tenant environment strategy, Microsoft Learn
- Manage advanced connector policies programmatically, Microsoft Learn