Require Users to Use Entra ID Auth to Interact with Agents
Implementation Effort: Medium – IT must configure agent authentication flows, consent, and app registrations that tie interactive agents to Entra ID, but this is a one‑time project rather than an ongoing program.
Discover and inventory existing agents in Agent 365 Registry
Implementation Effort: Low – Agent Registry is available in the Microsoft 365 admin center; Microsoft-built and Copilot Studio agents are automatically registered and require no manual onboarding.
Triage Discovered Agents and Establish Ownership
Implementation Effort: Medium – Requires cross-team coordination to assess agents and assign accountability.
Design Conditional Access Posture for Agents
Implementation Effort: Medium – Requires mapping all agent access patterns across the Microsoft Entra Agent ID architecture and defining a policy structure before any enforcement begins.
Design Identity Governance Access Controls for Agents
Implementation Effort: Medium – Requires cross-team alignment between identity governance administrators, security architects, and business stakeholders to define the governance model before any operational controls are deployed.
Create Custom Security Attributes for Agent and Resource Classification
Implementation Effort: Medium – Requires defining an attribute taxonomy across agent identities and target resources, coordinating with application owners to tag resources, and assigning attributes to agents through the Agent Registry or Entra admin center.
Enable ID Protection and Deploy Risk-Based Conditional Access for Agents
Implementation Effort: Low – ID Protection for agents is enabled at the tenant level with minimal configuration; the risk-based CA policy follows a standard template.
Deploy Attribute-Based Conditional Access Policies for Agents
Implementation Effort: Medium – Requires custom security attributes to be in place on both agents and resources, and careful policy design to avoid blocking legitimate agent flows.
Establish Agent Publishing and Certification Standards
Implementation Effort: Medium – Requires cross-team alignment between security, platform engineering, and development teams to define publishing standards, certification criteria, and observability instrumentation requirements.
Publish Discovered Agents to Agent Registry
Implementation Effort: Low – Registry publication is a straightforward administrative action per agent once discovery is complete.
Organize Discovered Agents with Registry Collections
Implementation Effort: Low – Collections are a lightweight organizational feature that can be configured quickly once agents are published.
Assign Sponsors and Owners to Agent Identities
Implementation Effort: Medium – Requires identifying the right human accountable for each agent identity across potentially many teams, and establishing an operational process for ongoing sponsor assignment as new agents are deployed.
Create Access Packages for Agent Resource Assignments
Implementation Effort: Medium – Requires defining catalogs, selecting resource roles, configuring approval policies, and setting expiration and lifecycle rules for each access package.
Configure Lifecycle Workflows for Sponsor Mover/Leaver Scenarios
Implementation Effort: Medium – Requires configuring lifecycle workflow templates in Microsoft Entra ID Governance and integrating them with the organization's existing joiner/mover/leaver processes.
Inventory workload identities with agent-like behavior
Implementation Effort: Medium – Requires reviewing existing managed identities and service principals across Azure subscriptions to identify those exhibiting autonomous, agent-like behavior patterns.
Triage workload identities as agent candidates
Implementation Effort: Medium – Requires cross-team evaluation of inventoried workload identities against migration criteria, including risk level, permission scope, and operational autonomy.
Migrate agent-candidate workloads to agent identities
Implementation Effort: High – Requires coordinated migration of workload identities to the agent identity framework, including re-registration in Agent Registry, permission reassignment, and validation of downstream service dependencies.
Enable Global Secure Access for Copilot Studio Agents
Implementation Effort: Low - Enable supported environment forwarding after prerequisites and pilot planning are complete.
Update Existing Copilot Studio Connectors to Route Through Global Secure Access
Implementation Effort: Medium - Requires identifying all existing Copilot Studio custom connectors and editing each one to apply the Global Secure Access routing configuration; new connectors inherit routing automatically.
Configure GSA dashboard for generative AI app visibility
Implementation Effort: Low – Dashboard is available in the Microsoft Entra admin center once Global Secure Access is configured; requires reviewing widgets and applying the generative AI filter.
Configure AI Destination, Source-Type, and HTTP-Method Filtering
Implementation Effort: Medium - Define AI destination rules, supported source conditions, policy assignments, and pilot tests.
Activate Baseline Security Policies for Copilot Studio Agent Traffic
Implementation Effort: Low - Attach approved policies and verify runtime decisions after routing is established.
Configure Inline Prompt Injection Protection with Global Secure Access
Implementation Effort: Medium - Configure acquisition, TLS inspection, prompt rules, conversation schemes, and policy assignment.
Extend Prompt Injection Protection to Custom JSON-Based AI Endpoints
Implementation Effort: Medium - Map each supported application's request format and validate extraction and enforcement.
Enable Microsoft Purview Audit for AI interactions
Implementation Effort: Low – Audit logging is on by default for most Microsoft 365 organizations; verification and enablement require a single PowerShell command or portal action.
Deploy DSPM Overview and Get Started Prerequisites
Implementation Effort: Low – Data Security Posture Management (DSPM) is a built-in Microsoft Purview capability that requires license activation and minimal configuration; no agents or infrastructure deployment needed.