AB-730 Exam Questions Tutorials

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.

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

When you share a Microsoft 365 Copilot prompt that references files stored in OneDrive, the prompt sharing action does not automatically change file permissions. Copilot follows the Microsoft 365 permission model, meaning users can only access, summarize, analyze, or ground responses in files that they already have permission to open.

Option C is correct because the shared prompt can be used successfully with the referenced files only if the recipient already has access to those OneDrive files. Sharing the prompt shares the prompt structure and instructions, not the underlying file access rights. This prevents accidental exposure of private or confidential business documents.

Option B is incorrect because Copilot does not automatically grant access to files when a prompt is shared. Option A is too strong because the files are not necessarily removed from the prompt; they remain referenced but usable only if permissions allow. Option D may happen in some Microsoft 365 file-sharing contexts, but the best general rule is that access must already exist or be granted separately.

Therefore, the user can run the prompt successfully only if they have access to the referenced OneDrive files.

Microsoft 365 Copilot operates within two primary knowledge boundaries: its foundational large language model training data and the organizational data available within the Microsoft 365 tenant. However, Copilot strictly enforces Microsoft’s security and compliance model, meaning it only retrieves and uses data that the signed-in user is authorized to access.

When using the Work scope, Copilot combines the general knowledge it was trained on with organizational data such as documents, emails, chats, calendars, and files stored in Microsoft 365. Importantly, Copilot respects role-based access control and existing permissions. It does not surface information from content the user does not have access to.

Option A is incomplete because Work scope includes organizational data. Option B is incorrect because Copilot does not access all tenant data indiscriminately; it is permission-scoped. Option D is incomplete because Copilot also leverages its general training knowledge.

Therefore, the correct explanation is that Copilot provides responses based only on data the user can access, combined with its general training knowledge.

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.