AB-730 AI Business Professional Questions and Answers

When building a custom analytics agent in Microsoft 365 Copilot that must process structured data from Excel files, advanced analytical capabilities are required. According to Microsoft AI Business Professional guidance, tasks such as performing mathematical calculations, generating aggregations, creating charts, and conducting structured data analysis require programmatic execution capabilities rather than simple text generation.

A code interpreter enables the agent to run Python-based analytical operations in a secure execution environment. This allows the agent to manipulate datasets, compute totals and averages, perform grouping and filtering, and generate visualizations such as bar charts or line graphs based on the Excel data. The interpreter bridges the gap between natural language instructions and executable analytical logic.

An image generator is designed for creative visual content and is unrelated to structured data analytics. Suggested prompts and templates improve usability and consistency but do not provide computational or visualization capabilities.

Therefore, to enable mathematical operations, aggregation, data analysis, and visualization of Excel sales data, the correct component to add to the agent is a code interpreter.

When building a custom agent in Microsoft 365 Copilot for marketing use cases, the required capabilities must align with the intended outputs. Marketing collateral includes written copy as well as visual assets such as logos and artwork. According to Microsoft AI Business Professional documentation, generative AI solutions that produce visual creative assets require integrated image generation capabilities powered by multimodal AI models.

Option C is correct because an image generator enables the agent to create visual marketing materials such as logos, artwork, and design elements. While templates and suggested prompts can improve usability and consistency, they do not provide the underlying capability to generate images. A code interpreter is designed for data analysis, calculations, or technical scripting tasks and is not relevant to creative marketing asset production.

Therefore, to fulfill the requirement of producing both textual and visual marketing collateral, the most essential addition to the custom agent is an image generator.

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.

Copilot in Outlook is designed to reduce time spent reading and writing email by using AI to summarize message threads and generate drafts grounded in the current email context. Microsoft guidance for Copilot in Outlook highlights core capabilities such as drafting replies that reflect the conversation tone and content, and summarizing email threads or inbox content so users can quickly understand what requires action.

Option B is correct because Copilot can generate a draft reply based on the context of the email conversation, helping you respond faster while keeping the response aligned to what was discussed. Option C is correct because Copilot can summarize emails—such as unread messages or a thread—by extracting key points, requests, decisions, and suggested next steps, which supports rapid triage.

Option A is not a Copilot task; inserting or customizing an HTML signature is a standard Outlook configuration feature. Option D is also a traditional Outlook management function and is not an AI drafting/summarization capability.

Therefore, the two tasks you can achieve with Copilot in Outlook are drafting responses and summarizing unread emails .

Microsoft 365 Copilot Pages supports collaboration similarly to other Microsoft 365 documents. Collaboration requires notifying or granting access to colleagues.

Using @mentions within the page (Option A) directly notifies the colleague and facilitates collaborative engagement. Sharing the page link (Option D) allows others to access and edit the content according to permissions. These two methods provide complete collaboration workflows.

Adding the page to a notebook does not grant collaborative access. Opening the page in Word changes the editing surface but does not inherently enable collaboration unless shared.

Therefore, the correct answers are A and D.

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

This scenario is an example of overreliance . Microsoft’s AI guidance highlights that Copilot is an assistive tool that can accelerate analysis and drafting, but users remain responsible for validating outputs—especially for high-impact business decisions. Overreliance occurs when someone treats AI output as authoritative and acts on it without applying judgment, cross-checking sources, or validating against current conditions.

Here, the merchandiser uses Copilot to generate stocking recommendations from historical sales data, then places a large order without reviewing the suggestions or incorporating current market trends. Even if the historical data is accurate, demand can shift due to seasonality changes, competitor actions, pricing, supply constraints, macroeconomic factors, or new product launches. Copilot’s recommendations should be treated as a starting point for decision-making, not the final decision.

Option A (verification) is the opposite behavior—checking accuracy before acting. Option C (fabrication) would involve Copilot inventing facts; the prompt doesn’t indicate fictional data, only unvalidated reliance. Option D (prompt injection) involves malicious instructions embedded in content to manipulate the model, which is not described here.

Therefore, the best answer is overreliance .

In Microsoft 365 experiences, the standard way to invoke or reference people and specific resources in-context is by using the @mention pattern. Microsoft 365 Copilot extends this familiar interaction model to agents: when you want to switch to, invoke, or direct a question to a specific agent from within an existing Copilot conversation, you use @ followed by the agent’s name. This makes the agent selection explicit and reduces ambiguity about which assistant or capability you want to use for the next turn.

The other syntaxes listed are commonly associated with different systems: square brackets are not used for agent invocation, hashtags are typically used for topics/tags, and slash commands are used in some chat applications for command execution—but they are not the standard method for calling a Copilot agent in Microsoft 365 Copilot Chat.

Therefore, to chat with an agent named Agent1 during an open Copilot conversation, you should enter @Agent1 .

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.

Copilot in Word assists with content generation, summarization, rewriting, and structural organization. It can analyze document headings and insert a table of contents based on structured heading styles, supporting document navigation. It can also generate summaries of key points, which aligns directly with generative AI text analysis capabilities.

Custom watermark formatting and precise page margin configuration are traditional Word formatting functions and are not core generative AI capabilities of Copilot.

Therefore, the correct answers are A and C.

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

Microsoft Purview is the correct choice because it is Microsoft’s unified compliance and data governance solution that helps organizations apply and enforce policies across Microsoft 365 content— including Copilot-related interactions where those interactions are captured in services such as Microsoft 365 audit, eDiscovery, and Purview compliance experiences. Purview supports capabilities such as data loss prevention (DLP) , retention , eDiscovery , audit , and sensitivity labeling so organizations can manage and govern data and AI-assisted content in line with regulatory and internal requirements. In contrast, Microsoft Entra ID focuses on identity and access management, Intune focuses on device and application management, and Defender for Cloud focuses on cloud security posture management. Governance policies for Copilot-generated conversations and associated compliance controls align most directly with Purview , which is designed to manage information protection and compliance across the Microsoft 365 environment.

In Microsoft 365 Copilot, a notebook is a workspace intended to organize and ground related Copilot work. Microsoft guidance describes notebooks as a way to bring together multiple conversations and keep them aligned to the same set of reference materials—such as documents, notes, links, or other resources—so you don’t have to repeatedly attach or restate the same context. This improves consistency and prompt-grounding across a set of related tasks (for example, managing a project, developing a proposal, or maintaining a recurring report).

Option B correctly captures this purpose: a notebook provides a private, organized location where reference materials can be curated and reused across related Copilot conversations.

Option A is incorrect because notebooks are not primarily designed to generate email-ready transcripts of conversations. Option C is incorrect because generating a summary of interactions is a conversation-level function; notebooks are broader organizational containers for materials and related workstreams, not a “summary generator” of a single chat thread.

Therefore, the purpose of a notebook is to organize reference materials across related conversations.

Microsoft 365 Copilot in Teams relies heavily on meeting transcripts to provide post-meeting intelligence such as summaries, key points, decisions, and action items. The transcript serves as the structured textual data that Copilot analyzes to understand what was discussed during the meeting.

The feature commonly referred to as recap or intelligent recap is generated based on this transcript. Without transcription enabled, Copilot lacks the necessary detailed conversation data to accurately reconstruct the meeting content. As a result, generating a recap of what was discussed is only possible when a transcript is available.

Other options such as scheduling a follow-up meeting or identifying attached content do not depend on transcription, as they rely on calendar data or meeting metadata rather than conversational analysis. However, summarization and recap capabilities are directly tied to the transcript.

Therefore, the correct completion is generate a recap of what was discussed during the meeting , as this action specifically requires the meeting to be transcribed.

Microsoft 365 Copilot is designed to be helpful by using work context —for example, the files you have access to, recent activity, meetings, emails, and SharePoint/OneDrive content—to suggest relevant prompts and help you start tasks faster. It also uses this context to augment your prompt before it is sent to the LLM. This is the grounding approach (often described as retrieval-augmented generation): Copilot retrieves relevant organizational content you’re permitted to access and adds it as supporting context so responses are accurate and business-relevant. However, Microsoft 365 Copilot does not use your organization’s contextual data to train the underlying foundation model . That separation is critical for enterprise privacy and compliance: your prompts, responses, and tenant data are used to generate the answer for your session and permissions, but are not used to improve or retrain the base LLM. This approach supports responsible AI, protects confidential business information, and ensures outputs respect access controls.

Agents created in the Microsoft 365 Copilot app are primarily designed for use within the Copilot Chat experience and related Copilot surfaces, not directly embedded inside individual applications like Word. Therefore, such agents are not automatically available in Microsoft Word, making Statement 1 incorrect.

However, these agents are designed for collaboration and reuse within an organization. Microsoft guidance confirms that agents can be shared with other users in the same tenant , allowing teams to leverage common tools, prompts, and knowledge sources. Hence, Statement 2 is correct.

For advanced automation scenarios involving complex workflows and third-party connectors, Microsoft provides Copilot Studio rather than the standard Copilot app. The Copilot app focuses on lightweight agent creation using natural language, files, and simple configurations. It does not support complex orchestration with external connectors. Therefore, Statement 3 is incorrect.

Thus, the correct answers are No, Yes, No .

The correct completion is “cannot modify the settings of” because built-in agents such as the Researcher agent in Microsoft 365 Copilot are system-defined experiences. These agents are designed and managed by Microsoft to ensure consistent functionality, security, compliance, and alignment with responsible AI standards.

While users can interact with Researcher, provide prompts, and refine outputs during conversations, they cannot directly modify the core system settings or configuration of the built-in agent from Microsoft 365. Administrative configuration and deeper customization are available when creating custom Copilot agents through approved development tools, but default Microsoft-provided agents have controlled configurations.

Options such as modifying agent instructions, adding prompts, or deleting suggested prompts imply direct structural customization of the built-in agent interface, which is not supported in the standard Microsoft 365 Copilot experience.

This reflects a key generative AI governance principle in enterprise environments: system-level controls remain centrally managed to maintain data protection, compliance, and responsible AI implementation across the organization.

Prompt-grounding means ensuring Copilot’s response is based on authoritative, relevant source material rather than inferred or generalized information. Microsoft guidance for Copilot emphasizes that the most effective way to ground responses is to explicitly point Copilot to the content you want it to use—such as specific SharePoint documents, OneDrive files, emails, meeting notes, or other Microsoft 365 resources the user has permission to access.

Option D is therefore the best answer because referencing specific files anchors Copilot’s reasoning to the exact material that should be used for facts, terminology, and details. This reduces hallucinations (fabrication) and improves accuracy and traceability, especially when Copilot can provide citations back to the referenced sources.

Option B (desired output format) improves structure and readability but does not, by itself, ground content. Option A can sometimes improve clarity, but shorter prompts do not guarantee grounding. Option C may help comprehension in some cases, but it is not a grounding strategy and can be counterproductive if the source material is technical.

Therefore, the best approach to improve prompt-grounding is to reference specific files .

Microsoft 365 Copilot follows Microsoft’s enterprise data governance and privacy principles, which allow users to manage their own conversation history where appropriate. According to Microsoft AI Business Professional guidance, users can review and delete individual Copilot conversation histories directly from their personal account settings without requiring administrative intervention.

Option D is correct because the My Account portal in Microsoft 365 Copilot allows individual users to manage their activity history, including deleting specific conversations. This enables targeted removal of sensitive interactions while retaining other conversation data.

Option A is incorrect because the Copilot app itself does not provide full account-level activity management capabilities. Options B and C are administrative tools used for tenant-wide governance, compliance, retention policies, and eDiscovery. These portals typically require administrative privileges and are not intended for individual user self-service deletion of specific conversations.

Therefore, to delete a single confidential Copilot conversation without affecting other chats and without requiring administrator approval, the correct tool is the My Account portal in Microsoft 365 Copilot.

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.

In Microsoft 365 Copilot, agents such as Researcher are accessed through the Agents experience within the Copilot app. If the user interface does not immediately display a specific agent, the correct action is to browse or search the available agents catalog. The exhibit shows the left navigation pane with an Explore agents option.

According to Microsoft AI Business Professional guidance, built-in and custom agents can be discovered and enabled through the Explore agents section. If the user already has the appropriate Copilot license and is signed in with their work account, there is no need to switch accounts or request another license.

Signing in through a browser does not change feature availability, and using a personal account would remove access to organizational features. Therefore, to access the Researcher agent, you should select Explore agents and search for Researcher.

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