Governance — the three-way split

The last card in Domain 3, and one of the most practically useful on the whole
deck. Three governance questions that sound like one, and are controlled in
different places.

Three questions, three places

Who may CREATE agents is controlled in Power Platform, through environment
security roles plus environment routing.

Who may USE agents is controlled in the Microsoft 365 admin centre, under
Copilot → Settings → Data access → Agents → User access.

Who may SHARE Agent Builder agents is also in the Microsoft 365 admin centre,
as an allow-list of specific users or groups.

Learn which lever lives where. A question that describes a creation problem and
offers a Microsoft 365 answer is testing exactly this.

The trap in the platform itself

The blunt Microsoft 365 toggle couples create and use. Turn it off for a group
of users and those users also lose the ability to use agents — including ones
they had nothing to do with building.

So avoid it, and separate the two in Power Platform instead. That is the clean
split, and the exam rewards knowing it.

Why create lives in Power Platform

Even lightweight Agent Builder agents save into a Power Platform environment. The
environment is therefore where creation is genuinely governed, whatever surface
the maker thinks they are using. Route makers to a designated environment and the
control follows them.

Sharing is an allow-list

There is no per-user deny. To block a few people, you allow everyone else —
invert it with a group.

And it applies to new sharing only; existing shares persist. So switching it
on is not remediation, and anything already shared needs dealing with separately.

Environment strategy

Separate by purpose — development, test, production, and a sandbox where
makers can learn without consequence.

Separate by risk — consequential or customer-facing agents get their own
environment, and third-party AI components are isolated deliberately.

Make the paved road easy — routing sends new makers somewhere governed by
default, and a register records what exists and who owns it. The same principle as
card 6: the compliant path should be the convenient one.

Exam trap. "Turn off agent access for those users" is the option that looks
right and is wrong. Use and create are coupled by that toggle — the clean split
is a security role in the Power Platform environment for create, while user
access in the Microsoft 365 admin centre stays open.

The one line to carry: create is a Power Platform question, use and share are
Microsoft 365 questions, and the blunt toggle that seems to solve both breaks one.

---

That completes Domain 3, the largest block on the exam. The thread running through
all eleven cards: measure correctness separately from activity, diagnose before
changing anything, and prefer controls that cannot be argued with over
instructions that can.

---

Currency (19 Aug 2026). Entra Agent IDs can now be created automatically per agent
(preview), which scopes connector permissions, Conditional Access and DLP governance to
an individual agent rather than to its maker. That is the tightest version of the
three-way split this card describes. See cards 42 and 44.