Pass the Microsoft 365 Certified: Microsoft 365 and AI Services Administrator Associate AB-650 Questions and answers with ExamsMirror

Microsoft Agent 365 provides centralized governance of tools and Model Context Protocol (MCP) servers that AI agents use to access external services and organizational data.

Option D is correct because the Microsoft 365 admin center ' s Tools management interface enables administrators to block an individual MCP server without disabling the agent or unrelated MCP servers.

In this scenario, MCP2 is currently marked Available but has not completed its security review. Allowing agents to invoke MCP2 could expose procurement information before appropriate security controls have been validated.

Administrators can navigate to the Microsoft 365 admin center, select Agents → Tools → Registry, locate MCP2, and select Block.

Blocking MCP2 changes its availability and prevents agents from using the tools exposed by that server. MCP1 remains available because it is a separate MCP server, and Agent1 itself is not disabled.

Option A is incorrect because agent management rules do not provide the direct server-specific blocking action requested.

Option B is incorrect because the Agent Registry manages agents, whereas the Tools Registry provides MCP server controls.

Option C is incorrect because policy templates are not the direct mechanism for blocking an individual MCP server.

Therefore, blocking MCP2 from Tools satisfies the requirements.

Microsoft References:

https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-plugins-skills-mcp-servers

https://learn.microsoft.com/en-us/microsoft-365/admin/manage/agent-tools-overview

SharePoint Data Access Governance provides reporting capabilities that help administrators identify overshared sites, excessive permissions, and potentially risky content exposure without changing the existing SharePoint authorization configuration.

Option D is correct because Data Access Governance reports can identify sites that have broad access permissions, anonymous sharing links, and permissions granted to large organizational groups.

Administrators can access these reports through the SharePoint admin center under Reports and Data access governance.

The site permissions snapshot report provides visibility into permissioned users, guest access, broken permission inheritance, and sharing links.

Sharing links activity reports can also identify sites where users have created Anyone links, organization-wide links, or externally shared links.

These capabilities are especially important for Microsoft 365 Copilot because Copilot respects existing SharePoint permissions. Overshared content may therefore appear in responses provided to users who have access through excessively broad permissions.

Option A primarily measures site usage rather than evaluating permission exposure.

Option B focuses on classified content rather than analyzing SharePoint site permission structures.

Option C involves reviewing user access assignments, rather than identifying overshared sites across the SharePoint environment.

Option E supports compliance content searches but is not the dedicated solution for detecting broad site permissions.

Data Access Governance reports provide the required visibility without modifying permissions.

Microsoft References:

https://learn.microsoft.com/en-us/sharepoint/data-access-governance-reports

https://learn.microsoft.com/en-us/sharepoint/data-access-governance-site-permissions-report

Review the: Microsoft 365 Copilot credits report; Notify the department by: Adding a budget and alert recipients to the billing policy

Microsoft 365 provides consumption reports and billing policy controls for organizations using pay-as-you-go Microsoft Copilot services.

First selection: Microsoft 365 Copilot credits report.

The Microsoft Copilot Credits report provides detailed information about consumption associated with metered Copilot Chat and agent interactions.

Administrators can access the report through the Microsoft 365 admin center under Reports, Usage, Microsoft Copilot, and Credits.

The report includes credits consumed by individual users, agents, billing policies, and user-agent combinations. These breakdowns help identify unusually high consumption and determine which activities are contributing to increased costs.

Second selection: Adding a budget and alert recipients to the billing policy.

Microsoft 365 pay-as-you-go billing policies support configurable budgets and spending notifications.

Administrators can specify a budget threshold and designate finance personnel as notification recipients. When consumption reaches the configured notification milestones, Microsoft sends email alerts to the designated recipients.

This provides proactive cost visibility without requiring finance personnel to manually inspect consumption reports.

A critical distinction is that billing policy budgets provide notifications rather than hard spending limits. Reaching the budget threshold does not necessarily stop additional consumption or billing.

Therefore, the Credits report provides the consumption breakdown, while the billing policy budget and notification recipients provide threshold-based alerts.

Microsoft References:

https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/message-consumption

https://learn.microsoft.com/en-us/microsoft-365/copilot/pay-as-you-go/setup

Microsoft Entra Conditional Access evaluates applicable policies based on user and group membership, targeted resources, and access controls. It supports nested security groups, and exclusions take precedence over inclusions within the same policy.

Statement 1: Yes.

User2 is a B2B collaboration guest who does not belong to any groups. CA2 includes all users, including B2B guests, and excludes Group1 and Group3. Because User2 belongs to neither excluded group, CA2 applies and blocks access to Payroll.

Statement 2: Yes.

User1 belongs to Group2, which is nested within Group1. Microsoft Entra Conditional Access evaluates nested group memberships, so User1 is treated as a member of Group1. Consequently, CA1 applies and requires MFA. CA2 does not apply because User1 is indirectly included in its Group1 exclusion.

Statement 3: No.

User3 belongs directly to Group1 and Group3. Although CA1 includes Group1, it explicitly excludes Group3. The exclusion overrides the inclusion, meaning CA1 does not require MFA for User3.

CA2 also excludes both Group1 and Group3. Therefore, neither policy imposes an MFA requirement or blocks User3 ' s access.

These conclusions assume no additional Conditional Access policies or other authentication requirements apply.

A Tenant payload is the appropriate configuration because it enables administrators to create and customize simulated phishing messages specifically for their organization. Microsoft Defender for Office 365 Plan 2 provides Attack simulation training, including the Credential Harvest technique, to assess how users respond to realistic phishing attempts.

When creating a tenant payload, administrators can customize the simulated email content, select a phishing URL, insert phishing links into the message body, and incorporate organization-specific language, branding, and contextual information. These capabilities satisfy the requirement for a custom phishing link and company-based terminology.

Option A is incorrect because a tenant landing page controls the destination experience after a user interacts with a simulated phishing link. It does not configure the phishing email itself.

Option B is incorrect because custom end-user notifications provide simulation-related communications, such as training or reinforcement messages, rather than defining the simulated attack payload.

Option D is incorrect because Global payloads are Microsoft-provided templates. Although useful for standardized simulations, they are not the appropriate mechanism for creating an organization-specific phishing message.

Creating a Tenant payload therefore fulfills both customization requirements.

Microsoft References:

https://learn.microsoft.com/en-us/defender-office-365/attack-simulation-training-payloads

Microsoft Entra Conditional Access integrates with Microsoft Entra ID Protection to evaluate authentication risk and enforce access restrictions based on suspicious sign-in activity.

Option D is correct because the Sign-in risk condition evaluates the probability that an individual authentication attempt is unauthorized. Microsoft Entra ID Protection calculates this risk using various detections, including anonymous IP addresses and impossible travel.

Anonymous IP address: Microsoft identifies sign-ins originating from anonymizing services, including Tor exit nodes and anonymous VPN services. Such connections may indicate attempts to conceal the user ' s actual location or identity.

Impossible travel: Microsoft identifies activities originating from geographically distant locations within a period shorter than the time required for physical travel. This can indicate account compromise or unauthorized credential use.

Administrators can configure a Conditional Access policy that evaluates sign-in risk levels and selects Block access under Grant controls.

Option A is incorrect because the Locations condition evaluates network locations, countries, regions, and IP address ranges rather than directly evaluating identity risk detections.

Option B is incorrect because Insider risk relates to potentially risky internal user activity.

Option C is incorrect because User risk represents the likelihood that an account is compromised, rather than the risk associated with a specific sign-in event.

Important: Impossible travel detection can occur offline, so risk-based blocking is not guaranteed to prevent the initial suspicious sign-in in real time.

Microsoft Reference: Microsoft Learn — Risk detections in Microsoft Entra ID Protection .

Microsoft Entra ID Governance provides entitlement management through access packages, enabling organizations to automate access requests, approvals, assignments, and expiration.

Option A is correct because access packages support both required capabilities: self-service access requests with approval and automatic revocation when the approved assignment expires.

Administrators can create an access package containing the resources or groups that grant access to Agent1. They then configure an assignment policy that allows eligible contractors to request access.

On the policy ' s Requests settings, administrators can enable approval and designate the appropriate approvers. This ensures that contractors cannot receive access without authorization.

On the Lifecycle settings, administrators can configure access package assignments to expire after a specified number of days. Setting the duration to 30 days automatically ends the assignment at the end of the project.

Option B is incorrect because PIM primarily manages just-in-time privileged role and group access, rather than the complete self-service entitlement management process requested.

Option C is incorrect because Conditional Access evaluates access conditions but does not independently provide request approval and assignment expiration.

Option D is incorrect because recurring access reviews periodically assess existing access instead of providing the required initial request-and-approval workflow.

Therefore, an access package meets both requirements.

Microsoft References:

https://learn.microsoft.com/en-us/entra/id-governance/entitlement-management-access-package-approval-policy

https://learn.microsoft.com/en-us/entra/id-governance/entitlement-management-access-package-lifecycle-policy

Microsoft Entra self-service password reset (SSPR) allows users to reset their passwords without contacting an administrator or helpdesk. Administrators can configure which authentication methods users must complete to verify their identities.

Option A is correct because Authentication methods controls the verification methods available during password reset, including Microsoft Authenticator push notifications.

In the legacy SSPR configuration, administrators navigate to Microsoft Entra admin center → Entra ID → Password reset → Authentication methods.

The Mobile app notification method allows users to verify their identities by responding to a Microsoft Authenticator notification.

An important configuration consideration is that the legacy SSPR experience supports app notifications when two authentication methods are required for password reset. When only one method is required, the mobile application verification code is supported instead.

To restrict the pilot to Group1, administrators must separately configure Properties, enable SSPR for selected users, and select Group1.

Option B configures administrator-specific password reset requirements. Option C controls SSPR enablement and targeting, but not the authentication method itself. Option D controls registration requirements, and Option E configures password reset notifications.

Current documentation qualification: Microsoft has deprecated management of authentication methods through legacy SSPR policies. For new deployments, administrators should configure Microsoft Authenticator through the centralized Authentication methods policy.

Microsoft Defender for Office 365 supports outbound spam policies that control sending limits and automatically restrict accounts exhibiting suspicious outbound email activity.

Option A is correct because a custom outbound anti-spam policy can target Group1 specifically, allowing administrators to enforce more restrictive sending limits for marketing department mailboxes without changing the organization-wide configuration.

Administrators can navigate to Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-spam, and create a custom outbound policy.

The policy should include Group1, configure the appropriate external recipient limit, and select Restrict the user from sending mail as the action when a limit is reached.

Option B is incorrect because modifying the default outbound policy would affect other users not covered by a higher-priority custom outbound policy.

Option C is incorrect because Strict preset security policies do not contain configurable outbound spam policies.

Option D is incorrect because Standard preset protection cannot provide a custom outbound sending limit.

Option E is incorrect because inbound anti-spam policies protect incoming email rather than restricting compromised users ' outgoing messages.

Crucially, Microsoft ' s documentation confirms that Strict and Standard preset security policies do not override outbound spam policies. Therefore, the custom outbound policy can apply to Group1 without excluding its members from Strict protection.

Microsoft References:

Microsoft Learn — Configure outbound spam policies .

Microsoft Learn — Preset security policies .

Microsoft Entra Lifecycle Workflows supports automated identity lifecycle management, including workflows that govern Microsoft Entra agent identity sponsorships when employees change positions or leave an organization.

Option B is correct because the Lifecycle Workflows Administrator role grants the administrative permissions required to create, modify, and manage lifecycle workflows without granting broad entitlement management permissions.

Microsoft documents several agent sponsorship workflow tasks, including sending notifications to managers, notifying cosponsors, and transferring agent identity sponsorships to a manager.

These tasks are available within mover and leaver workflow templates. Admin1 can configure the appropriate workflow triggers, assign sponsorship-related tasks, and manage workflow execution.

The Lifecycle Workflows Administrator role is specifically scoped to lifecycle workflow management. It does not inherently grant administrative control over access packages, access reviews, or entitlement management catalogs.

Option A is incorrect because Global Administrator provides excessive privileges.

Option C is incorrect because AI Administrator is not the dedicated role for managing Microsoft Entra Lifecycle Workflows.

Option D is incorrect because Identity Governance Administrator provides broader identity governance permissions, conflicting with least privilege.

Option E is incorrect because Agent ID Administrator manages agent identity administration rather than providing the specific lifecycle workflow permissions required.

Therefore, Lifecycle Workflows Administrator is the appropriate role.

Microsoft References:

https://learn.microsoft.com/en-us/entra/id-governance/agent-sponsor-tasks

https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference