Microsoft AB-730 - AI Business Professional

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

In the Microsoft 365 Copilot app, the Conversations list can display status indicators next to individual conversation titles. In the exhibit, the Standings conversation has a distinct indicator (a green badge) shown to the right of the conversation name. This badge is used to signal that the conversation includes a verified response.

A verified response indicator is intended to help users quickly recognize outputs that were produced with stronger grounding and traceability—for example, responses that include supporting citations or references that can be reviewed for accuracy. This aligns with Microsoft’s guidance on improving trust in AI output by making source-backed or verification-supported responses easier to identify and validate.

The other options do not match the indicator shown. Conversations that are shared or added to notebooks typically use different share/notebook iconography, and scheduled prompts are represented with scheduling-related indicators rather than a verification badge. “Anonymous data” is not something Copilot marks at the conversation level in this manner.

Therefore, the best inference is that the Standings conversation contains a verified response.

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

To generate an effective monthly summary with Copilot in Excel, Microsoft prompting guidance emphasizes two core elements: clear intent and expected output structure. First, you should state the goal explicitly—such as “summarize total sales by month based on OrderDate and Amount, and highlight month-over-month changes.” This directs Copilot to the correct aggregation and analysis behavior (Option D).

Second, specifying the desired format improves usability and reduces ambiguity. For example, requesting “a table with Month, Total Sales, Number of Orders, and Average Order Value” or “a bulleted executive summary plus a small summary table” ensures Copilot returns results in a format you can immediately use (Option A).

A specific cell range (Option B) is usually unnecessary when the data is already in a recognized Excel table, because Copilot can work from the table context. The workbook file name (Option C) does not help analysis. Providing a formula (Option E) is not required because Copilot can compute monthly totals; formulas are optional if you want a specific calculation method, but they are not the best prompt ingredients for an effective summary.

Therefore, the best answers are A and D.

Microsoft 365 Copilot can use Microsoft Graph-grounded data (based on the user’s permissions) to help users work with Microsoft 365 content. This includes surfacing and summarizing information from Teams chats, so statement 1 is true. Copilot can also summarize and generate content related to Teams meetings (for example, meeting recap details, key discussion points, and follow-up actions when meeting artifacts such as transcript/notes are available), and it can answer questions and draft related content—so statement 3 is true.

Statement 2 is false because, while Copilot can draft emails and help prepare messages, it does not independently schedule and send emails automatically “based on conditions” as a native Copilot function. Conditional sending is typically handled through workflow automation tools (for example, Power Automate) and still requires appropriate configuration, permissions, and governance. In enterprise environments, this separation helps reduce risk by ensuring that automated outbound communication remains controlled, auditable, and compliant.

Custom instructions allow users to define persistent preferences for tone, style, and response behavior across conversations. Microsoft documentation explains that Custom instructions help tailor Copilot responses to professional roles, communication styles, and domain expectations.

For a medical researcher requiring consistently professional, field-appropriate responses, configuring Custom instructions in Settings ensures that Copilot maintains the desired tone and terminology in future interactions.

Attaching examples influences only a single conversation. Saving prompts to the Prompt Gallery aids reuse but does not enforce tone globally. Copilot Memory stores factual preferences but is not intended for style configuration.

Therefore, the best and most comprehensive approach is to configure Custom instructions in Settings.

Microsoft 365 Copilot operates within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Shared prompts, prompt links, and Copilot artifacts are governed by organizational access controls and tenant isolation. If a prompt is created and shared from outside your organization, cross-tenant access may not be supported depending on the sharing configuration and administrative policies.

When a user attempts to open a prompt that resides in another organization’s tenant without proper cross-tenant sharing permissions, Copilot cannot locate or validate the resource within the user’s own environment. As a result, the system displays a “Prompt not found” message.

Option B would typically result in an access or permissions error rather than the prompt being unavailable entirely. Sensitivity labels and scheduled prompts do not inherently cause a “not found” error. Therefore, the most likely cause is that the prompt exists outside your organization’s tenant boundary and is not accessible to you.

==================================================

Enterprise data protection (EDP) (often referred to as commercial data protection) is the capability that ensures Microsoft 365 Copilot handles organizational data under enterprise security and privacy guarantees. With EDP, Copilot processes prompts and responses within the customer’s Microsoft 365 boundary, respecting tenant isolation and identity-based access controls. This means Copilot only retrieves and uses data that the signed-in user is permitted to access, and the data remains governed by Microsoft 365 compliance features (such as retention, eDiscovery, audit, and Purview controls). Critically, EDP ensures that your organization’s prompts and the retrieved business content are not used to train the underlying AI foundation models. This is essential for protecting confidential business information and meeting regulatory and contractual requirements. The other options (Common Data Model, sensitivity labels, and Zero Trust) support data structure, classification, and security posture, but they do not specifically represent the Copilot guarantee that tenant data stays protected and is not used for model training.

Use the Analyst agent for Prompt 1 because it is optimized for structured data work: consolidating worksheets, performing calculations, sentiment breakdowns by category (product line), and producing visualizations. These tasks align with analysis-style workflows where quantitative processing and charting are required.

Use the Researcher agent for Prompt 2 because it is designed to synthesize information from multiple sources, including SharePoint content plus web grounding, and to produce a well-structured brief with citations. Researcher is best when you need evidence-backed insights, reputable sourcing, and an organized narrative with risks and gaps.

Use Chat for Prompt 3 because the goal is drafting a refined executive email based on an attached document with tone control and communication standards. Chat excels at business writing, rewriting, tone adjustment, and producing polished communications without needing the deeper research workflow or heavy data analytics specialization.

When creating an agent in the Microsoft 365 Copilot app using a template, administrators or authorized users can configure specific behaviors and knowledge sources for the agent. Therefore, it is correct that you can choose which knowledge sources the agent can use. This ensures proper grounding in approved Microsoft 365 data such as SharePoint sites, OneDrive folders, or other organizational repositories. Controlling knowledge sources supports responsible AI principles, including data security, relevance, and compliance.

Agents created within Microsoft 365 are designed primarily for internal organizational use. As a result, sharing the agent with users inside the organization is supported, enabling collaboration and productivity improvements across teams.

However, sharing the agent with external users is not supported by default. External sharing would introduce security and compliance risks, so Microsoft enforces tenant-level boundaries to protect enterprise data.

These capabilities reflect best practices in managing AI prompts and agents securely within enterprise environments.

Microsoft 365 Copilot agents operate within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Custom agents created in the Microsoft 365 Copilot app are governed by organizational policies, role-based access control, and Microsoft Entra ID authentication.

According to Microsoft AI Business Professional guidance, Copilot agents are designed for enterprise use and are shared within the organization unless administrators configure broader sharing capabilities. External sharing with personal Microsoft accounts or arbitrary email addresses is not supported by default due to security, data protection, and compliance requirements.

Because the agent in this scenario interacts with organizational data such as client emails, project milestones, and internal reports, access must remain restricted to authenticated users within the same tenant. This ensures that sensitive business information remains protected and that data access respects existing permissions.

Therefore, the agent can be shared only with people in your organization, making option D the correct answer.

According to Microsoft AI Business Professional guidance for Microsoft 365 Copilot, grounding a response means ensuring the AI generates output based on specific, authoritative content rather than relying on generalized training data. When working with enterprise documents such as proposals, grounding is achieved by explicitly referencing the source material within the prompt.

Option C is correct because referencing the proposal content directs Copilot to use that specific document as the primary context for generating the response. Microsoft documentation emphasizes that effective prompts should include clear context and explicit references to relevant files, meetings, emails, or documents stored in Microsoft 365. This reduces hallucinations and ensures factual alignment with organizational data.

Option A is incorrect because relying on training data increases the risk of inaccurate or fabricated information. Options B and D improve prompt clarity but do not guarantee grounding in the proposal itself.

Therefore, explicitly referencing the proposal content is the most reliable and best practice method for ensuring grounded, accurate responses in Microsoft 365 Copilot.