Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.2.3. Agent Settings: Types, Sharing, Templates, and User Access

💡 First Principle: Tenant agent settings are defaults applied before any individual decision — which publishers' agents may exist, who may use agents at all, how agents may be shared, and which security policies attach automatically. Get the defaults right and individual approvals become exceptions rather than firefighting.

All of these live under Microsoft 365 admin center > Agents > Settings.

  • Agent and plugin access — the current name for the outline's "allowed agent types". Three checkboxes: allow agents and plugins built by Microsoft, built by your organization, and built by external publishers. Disabled types don't appear in the agent store, except Microsoft-built items, which users still see but can't install. "Plugins" here include tools, MCP servers, connectors and skills.
  • User access — All users (the default), No users, or Specific users or groups: who may use agents at all.
  • Sharing — All users, No users or Specific users. Choosing No users disables organization-wide sharing, but users can still share with specific individuals. This control applies only to agents built with Microsoft Copilot Agent Builder.
  • Agent feedback sharing — whether agent developers receive users' ratings and comments (no agents, all agents or selected agents). It doesn't stop users rating.
  • Tags — up to 50 per organization and 5 per agent, for organizing the registry.
  • Agent management rules — bulk actions: install Microsoft agents, reassign ownerless Agent Builder agents to their creators' managers, block ownerless agents without usage, apply a template, and reject publish requests older than a set number of days.

Templates (Agents > Settings > Templates) attach a bundle of security policies to agents when they're activated:

  • Default templates combine Entra, Purview, SharePoint and Defender policies — among them Purview audit, detection of sensitive information in AI interactions, a Purview AI compliance assessment, identity protection, lifecycle management for agents and restrictions on external sharing. These default policies are locked.
  • Custom templates add Entra policies you must create in Entra first: Conditional Access, access packages and custom security attributes.
  • Template edits apply only to new activations. To bring existing agents into line, run the Apply template agent management rule — a one-time bulk operation over registry agents that have an agent identity.
  • Templates require Microsoft 365 E7 or Agent 365, and the default template assigns the Agent 365 license automatically during activation.

⚠️ Exam Trap: "Set Sharing to No users to stop every agent being shared" is wrong twice: users can still share Agent Builder agents with named individuals, and the setting doesn't govern agents built in other tools.

Reflection Question: You add a Conditional Access policy to your custom agent template, but 300 agents approved last quarter aren't covered by it. Why not, and what's the one-time fix?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned