The AI Business Professional (AB-730)

Microsoft 365 Copilot operates within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Shared prompts, prompt links, and Copilot artifacts are governed by organizational access controls and tenant isolation. If a prompt is created and shared from outside your organization, cross-tenant access may not be supported depending on the sharing configuration and administrative policies.

When a user attempts to open a prompt that resides in another organization’s tenant without proper cross-tenant sharing permissions, Copilot cannot locate or validate the resource within the user’s own environment. As a result, the system displays a “Prompt not found” message.

Option B would typically result in an access or permissions error rather than the prompt being unavailable entirely. Sensitivity labels and scheduled prompts do not inherently cause a “not found” error. Therefore, the most likely cause is that the prompt exists outside your organization’s tenant boundary and is not accessible to you.

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

When Microsoft 365 Copilot cannot access a referenced file, it may return a message indicating that the file is empty, corrupted, or cannot be processed. In many cases, this message appears when the user does not have sufficient permissions to open the file in SharePoint, OneDrive, or another Microsoft 365 location.

Copilot operates within the Microsoft Graph security boundary and strictly respects user permissions. If a saved prompt references File.docx but the user no longer has access to it—due to permission changes, file relocation, or removal—Copilot cannot retrieve the content for grounding. As a result, it cannot analyze or summarize the file and returns a processing-related error.

Not scheduling the prompt is unrelated to file processing. Running from a web or desktop app does not affect file readability. Using a different agent does not typically cause a file-format processing error.

Therefore, the most likely cause is that you do not have access to the file.

To ensure cited information is accurate, Microsoft’s AI guidance emphasizes human verification of AI-generated outputs, especially when the content will be used in formal business documents. Even when Copilot grounds responses in SharePoint files, it can still misinterpret text, summarize imprecisely, or attribute a statement to the wrong section of a source. The most reliable way to confirm accuracy is to check each citation against the original SharePoint document and validate that the claim is supported exactly as written.

Option A is the best answer because manual verification is the definitive control for accuracy and accountability. Option B may help by asking Copilot to re-check or restate where information came from, but it is still an AI-generated confirmation and does not replace direct source validation. Options C and D can improve consistency and reuse of standards or references, but they do not guarantee citation correctness; they still depend on model interpretation.

Therefore, the best approach is to manually verify the citations in the generated proposal content.

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.

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

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.

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

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

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 .

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.