AB-730 AI Business Professional Questions and Answers

In Microsoft 365 Copilot, the Copilot Prompt Gallery is used to store and reuse prompts that have been created and tested. To save a prompt into the gallery, Copilot must first have the prompt as an executed interaction so it can be captured as a reusable prompt (often alongside the context and intended outcome). Microsoft guidance for prompt management emphasizes validating prompts by running them and reviewing the output, then saving the prompt for reuse once it produces the desired results.

Option D is therefore the correct first step: run the prompt . After execution, you can save it to the Prompt Gallery so it becomes easily discoverable and reusable for future project reports or for sharing within your organization (subject to policy).

Creating a notebook is useful for organizing reference materials across related conversations, but it is not required to publish a prompt to the gallery. Adding an agent is for creating specialized assistants with knowledge and capabilities, not for saving a single prompt. Creating a page is used to refine and collaborate on generated content, not to make a prompt available in the gallery.

Therefore, the first action is to run the prompt .

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

Microsoft 365 Copilot can be accessed via its dedicated web experience for enterprise users. The correct web entry point for Microsoft 365 Copilot is https://m365.cloud.microsoft , which provides authenticated access to Copilot features within the Microsoft 365 environment.

This URL routes users into the Microsoft 365 ecosystem where Copilot integrates with organizational data such as SharePoint, OneDrive, Teams, and Outlook. It ensures that users are authenticated through Microsoft Entra ID and that access controls are enforced according to tenant policies.

Option B refers to Copilot Studio, which is used to build and manage custom copilots and agents rather than access the Microsoft 365 Copilot chat experience. Option C (My Apps) is a general application launcher portal. Option D is an incorrect account management URL and does not provide Copilot access.

Therefore, to access Microsoft 365 Copilot from a web browser, the correct URL is https://m365.cloud.microsoft .

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.

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.

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.

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 provides centralized activity management controls through the My Account portal, which allows users to manage privacy settings, activity history, and data associated with Microsoft 365 services, including Copilot. When the requirement is to delete all conversations with minimal effort, the most efficient method is to use the account-level activity management tools rather than deleting conversations individually.

The My Account portal enables bulk management of Copilot activity data, allowing users to clear conversation history in a consolidated manner. This approach aligns with Microsoft’s privacy-by-design framework, giving users control over their AI-generated interaction history without requiring administrative intervention.

Using the Copilot web or desktop app would typically require manually deleting conversations one at a time, increasing effort. The Windows 11 Settings app is unrelated to Microsoft 365 Copilot data management.

Therefore, to delete all Copilot conversations efficiently and with the least amount of effort, the correct approach is to use the My Account portal in Microsoft 365.

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 .

Microsoft 365 Copilot agents dynamically reflect updates such as new suggested prompts. When an agent is updated, users who already have the agent installed do not need to reinstall or have the agent reshared. Instead, the updated configuration becomes available when the agent is used again.

Suggested prompts are surfaced when a user interacts with the agent. Therefore, once Ben Smith issues any prompt to Agent1, the agent session refreshes and displays the latest suggested prompts, including the newly added one.

Stopping and resharing the agent (Option A) or reinstalling it (Option B) is unnecessary overhead. Option D refers to a non-standard command and is not part of Microsoft Copilot functionality.

Thus, the correct action is simply to have the user interact with the agent again.

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

Copilot in Microsoft Teams is designed to help users work faster by summarizing meeting content and assisting with message composition in chats and channels. Microsoft guidance highlights that Copilot can synthesize what was discussed in a meeting by generating a structured recap that includes key points, decisions, and action items. This directly matches option C . Copilot can also help you respond more quickly in Teams conversations by drafting replies grounded in the context of the existing chat or channel thread, which matches option D .

Options A and B are not Copilot capabilities. Muting and unmuting participants is a meeting control function handled by Teams meeting roles and settings, and it is not automatically driven by Copilot based on participant location. Creating custom backgrounds is a Teams visual feature (and can involve Designer or image tools), but it is not a Copilot-in-Teams productivity function for summarization or drafting based on conversation context.

Therefore, the two tasks you can achieve using Copilot in Teams are generating meeting summaries with decisions and action items, and drafting responses to channel messages based on conversation context.

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 provides structured ways to persist and reuse knowledge sources to avoid repeatedly uploading the same files.

Creating a notebook that references the five files (Option B) allows those documents to remain attached within a persistent workspace. Copilot can then consistently ground responses in those files without re-uploading them for every conversation.

Creating an agent with a defined knowledge source (Option D) also provides a reusable solution. By configuring the five files as part of the agent’s knowledge base, the agent can automatically reference them in future interactions.

Saving a prompt does not persist file attachments. Fine-tuning models is not part of standard Microsoft 365 Copilot user workflows. Uploading a ZIP file does not improve reference management and may reduce accessibility of individual documents.

Therefore, the correct solutions are to create a notebook that references the files and to create an agent with a knowledge source.

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.

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.

When transcription is not enabled , Microsoft 365 Copilot in Teams cannot access a full historical record of the meeting conversation. Copilot relies on transcript data to provide complete summaries and recaps. Without transcription, Copilot can still assist during the meeting , but only from the point at which it is activated.

Copilot does not automatically activate at the start of the meeting; a user must explicitly invoke it. Once activated, Copilot processes the live conversation stream and can generate summaries, key points, or insights from that moment forward only . It cannot reconstruct earlier discussion because no transcript exists for prior content.

Options B and D are incorrect because they assume automatic activation and full-meeting recap capability, which require transcription. Option A is incorrect because Copilot summarizes the meeting content, not just the speech of the activating user.

Therefore, the correct answer is C .

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

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.

Saved prompts in Microsoft 365 Copilot Prompt Gallery are designed to be reusable templates for common tasks. Microsoft guidance indicates that users can manage these prompts similarly to other reusable assets—this includes editing metadata and removing them when no longer needed.

Option A is correct because users can update the title of a saved prompt to improve clarity, organization, or discoverability within the Prompt Gallery. This is part of basic prompt management.

Option E is also correct because users can delete or remove saved prompts from the Prompt Gallery if they are outdated or no longer relevant.

Option B is incorrect because prompts are not directly shared to Teams as a native feature; they are typically shared via the Prompt Gallery or copied manually. Option C is incorrect in this context because saved prompts are generally treated as reusable templates rather than being directly edited in-place (you typically create a new version). Option D is incorrect because scheduling prompts is not a standard capability of saved prompts in Microsoft 365 Copilot.

Therefore, the correct answers are A and E .

In Microsoft 365 Copilot, notebooks are designed to organize related work into a single, reusable workspace. A notebook can group multiple Copilot conversations and associate them with shared reference materials (for example, the same set of files, links, or notes). This directly addresses both requirements in the question: (1) making conversations easier to find by collecting them in one place, and (2) enabling those conversations to use the same reference sources for grounding and continuity.

An agent is best when you want a specialized Copilot experience with predefined instructions, capabilities, and (optionally) a configured knowledge source. However, an agent does not primarily function as a “container” to gather and organize multiple existing conversations.

A page is used to capture and edit output (such as a generated report) for collaboration, not to organize multiple conversations with shared references. An app is a broader product surface and does not solve the conversation organization requirement.

Therefore, the best solution is to use a notebook .

In Microsoft 365 Copilot, when content from a document is summarized or referenced, Copilot respects Microsoft 365 security, compliance, and data protection policies such as sensitivity labels . Sensitivity labels can restrict how content is accessed, shared, or processed, and Copilot behavior reflects these constraints.

The exhibit shows that Copilot is able to summarize the document but provides only limited or generalized insights, indicating restricted handling of the content. This is consistent with documents that have sensitivity labels applied (for example, Confidential or Highly Confidential), where Copilot may limit exposure of detailed content or apply safeguards when generating responses.

Other options do not align with the scenario. If the file were not supported, Copilot would not process it at all. If it were inaccessible outside the organization, that would affect sharing rather than summarization behavior. Being in a notebook does not impose restrictions on how content is summarized.

Therefore, the correct inference is that Document1.docx has a sensitivity label applied .

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.