Power Platform security in 2026: 8 settings to check

1. Data policies: who talks to whom

What used to be called DLP policies are now data policies. Every connector belongs to one of three groups: Business, Non-Business or Blocked. An app or flow can’t mix Business and Non-Business connectors, and a Blocked connector doesn’t work at all.

New connectors go to Non-Business by default. Decide what is allowed instead of chasing what isn’t.
An environment policy can’t override a tenant policy. When several policies apply, the most restrictive one wins.
Some Microsoft connectors, such as SharePoint and Office 365 Outlook, can’t be blocked in classic policies.
Custom connectors are classified by URL pattern. In the shared environment, Microsoft recommends blocking all of them.

2. The default environment

Every user who signs in to Power Platform becomes a Maker in the default environment, and it can’t be deleted. Microsoft recommends:

Renaming it to Personal Productivity, so it’s clear it isn’t meant for business systems.
A strict data policy there: Blocked as the default group, the connectors that can’t be blocked in Business, everything else blocked.
Turning on environment routing, which sends each maker to a personal developer environment (requires premium licensing).
Restricting who can create new environments.

3. Tenant isolation: block connections to other tenants

By default, a user can connect a flow to an account in another tenant, such as a mailbox in an outside organization, and send data to it. Tenant isolation blocks such connections in both directions, with an allowlist. It’s off by default, under Security > Identity and access > Tenant isolation.

4. Sharing apps and flows

Share with Everyone is off by default. Keep it that way: while it’s off, only admins can share with the whole organization.
In Managed Environments you can limit sharing: block sharing with security groups, cap the number of individuals, and restrict sharing of agents. Limits apply to new sharing only.
Environment security groups decide which users can access each environment.

5. Conditional Access

MFA and Conditional Access apply to Power Platform too, with one trap: Microsoft Flow Service isn’t part of the "Office 365" target in Conditional Access. If your policy targets Office 365 only, target All cloud apps or add Flow Service. Conditional Access on an individual app is available only in Managed Environments.

6. Copilot Studio agents

Data policies apply to agents too: connectors, knowledge sources, channels and authentication. Block the Chat without Microsoft Entra ID authentication connector so every agent requires sign-in.
Agents can be built by users with a Copilot Studio license, a Microsoft 365 Copilot license, or a trial. E3 users can build basic agents in Teams; to prevent that, turn off the Power Virtual Agents for Office 365 service plan.
Actions such as creating, publishing and sharing an agent are recorded in Microsoft Purview Audit.

7. Monitoring: Audit and the Security page

Activity in Power Apps, Power Automate, Copilot Studio and changes to data policies are recorded in Microsoft Purview Audit. Admin activity logging is on by default.
Dataverse auditing is turned on separately in each environment.
In the Power Platform admin center, Security > Overview shows a security score and recommendations. The score is still in preview, and some recommendations can only be applied in Managed Environments.

8. Email sent by automated flows

A Power Automate flow can send email outside the organization on a user’s behalf. Power Platform doesn’t restrict this itself. The documented approach is an Exchange mail flow rule that matches the x-ms-mail-application header these messages carry, and blocks or flags them.

What needs extra licensing

Setting	Licensing
Classic data policies, tenant isolation, Share with Everyone	Included, no Managed Environments needed
Conditional Access	Entra ID P1 (included in Business Premium, Microsoft 365 E3 and E5)
Managed Environments: sharing limits, per-app Conditional Access, IP firewall	Every active user in the environment needs a premium license (such as Power Apps Premium or Power Automate Premium) or pay-as-you-go
Customer Lockbox, customer-managed key (CMK)	Managed Environments plus Microsoft 365 E5 or a matching add-on

Two dates for your calendar: Microsoft asks you to convert unmanaged developer environments to Managed Environments by 15 December 2026. And from February 2027, users without a qualifying license can’t open apps in managed environments.

Want to know what’s configured in your Power Platform? Griffin31 checks your Microsoft 365 tenant’s security settings continuously, including 16 Power Platform checks, and shows you what to fix first.

Book a demo