AB-730 AI Business Professional Questions and Answers

 When Microsoft 365 Copilot searches for content on the web, it uses the Bing search service.

Answer: Yes

 When Microsoft 365 Copilot searches for content on the web, it uploads the entire conversation history into the search request.

Answer: No

 When Microsoft 365 Copilot searches for content on the web, the query is anonymized and stripped of any user-identifiable information.

Answer: Yes

Microsoft 365 Copilot can use web grounding when a response requires current or public information. For web search, Copilot uses the Bing search service to retrieve relevant web results, so Statement 1 is Yes . This allows Copilot to supplement its response with up-to-date internet content when web grounding is enabled or selected.

Statement 2 is No because Copilot does not send the entire conversation history to Bing as a web search request. Instead, Copilot generates a search query based on the user’s prompt and relevant context. Sending the complete conversation would create unnecessary privacy and data exposure risk, which would conflict with Microsoft’s enterprise data protection model.

Statement 3 is Yes because Microsoft 365 Copilot is designed to protect user and tenant information during web grounding. Search queries are handled in a privacy-preserving way, with user-identifiable and tenant-identifiable information removed before the query is sent to Bing.

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 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.

When you use Microsoft 365 Copilot Chat without a Microsoft 365 Copilot license, Copilot Chat operates in a “general” mode rather than a Microsoft Graph-grounded work mode. In this configuration, Copilot does not have the entitlement to access and reason over your organization’s protected Microsoft 365 content (such as SharePoint sites, OneDrive files, Outlook mail, Teams messages, or other tenant resources). It also does not connect directly to your organization’s internal databases unless separate, explicitly configured integrations exist.

Instead, Copilot relies on three primary sources to generate a response: (1) the prompt context you provide in the current request (what you ask, plus any text you paste), (2) the conversation history within the current chat thread to maintain continuity, and (3) internet search data (when web grounding is available) to supplement general knowledge with up-to-date public information.

Therefore, the correct selections are C (prompt context), E (internet search data), and F (conversation history) , while organizational Microsoft 365 data and Teams chat data are not used without the Copilot license.

Microsoft distinguishes Microsoft 365 Copilot (the full, licensed experience integrated across Microsoft 365 apps and Microsoft Graph) from Microsoft 365 Copilot Chat (the chat-first experience available more broadly). Some advanced capabilities—especially those tied to specialized agents and persistent work organization—are typically associated with the full Copilot license.

The Researcher agent is an advanced capability and is not consistently available in Copilot Chat across tenants because it is treated as a premium agent experience. Copilot Notebooks are also a structured organization feature used to group conversations and share reference materials; this is typically positioned as part of the full Microsoft 365 Copilot experience.

Copilot Pages , however, is the collaborative, editable canvas used to refine, organize, and share Copilot-generated content. Pages is designed to work alongside Copilot Chat so users can move from a chat response into an editable artifact for collaboration and reuse. This makes Pages the feature most commonly available in both the full Microsoft 365 Copilot and Microsoft 365 Copilot Chat experiences.

Therefore, the best answer is Copilot Pages .

After a Microsoft Teams meeting ends, the Microsoft 365 Copilot feature designed specifically to help you catch up on what happened—including key discussion points, decisions, and next steps—is Recap (often referred to as intelligent recap). Recap aggregates post-meeting artifacts such as the recording, transcript, and AI-generated insights, and surfaces actionable items so attendees can quickly understand outcomes without rewatching the full meeting. This aligns directly with the requirement to review “key points and next steps” after each meeting.

Meeting Whiteboard is a collaborative canvas used during meetings for brainstorming and sketches; it does not automatically produce a structured summary of decisions and actions. Meeting info provides logistical details (participants, agenda, attachments) rather than a synthesized outcomes summary. Thread summaries focus on chat or channel message threads, not the meeting’s recorded and transcribed content.

Therefore, to consistently catch up on key points and next steps after meetings, the correct Copilot feature to use is Recap .

Microsoft 365 Copilot fully respects Microsoft Purview Information Protection, including sensitivity labels applied to documents. When content is used as a source to generate new content (for example, creating a PowerPoint presentation from a Word document), Copilot ensures that data protection policies are preserved and inherited.

If the source Word document is labeled Highly Confidential, the generated presentation will automatically inherit the same sensitivity label. This ensures that the classification, encryption, and access restrictions applied to the original content are consistently enforced in derived content. This behavior aligns with Microsoft’s compliance and data governance model, which prevents accidental data exposure when content is reused or transformed.

Option A is incorrect because Copilot does not require manual reclassification when a label is already present on the source. Option B is incorrect because labels are not dropped during content generation. Option D is incorrect because Copilot can still generate content from labeled documents, provided the user has access.

Therefore, the presentation will be generated with the Highly Confidential label applied.

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.

Evaluating spend and performance trends and determining ROI is a structured analytics task. In Microsoft 365 Copilot, the Analyst agent is designed for quantitative analysis workflows: it can interpret tables, analyze datasets, identify trends over time, calculate metrics (such as ROI), and present results clearly (often including charts or summarized insights). This makes it the best fit when your goal is to compare marketing channels and understand which ones are delivering the strongest return based on last year’s data.

Chat (Option B) can help you brainstorm questions or explain results, but it is not purpose-built for deep numeric analysis. The Researcher agent (Option C) is optimized for gathering and synthesizing information from sources and producing research-style outputs, not performing ROI calculations on internal performance data. A notebook (Option D) is useful for organizing files and keeping shared reference material across related conversations, but it does not itself perform the analysis—you would still need an analysis-capable agent.

Therefore, the best choice to evaluate spending and performance trends and calculate ROI is the Analyst agent .

The Describe tab is where you leverage generative AI to help build an agent by describing what you want the agent to do in natural language. Instead of manually configuring everything first, you provide the agent’s purpose, target users, tone, and the tasks it should perform (for example: “Create an onboarding agent that answers HR policy questions in a friendly tone and references SharePoint policies”). Copilot then uses that description to propose an initial agent setup—such as suggested behaviors, starter prompts, and structure—accelerating agent creation and improving consistency. By contrast, the Configure tab is typically used to fine-tune and finalize settings (such as knowledge sources, actions, and other parameters) after the agent concept is established. A Copilot notebook or Copilot page can help organize content and outputs, but they are not the primary place where generative AI “builds” the agent definition. Using the Describe tab reflects best practice: start with clear intent and constraints, then refine configuration for governance, accuracy, and usability.

The instructions will apply to new chat conversations.

Answer: Yes

The instructions will apply to new conversations with the Researcher agent and the Analyst agent.

Answer: Yes

The instructions will apply to previous responses in existing conversation.

Answer: No

Custom instructions in Microsoft 365 Copilot are a persistent preference mechanism that influences how Copilot responds going forward. Once configured, they are applied when you start new interactions, helping Copilot maintain consistent tone, formatting, and behavioral preferences across future chats. Therefore, they apply to new chat conversations (Statement 1 = Yes).

Custom instructions also carry into new conversations you initiate with Copilot experiences and agents (such as Researcher and Analyst), because the instructions act as a user-level guidance layer that shapes responses regardless of which Copilot “mode” you start—provided those agents are being used in the same Copilot environment and are subject to your settings (Statement 2 = Yes).

However, custom instructions do not retroactively change content that was already generated. Existing conversation history and any prior responses remain unchanged; the instructions affect subsequent turns or new threads, not previously produced outputs (Statement 3 = No).

The correct answer is a page because Microsoft 365 Copilot supports Copilot Pages as a place to capture AI output and then refine it collaboratively. When Researcher generates a report, saving it to a page turns the response into an editable artifact where you can reorganize sections, polish wording, add supporting details, and continue iterating with Copilot while keeping the content structured.

A “conversation” is the chat thread itself and isn’t the primary editable format for producing a finalized deliverable. An “agent” is the experience that generates the content, not the storage/edit surface. A “notebook” is used for broader organization of work, but the direct save-and-edit unit for a generated response is the page , which is designed specifically for drafting, editing, and preparing content for business use (for example, exporting or reusing in Word/Teams/Outlook workflows).

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 guidance for effective prompting emphasizes clarity and context as the two most important factors. Providing context (Option A) ensures that Copilot understands the background, data sources, and constraints relevant to the task. This improves grounding and reduces ambiguity, leading to more accurate and useful responses.

Providing a clear goal (Option D) is equally critical. A well-defined objective—such as summarizing, analyzing, or drafting—helps Copilot determine the correct approach, structure, and level of detail for the response. Without a clear goal, outputs may be generic or misaligned with user expectations.

Using a broad range of instructions can introduce confusion rather than clarity. Acronyms may reduce clarity unless explicitly defined. Keeping prompts generic is discouraged because specificity improves quality and relevance of responses.

Therefore, the correct answers are A (adding context) and D (providing a clear goal) .

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.

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

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.

The correct answer is instructions because an agent’s persona—such as being warm, friendly, formal, or analytical—is defined through its behavioral and communication guidance. In Microsoft 365 Copilot, the Instructions field controls how the agent responds, including tone, style, personality, response structure, and interaction patterns.

The description typically explains what the agent does, not how it communicates. Capabilities define what tasks the agent can perform, such as summarizing documents or analyzing data. Suggested prompts provide example user queries but do not control the agent’s personality or communication style.

To establish a warm and friendly persona, the instructions should explicitly state guidance such as: “Respond in a supportive, conversational tone. Use clear and positive language. Be encouraging and approachable.” This ensures consistent tone across all interactions.

Defining persona through instructions reflects prompt engineering best practices in generative AI, enabling predictable behavior, improved user experience, and alignment with organizational communication standards within Microsoft 365 Copilot environments.

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

Microsoft 365 Copilot conversation retention is governed by Microsoft Purview Data Lifecycle Management and an organization ' s retention policies. Under the default Microsoft 365 configuration , no automatic retention period is configured specifically for Copilot conversations. This means Copilot interactions remain subject to the organization ' s existing Microsoft 365 retention configuration and are retained indefinitely until a retention or deletion policy is applied or a user deletes the conversation (where permitted by organizational policy). Microsoft introduced dedicated retention policies for Copilot so administrators can configure periods such as 30 days or other business-specific durations, but these are administrator-configured policies , not default behavior.

Therefore, options A (30 days) and D (90 days) represent examples of configurable retention periods rather than the default. Option C (one year) is not the default Microsoft setting. With Microsoft 365 services using their default configuration and no explicit retention policy configured, Copilot conversations can be retained indefinitely , subject to organizational compliance requirements and any future administrator-defined retention policies.

Prompt injection is a generative AI security risk where an attacker inserts instructions (often hidden in text, documents, webpages, or user inputs) to override or manipulate the assistant’s intended behavior. This can lead to unintended actions such as ignoring policy controls, producing unsafe outputs, or attempting to reveal sensitive information. Because generative AI systems follow natural-language instructions, they can be socially engineered to prioritize malicious content unless safeguards are in place. This is why prompt injection can cause data exposure (for example, attempting to extract confidential content from grounded sources) and can also embed harmful instructions that redirect the model’s behavior. In enterprise settings like Microsoft 365 Copilot, mitigations include grounding boundaries, permission trimming, content filtering, and instruction hierarchy (system policies over user instructions). From a business governance perspective, users should treat untrusted inputs (emails, documents, web text) as potentially hostile and apply least-privilege access and validation when using AI outputs in decision-making.

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

When you share a Microsoft 365 Copilot prompt that references files stored in OneDrive, the prompt sharing action does not automatically change file permissions. Copilot follows the Microsoft 365 permission model, meaning users can only access, summarize, analyze, or ground responses in files that they already have permission to open.

Option C is correct because the shared prompt can be used successfully with the referenced files only if the recipient already has access to those OneDrive files. Sharing the prompt shares the prompt structure and instructions, not the underlying file access rights. This prevents accidental exposure of private or confidential business documents.

Option B is incorrect because Copilot does not automatically grant access to files when a prompt is shared. Option A is too strong because the files are not necessarily removed from the prompt; they remain referenced but usable only if permissions allow. Option D may happen in some Microsoft 365 file-sharing contexts, but the best general rule is that access must already exist or be granted separately.

Therefore, the user can run the prompt successfully only if they have access to the referenced OneDrive files.

Prompt scheduling in Microsoft 365 Copilot enables users to automate recurring AI-driven tasks such as generating reports, summaries, or updates. However, there are defined operational limits to ensure system performance, responsible AI usage, and governance compliance.

First, the most frequent interval at which a prompt can be scheduled is once per day . Scheduling more frequently, such as hourly, is not supported. This limitation prevents excessive automated execution that could strain system resources or generate unnecessary redundant outputs.

Second, a scheduled prompt has a maximum execution limit of 15 times . After reaching this threshold, the schedule must be recreated if further automation is required. This control ensures users periodically review and validate automated prompts for relevance, accuracy, and business alignment.

These constraints reflect Microsoft’s enterprise AI governance strategy: balancing productivity automation with performance optimization, cost control, compliance oversight, and responsible AI lifecycle management within Microsoft 365 Copilot environments.

Statements:

You can add a Microsoft Teams chat as a knowledge source to a Microsoft 365 Copilot agent.

Answer: Yes

You can add a Microsoft 365 Copilot conversation as a knowledge source to a Copilot agent.

Answer: No

You can use an image file, such as a JPG file, as a knowledge source for a Microsoft 365 Copilot agent.

Answer: NO

Microsoft 365 Copilot Agent Builder supports grounding agents in approved knowledge sources so responses are accurate and permission-trimmed. Teams chats can be used as a knowledge source: Microsoft Learn confirms you can ground an agent in Teams data, including chat messages (and optionally scope to specific chats), enabling the agent to reference collaboration context when answering questions.

A Copilot conversation itself is not a supported “knowledge source” option; knowledge sources are configured from items like SharePoint content, Teams, email, websites, uploaded files, and connectors—not prior chat transcripts.

Finally, JPG images are not supported as knowledge-source file types . Microsoft’s supported file types for agent knowledge include documents like .doc/.docx, .pdf, .ppt/.pptx, .txt, and Excel formats (.xls/.xlsx), but not image formats. Therefore, you cannot use a JPG as a knowledge source for a Copilot agent.