AB-730 Questions Bank

Microsoft 365 Copilot can be accessed via its dedicated web experience for enterprise users. The correct web entry point for Microsoft 365 Copilot is , which provides authenticated access to Copilot features within the Microsoft 365 environment.

This URL routes users into the Microsoft 365 ecosystem where Copilot integrates with organizational data such as SharePoint, OneDrive, Teams, and Outlook. It ensures that users are authenticated through Microsoft Entra ID and that access controls are enforced according to tenant policies.

Option B refers to Copilot Studio, which is used to build and manage custom copilots and agents rather than access the Microsoft 365 Copilot chat experience. Option C (My Apps) is a general application launcher portal. Option D is an incorrect account management URL and does not provide Copilot access.

Therefore, to access Microsoft 365 Copilot from a web browser, the correct URL is .

Microsoft 365 Copilot can use Microsoft Graph-grounded data (based on the user’s permissions) to help users work with Microsoft 365 content. This includes surfacing and summarizing information from Teams chats, so statement 1 is true. Copilot can also summarize and generate content related to Teams meetings (for example, meeting recap details, key discussion points, and follow-up actions when meeting artifacts such as transcript/notes are available), and it can answer questions and draft related content—so statement 3 is true.

Statement 2 is false because, while Copilot can draft emails and help prepare messages, it does not independently schedule and send emails automatically “based on conditions” as a native Copilot function. Conditional sending is typically handled through workflow automation tools (for example, Power Automate) and still requires appropriate configuration, permissions, and governance. In enterprise environments, this separation helps reduce risk by ensuring that automated outbound communication remains controlled, auditable, and compliant.

The first statement is correct because Microsoft 365 provides transparency and user control through the My Account portal, where users can review their Copilot activity history. This aligns with Microsoft’s responsible AI and data governance principles, ensuring visibility into AI interactions.

The second statement is incorrect. Deleting Copilot activity history removes stored interaction records (such as prompts and responses), but it does not automatically delete associated notebooks, documents, or pages stored in services like OneDrive or SharePoint. Those files remain governed by standard Microsoft 365 retention and lifecycle policies.

The third statement is correct because users can delete their entire Copilot activity history, including both prompts and generated responses. This reinforces enterprise-grade privacy controls and regulatory compliance requirements.

These controls demonstrate core generative AI fundamentals: transparency, user data ownership, security boundaries, and responsible lifecycle management of AI-generated interactions within Microsoft 365 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.