Assignable Security Roles for Dataverse Environment without Database

Correct Answers: B and D

When you create a Dataverse environment without a database, you have only two security role choices: Environment Maker and Environment Admin.

Environment Maker can create new resources, like apps, flows, connections, gateways; share the apps with the users in an organization.

But this role does not have privileges to access the environment's data.

Environment Admin can perform all administrative tasks in the environment, like add and remove users from Environment Maker or Admin roles; provision Dataverse database, and view and manage the environment's resources.

Option A is incorrect because System Customizer is a Dataverse security role for the environments with the Dataverse database.

Option C is incorrect because System Administrator is a Dataverse security role for the environments with the Dataverse database.

Option E is incorrect because Basic user (previously Common Data Service User) is a Dataverse security role for the environments with the Dataverse database.

For more information about Dataverse security roles, please visit the below URL:

It is not possible to create a Dataverse environment without a database. Therefore, it is difficult to provide an accurate answer to this question without more context. However, assuming that the question is referring to a scenario where a Dataverse environment has been created but no database has been added, the correct answer would be as follows:

In this scenario, you can assign the following security roles to the users of the environment:

A. System Customizer: This role can be assigned to users who need to customize the system but do not require administrative privileges. Users with this role can create and modify system entities, fields, forms, views, and dashboards, but cannot perform administrative tasks.

B. Environment Maker: This role can be assigned to users who need to create and manage environments but do not require administrative privileges. Users with this role can create and manage environments, but cannot perform administrative tasks.

C. System Administrator: This role can be assigned to users who need full administrative access to the system. Users with this role can perform all administrative tasks, including managing security, creating and modifying system entities, and managing environments.

D. Environment Admin: This role can be assigned to users who need to manage environments but do not require full administrative privileges. Users with this role can create and manage environments, manage users and security, and perform other administrative tasks related to the environment.

E. Basic User: This role can be assigned to users who need basic access to the system but do not require administrative privileges. Users with this role can view and edit data in the system but cannot perform administrative tasks.

It is important to note that the specific roles that can be assigned to users may vary depending on the configuration of the system and the permissions granted to the user creating the environment. Therefore, it is recommended to consult the system documentation or seek assistance from a qualified professional to ensure the correct security roles are assigned.