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 .

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.

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.

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.

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 .

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

Custom instructions in Microsoft 365 Copilot allow users to define persistent preferences that shape how Copilot responds across future interactions. According to Microsoft AI Business Professional guidance, these instructions are intended to personalize the Copilot experience by specifying communication preferences such as writing style, tone, level of detail, formatting, and other response characteristics. Once configured, these preferences are automatically applied to new Copilot conversations, providing a more consistent experience without requiring users to repeat the same instructions in every prompt.

Option B is correct because it accurately describes the primary purpose of custom instructions. Examples include asking Copilot to respond in a professional tone, use concise language, produce executive summaries, or format responses as bullet points.

Option A is partially related because users may include personal information within custom instructions, but the primary purpose is not to provide profile information—it is to establish response preferences. Option C is incorrect because security and data-sharing policies are enforced through Microsoft 365 administration and Microsoft Purview, not through custom instructions. Option D is incorrect because custom instructions do not grant Copilot additional permissions or autonomous action capabilities.

Therefore, the correct answer is B .

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

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