A company is creating a Microsoft Power Platform app to enable employees to log daily time entries. Employee user accounts are in multiple Azure AD…

The scenario describes a security model where users gain privileges through their membership in a team. The security role, which contains the necessary permissions for app functionality (including creating personal views via the 'Saved View' privilege), is assigned to the team. Users, including the guest users from other tenants, are then added as members to this team. Their effective permissions are the sum of any roles assigned directly to them plus the roles assigned to all teams they are a member of. This is a standard and recommended Dataverse security pattern for managing access for groups of users.

A. Direct basic level: This is incorrect because the scenario explicitly states that the security role is assigned to the team, not directly to the user.

B. Azure AD security group: While the Dataverse team can be linked to an Azure AD security group, the construct that holds the security role within Dataverse is the "Team," making it the more precise answer.

D. Shared app access: This grants a user the ability to open the model-driven app but does not grant the underlying Dataverse data privileges needed to interact with records or create personal views.

1. Microsoft Learn, Power Platform documentation. "Security concepts in Microsoft Dataverse - Teams." This document states, "A team is a group of users... A team can own records and can have security roles assigned to the team. When a security role is assigned to a team, all members of the team inherit the privileges of that role." This directly supports the use of a team to grant privileges to its members.

2. Microsoft Learn, Power Platform documentation. "Security roles and privileges." Under the "Privilege reference" section, the "Core Records" tab is detailed. It lists the "Saved View" privilege, which is required for a user to create, update, and delete their own personal views. This privilege would be configured within the "Employee Security role" that is assigned to the team.

3. Microsoft Learn, Power Platform documentation. "Collaborate with guests in an environment." This document explains the process for adding guest users and notes that their security can be managed by adding them to Azure AD security groups, which are then used to create Dataverse teams that are assigned security roles. This confirms the scenario's architecture is a valid implementation pattern.