Agents inherit your tenant’s habits. If SharePoint is overshared, agents will surface it. If you have no DLP, connectors leak. This is the companion to Ways to Build an Agent in Microsoft 365: that page tells you which builder to pick, this one gets the tenant ready so any builder is safe to use. Ten steps, most are configuration, not code.

TL;DR: Do these ten things before opening the floodgates. Each step names the admin who owns it and what to skip if it doesn’t apply. You don’t need all ten for every scenario, so scope it to what you’re actually enabling.

✅ Scope it right: Only enabling SharePoint agents on one site? Steps 1-3 and 10 are enough. Makers using Copilot Studio? Add 4-6. Devs going pro-code/Foundry? Add 7-9. Do what you need, no more.

1) Fix SharePoint oversharing first

🔸 Admin: SharePoint admin. Agents answer with whatever the user can already see, so oversharing becomes agent oversharing. Run Data access governance reports to find overshared sites and “Everyone except external users” (EEEU) exposure, then trigger site access reviews so site owners clean up permissions. This is the single highest-impact step.

🔸 Skip only if your content estate is already tightly permissioned.

2) Turn on the controls that keep sites out of agents and Copilot

🔸 Admin: SharePoint admin.

🔸 Restricted content discovery: hide a whole site from agents and org-wide search (site keeps working; content just isn’t surfaced).

🔸 Restricted access control: lock a site to specific Entra/M365 groups (up to 10 per site). Enable tenant-wide with Set-SPOTenant -EnableRestrictedAccessControl $true; optionally delegate to site admins with Set-SPOTenant -DelegateRestrictedAccessControlManagement $true.

🔸 Requires SharePoint Advanced Management.

3) Protect sensitive data with Purview (labels + DLP)

🔸 Admin: Compliance / Purview admin. Apply sensitivity labels and Microsoft Purview DLP so sensitive items are excluded from agent responses (citations may appear, but the content isn’t used). To govern the .agent file itself, use DLP conditions based on the .agent extension (you can’t label the file directly yet). Extend DLP to block sensitive sharing with external users.

🔸 Skip only if you have no regulated/sensitive content, which is rare.

4) Decide who can build, and set Power Platform environments

🔸 Admin: Power Platform admin. Don’t let production agents live in the Default environment. Create dedicated environments, use environment routing for new makers, and separate dev/test/prod. This is where Copilot Studio agents and their flows live.

🔸 Skip only if no one will use Copilot Studio or Power Automate.

5) Put DLP policies on connectors

🔸 Admin: Power Platform admin. Classify connectors (Business / Non-business / Blocked) with Power Platform DLP so a maker can’t wire a Copilot Studio agent to an unapproved service. Pair with geo/data-residency settings in Copilot Studio where required.

🔸 Skip only if Copilot Studio/Power Platform isn’t in use.

6) Establish connector-failure and reliability patterns for makers

🔸 Admin: Power Platform admin / CoE. Agents that call connectors need to fail gracefully. Standardize the flow-wrapper pattern so a non-2xx status doesn’t become a hard failure the LLM can’t see.

🔸 Skip only if your agents make no external calls.

7) Give agents real identities with Entra Agent ID

🔸 Admin: Entra (Identity) admin. Treat agents as first-class identities, not anonymous scripts. Microsoft Entra Agent ID issues scoped, time-bound tokens (least privilege), and Conditional Access plus Identity Protection apply to agents just like users. Assign each agent an owner/sponsor and a lifecycle so access doesn’t outlive its purpose.

🔸 Essential once autonomous or pro-code agents appear.

8) Define agent blueprints for pro-code and autonomous agents

🔸 Admin: Entra / AI admin. An agent blueprint is the IT-approved template (capabilities, required tool access, security/compliance constraints, audit requirements, linked DLP/logging policies). Every agent instance inherits it, so governance is consistent across mail, calendar, Teams and SharePoint, and shadow agents are prevented.

🔸 Skip only if you’re strictly no-code/low-code for now.

9) Wire up monitoring and threat/data protection

🔸 Admin: Security / Defender + Purview admins. Connect agent telemetry to Microsoft Defender (threat detection, AI agent inventory) and Microsoft Purview (DLP, information protection, compliance/retention). Have dev teams auto-instrument agents for observability so you don’t hand-write monitoring code.

10) Stand up Microsoft Agent 365 as the control plane

🔸 Admin: Global or AI Administrator. This is the layer that ties 1-9 together across every builder. In the Microsoft 365 admin center, Agents, use the registry, Agent Map (E7 + Global/AI Admin) and hero metrics to discover, approve, own and retire agents through one IT-controlled flow. Agent 365 governs agents regardless of where they were built: Copilot Studio, SharePoint, Foundry, Agents SDK, LangChain, even Bedrock/Vertex. Included in Microsoft 365 E7 or as a standalone subscription.

Quick “what do I actually need?” map

Your situation	Do these steps
One SharePoint agent on one site	1, 2, 3, 10
Business users using Agent Builder	1, 3, 10
Makers using Copilot Studio	1-6, 10
Pro-code / Foundry / autonomous agents	1, 3, 7, 8, 9, 10
Full enterprise rollout	All 10

🛠️ FAQ

Do I need Microsoft Agent 365 to start? No, you can secure individual paths with SharePoint/Purview/Power Platform controls. But once agents multiply across builders, Agent 365 is what prevents sprawl and gives one place to observe, govern and secure them. It’s in E7 or standalone.

What’s the very first thing to do? Fix SharePoint oversharing (step 1). Agents amplify existing permission problems faster than anything else.

Which admin roles are involved overall? SharePoint admin, Compliance/Purview admin, Power Platform admin, Entra (Identity) admin, Security/Defender admin, and a Global or AI Administrator for tenant-wide agent governance and the Agent Map.

We’re no-code only. Can we skip Entra Agent ID and blueprints? For now, yes. Steps 7-8 matter most for autonomous/pro-code agents. Revisit them the moment devs or autonomous agents enter the picture.

🔗 Related

🔸 Ways to Build an Agent in Microsoft 365, which builder to pick (the companion to this checklist).

🔸 M365 Copilot vs Copilot Studio, which Copilot builds agents that take action.

🔸 Computer use (CUA) in Copilot Studio, govern agents that operate apps by sight.

🔸 All AI & Copilot tips · Knowledge base overview

Sources: Microsoft Learn: SharePoint (manage access to agents, restricted access control, restricted content discovery, data access governance, SharePoint Advanced Management), Microsoft Purview DLP, Power Platform (environments, DLP, environment routing), Microsoft Entra Agent ID and ID governance, Microsoft Defender (AI agent inventory), and Microsoft Agent 365 (overview, admin center Agents, Agent Map, agent blueprint, licensing). Details reflect Microsoft Learn at time of writing and evolve quickly, so always confirm current capabilities and licensing in the official documentation.