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.

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.

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.

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.

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

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 are designed to integrate with Microsoft 365 data sources and provide flexible, natural-language-driven configuration. Agents can be connected to organizational data such as SharePoint, OneDrive, and Exchange. Since shared mailboxes are part of Exchange Online and accessible through Microsoft Graph (subject to permissions), agents can be configured to search shared mailboxes, making Statement 1 correct.

Microsoft also enables natural language creation of agents , allowing users to describe what the agent should do, its purpose, and behavior using conversational instructions rather than requiring code. This simplifies agent creation and aligns with Copilot’s low-code/no-code approach, so Statement 2 is correct.

However, agents cannot use other agents as knowledge sources. Knowledge sources are limited to structured content such as files, sites, and data repositories. Agents operate independently rather than being nested or chained as data sources, making Statement 3 incorrect.

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

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 .

Microsoft 365 Copilot respects Microsoft 365 permissions (“permission trimming”). This means it can only access and summarize content you are authorized to view. Therefore, Copilot cannot answer questions about Teams meetings you are not invited to (and otherwise don’t have access to), making statement 1 No .

Copilot can summarize and answer questions about Teams artifacts you do have access to—such as chat messages, channel posts, and meeting content (for example, transcripts, notes, recordings, and meeting recap details when available). That makes statement 2 Yes .

Copilot can also help you prepare for your schedule by summarizing upcoming meetings you’re invited to , using calendar and meeting context (subject, time, participants, related emails/files, and available agenda/notes). This supports planning and prioritization for the week ahead, so statement 3 is Yes .

When you add a file to a Microsoft 365 Copilot notebook from a Microsoft SharePoint site , you are referencing a document that is stored and managed within Microsoft 365. SharePoint maintains a single authoritative file that can be updated over time (with version history behind the scenes). Copilot notebooks that reference SharePoint content are designed to stay grounded in the current version of that cloud-hosted document, subject to your permissions.

Because Process.docx is stored in SharePoint, the notebook reference points to the SharePoint document itself rather than a static local snapshot. When another user updates the document in SharePoint, the “latest” content becomes the current version available at that location. When you chat in the notebook, Copilot will use the file as it exists now in SharePoint, which means it will reference the most recent version.

Option A would be typical only if you attached a local file upload (a static copy) rather than a SharePoint-hosted file. Option C is incorrect because Copilot uses the current file at the referenced location, not multiple historical versions simultaneously.

Therefore, the chat will reference the most recent version of Process.docx .

Microsoft 365 Copilot includes a memory capability that allows it to retain user-provided preferences or details across interactions when explicitly instructed to remember them. These stored details are referred to as memories and are separate from standard conversation history.

If you previously asked Copilot to remember specific trip-related details, those details are stored as structured memory items. Simply deleting the conversation does not necessarily remove stored memory entries. Likewise, deleting activity history through the My Account portal removes conversation records but does not directly manage structured Copilot memories. Custom instructions define persistent behavioral preferences and are unrelated to trip-specific stored data.

To ensure Copilot no longer retains those trip details, you must delete the stored memories directly within Copilot. Microsoft documentation explains that users can view and manage saved memories and remove them individually to control what Copilot retains.

Therefore, the correct action to ensure Copilot forgets the trip details is to delete the memories.