The AI Business Professional (AB-730)

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.

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 .

Microsoft 365 Copilot in Teams is designed to provide real-time meeting assistance, including summarizing discussions, identifying key decisions, and highlighting action items. When joining a meeting late, the most efficient and immediate method to catch up is to directly prompt Copilot within the Teams meeting experience.

Option A is the best answer because Copilot in Teams can summarize what has occurred so far during the live meeting. It leverages the meeting transcript, speaker attribution, and contextual signals to generate a concise, structured summary in real time. This minimizes delay and provides actionable insights instantly.

Reading the transcript (Option B) would require manual review and is not the fastest method. Intelligent recap (Option D) is typically available after the meeting concludes and processes recording data. Asking Copilot from the separate Microsoft 365 Copilot app (Option C) may not provide immediate, in-meeting contextual awareness.

Therefore, the fastest and most effective approach is to ask Copilot in Teams to summarize what you missed.

According to Microsoft AI Business Professional guidance for Microsoft 365 Copilot, grounding a response means ensuring the AI generates output based on specific, authoritative content rather than relying on generalized training data. When working with enterprise documents such as proposals, grounding is achieved by explicitly referencing the source material within the prompt.

Option C is correct because referencing the proposal content directs Copilot to use that specific document as the primary context for generating the response. Microsoft documentation emphasizes that effective prompts should include clear context and explicit references to relevant files, meetings, emails, or documents stored in Microsoft 365. This reduces hallucinations and ensures factual alignment with organizational data.

Option A is incorrect because relying on training data increases the risk of inaccurate or fabricated information. Options B and D improve prompt clarity but do not guarantee grounding in the proposal itself.

Therefore, explicitly referencing the proposal content is the most reliable and best practice method for ensuring grounded, accurate responses in Microsoft 365 Copilot.

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 .

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.

Microsoft 365 Copilot follows Microsoft’s Responsible AI principles and enforces strict content safety policies. When a prompt violates safety guidelines—such as containing harmful, abusive, illegal, or restricted content—the system may refuse to generate a response. The refusal message shown is consistent with safety filtering behavior.

Generative AI systems include moderation layers that evaluate prompts before generating output. If the prompt is classified as unsafe or non-compliant with policy, Copilot blocks the request and encourages the user to try a different topic.

A vague prompt typically results in a generic or clarifying response rather than a refusal. There is no fixed limit of five requests per prompt. Exceeding the context window usually results in truncation or processing errors, not a safety-based refusal message.

Therefore, the most likely cause of the response is that the prompt contains language that violates safety guidelines.

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

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 .

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.