When you use Microsoft 365 Copilot Chat without a Microsoft 365 Copilot license, Copilot Chat operates in a “general” mode rather than a Microsoft Graph-grounded work mode. In this configuration, Copilot does not have the entitlement to access and reason over your organization’s protected Microsoft 365 content (such as SharePoint sites, OneDrive files, Outlook mail, Teams messages, or other tenant resources). It also does not connect directly to your organization’s internal databases unless separate, explicitly configured integrations exist.

Instead, Copilot relies on three primary sources to generate a response: (1) the prompt context you provide in the current request (what you ask, plus any text you paste), (2) the conversation history within the current chat thread to maintain continuity, and (3) internet search data (when web grounding is available) to supplement general knowledge with up-to-date public information.

Therefore, the correct selections are C (prompt context), E (internet search data), and F (conversation history), while organizational Microsoft 365 data and Teams chat data are not used without the Copilot license.

Copilot in Word assists with content generation, summarization, rewriting, and structural organization. It can analyze document headings and insert a table of contents based on structured heading styles, supporting document navigation. It can also generate summaries of key points, which aligns directly with generative AI text analysis capabilities.

Custom watermark formatting and precise page margin configuration are traditional Word formatting functions and are not core generative AI capabilities of Copilot.

Therefore, the correct answers are A and C.

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

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

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.

The Describe tab is where you leverage generative AI to help build an agent by describing what you want the agent to do in natural language. Instead of manually configuring everything first, you provide the agent’s purpose, target users, tone, and the tasks it should perform (for example: “Create an onboarding agent that answers HR policy questions in a friendly tone and references SharePoint policies”). Copilot then uses that description to propose an initial agent setup—such as suggested behaviors, starter prompts, and structure—accelerating agent creation and improving consistency. By contrast, the Configure tab is typically used to fine-tune and finalize settings (such as knowledge sources, actions, and other parameters) after the agent concept is established. A Copilot notebook or Copilot page can help organize content and outputs, but they are not the primary place where generative AI “builds” the agent definition. Using the Describe tab reflects best practice: start with clear intent and constraints, then refine configuration for governance, accuracy, and usability.

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.

a specific date range of activity

The Microsoft 365 My Account portal provides users with control over their Copilot activity history in alignment with enterprise privacy and compliance standards. When selecting Delete history, users can remove Copilot activity based on a defined time range rather than deleting only a single conversation or all activity universally.

This functionality reflects Microsoft’s commitment to transparency, user control, and responsible AI governance. Allowing deletion by date range enables organizations and individuals to manage data retention policies efficiently while maintaining compliance with regulatory frameworks such as GDPR and internal data governance policies.

The other options are incorrect because deleting a specific conversation or all conversations with a specific agent is not the primary method offered in the My Account activity deletion setting. Instead, deletion is structured around activity time periods.

This capability reinforces generative AI best practices: secure data management, lifecycle control of AI interactions, and user-directed privacy management within enterprise environments.

Enterprise data protection (EDP) (often referred to as commercial data protection) is the capability that ensures Microsoft 365 Copilot handles organizational data under enterprise security and privacy guarantees. With EDP, Copilot processes prompts and responses within the customer’s Microsoft 365 boundary, respecting tenant isolation and identity-based access controls. This means Copilot only retrieves and uses data that the signed-in user is permitted to access, and the data remains governed by Microsoft 365 compliance features (such as retention, eDiscovery, audit, and Purview controls). Critically, EDP ensures that your organization’s prompts and the retrieved business content are not used to train the underlying AI foundation models. This is essential for protecting confidential business information and meeting regulatory and contractual requirements. The other options (Common Data Model, sensitivity labels, and Zero Trust) support data structure, classification, and security posture, but they do not specifically represent the Copilot guarantee that tenant data stays protected and is not used for model training.

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.