AB-730 Exam Dumps - AI Business Professional

Microsoft 365 Copilot agents operate within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Custom agents created in the Microsoft 365 Copilot app are governed by organizational policies, role-based access control, and Microsoft Entra ID authentication.

According to Microsoft AI Business Professional guidance, Copilot agents are designed for enterprise use and are shared within the organization unless administrators configure broader sharing capabilities. External sharing with personal Microsoft accounts or arbitrary email addresses is not supported by default due to security, data protection, and compliance requirements.

Because the agent in this scenario interacts with organizational data such as client emails, project milestones, and internal reports, access must remain restricted to authenticated users within the same tenant. This ensures that sensitive business information remains protected and that data access respects existing permissions.

Therefore, the agent can be shared only with people in your organization, making option D the correct answer.

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

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.

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

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.

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.