This post is a part of the AB-900: Microsoft 365 Copilot and Agent Administration Fundamentals Exam Prep Hub.
This topic falls under these sections:
Perform basic administrative tasks for Copilot and agents (25–30%)
--> Perform basic administrative tasks for agents
--> Identify how to configure user access to agents
Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.
Introduction
In Microsoft 365 Copilot, agents are specialized AI assistants designed to perform focused tasks such as answering domain-specific questions, retrieving organizational knowledge, or executing workflows. Because agents can access organizational data and systems, controlling who can use them and under what conditions is a critical administrative responsibility.
Configuring user access ensures that the right users can interact with the right agents while maintaining security, compliance, and least-privilege principles.
1. What “agent access” means
User access to agents determines:
- Which users can discover an agent
- Which users can interact with or run an agent
- Whether an agent is available organization-wide or restricted to specific groups
- Whether external or guest users can use agents (if allowed)
Access is typically controlled through a combination of:
- Microsoft 365 identity and access controls
- Entra ID (Azure AD) group membership
- Copilot and agent-specific policies
2. Key methods to configure access to agents
A. Assigning access via Microsoft Entra ID groups
One of the most common approaches is group-based access control.
Administrators can:
- Assign an agent to specific security groups or Microsoft 365 groups
- Restrict usage to departments (e.g., HR, Finance, IT)
- Manage access at scale without assigning users individually
Benefits:
- Scalable management
- Easier onboarding/offboarding
- Centralized governance
B. Tenant-wide vs scoped availability
Agents can be configured as:
1. Tenant-wide agents
- Available to all licensed users in the organization
- Used for general productivity scenarios (e.g., company policy assistant)
2. Scoped agents
- Limited to specific users or groups
- Used for sensitive or department-specific data (e.g., HR policy agent)
C. Role-based access control (RBAC)
Some agent administration actions require specific roles in Microsoft 365 or Entra ID:
- Global Administrator
- AI Administrator / Copilot Administrator
- Service-specific admin roles
RBAC ensures:
- Only authorized admins can publish or modify agents
- Governance over agent deployment lifecycle
D. Conditional Access policies
Conditional Access can indirectly control agent usage by enforcing:
- Device compliance requirements
- Multi-factor authentication (MFA)
- Location-based restrictions
- Risk-based sign-in rules
This ensures that even if a user has access to an agent, they must meet security requirements before using it.
E. Application and permission scopes
Agents may require access to:
- Microsoft 365 data (SharePoint, Outlook, Teams)
- External connectors or APIs
- Graph permissions
Administrators control:
- What data the agent can access
- Whether consent is required
- Whether permissions are user-delegated or app-level
3. Lifecycle considerations for agent access
Provisioning
- Define target audience (group or tenant-wide)
- Assign initial permissions
- Validate compliance requirements
Modification
- Update group membership to change access
- Adjust policies as organizational needs evolve
Deprovisioning
- Remove users or groups when no longer needed
- Disable or retire the agent if required
- Ensure data access is revoked appropriately
4. Governance best practices
To securely manage agent access:
- Use least privilege access (only necessary users/groups)
- Prefer group-based assignment over individual assignment
- Regularly review agent usage and permissions
- Restrict sensitive agents to controlled departments
- Monitor access logs for unusual activity
- Align with Microsoft Purview policies where applicable
5. Common use cases
- HR agent accessible only to HR staff
- IT helpdesk agent available to all employees
- Finance reporting agent restricted to finance team
- Executive summary agent limited to leadership group
6. Key exam takeaway
For AB-900, remember:
- Agent access is primarily controlled through Entra ID groups, roles, and policies
- Access can be tenant-wide or scoped
- Security is enforced through RBAC and Conditional Access
- Governance ensures agents are only available to the appropriate users
Practice Exam Questions (10)
1.
What is the most common method used to manage user access to Microsoft 365 agents at scale?
A. Individual user assignment
B. Local device policies
C. Entra ID group-based assignment
D. DNS configuration
Answer: C
Explanation: Entra ID group-based assignment is the scalable and recommended way to manage agent access.
2.
Which configuration limits an agent to only HR department users?
A. Tenant-wide publishing
B. Scoped group assignment
C. Public sharing link
D. Guest user activation
Answer: B
Explanation: Scoped assignment using groups restricts access to specific departments like HR.
3.
Which role is typically required to manage Copilot or agent deployment settings?
A. SharePoint Site Owner
B. Global Administrator
C. Teams Guest User
D. Exchange Recipient User
Answer: B
Explanation: Global Administrators (or similar privileged roles) manage high-level agent deployment settings.
4.
What is the purpose of Conditional Access in relation to agent usage?
A. To increase storage capacity
B. To control data indexing speed
C. To enforce security requirements before access
D. To create new agents automatically
Answer: C
Explanation: Conditional Access ensures users meet security conditions like MFA or device compliance.
5.
What happens when a user is removed from an Entra ID group assigned to an agent?
A. They retain permanent access
B. Their access is automatically revoked
C. The agent is deleted
D. The entire tenant loses access
Answer: B
Explanation: Group membership changes immediately affect access to assigned resources, including agents.
6.
Which access model makes an agent available to all licensed users in a tenant?
A. Scoped access
B. Tenant-wide access
C. External sharing mode
D. Device-based access
Answer: B
Explanation: Tenant-wide access allows all licensed users to use the agent.
7.
Which control helps restrict what data an agent can access?
A. Network firewall rules
B. Permission scopes and Graph permissions
C. Printer access policies
D. Windows registry settings
Answer: B
Explanation: Permission scopes define what data and services an agent can access.
8.
What is a key benefit of using group-based access for agents?
A. It disables auditing
B. It simplifies scalable management
C. It removes the need for authentication
D. It bypasses licensing requirements
Answer: B
Explanation: Group-based access simplifies administration, especially in large organizations.
9.
Which scenario best describes proper agent governance?
A. All users can create unrestricted agents
B. Agents are available without authentication
C. Sensitive agents are limited to specific departments
D. Agents bypass compliance policies
Answer: C
Explanation: Sensitive agents should be restricted to appropriate departments for security and compliance.
10.
What is a recommended best practice when configuring access to agents?
A. Assign access individually to each user
B. Use least privilege access principles
C. Allow anonymous access by default
D. Disable group usage entirely
Answer: B
Explanation: Least privilege ensures users only get the access they need, improving security and governance.
Go to the AB-900 Exam Prep Hub main page
The Data Community 