Start preparing for your Next Exam | Use coupon – TOGETHER | Avail 30% discount

Overview to Manage Environment

  1. Home
  3. Overview to Manage Environment

We may define an environment as a space to store, manage, and share our organization’s business data, apps, and flows. Also, the environment serves as a container to separate apps having different roles, security requirements, or target audiences. We shall now learn more about scope, permissions of an environment as well as manage the environment.

Scope of an Environment

We shall now discuss the scope of the environment –

  • Firstly, every environment has been built under an Azure Active Directory (Azure AD) tenant, and its resources can only be accessed by users within that tenant. 
  • Secondly, when we create an app in an environment, that app is routed only to datacenters in that geographic location. Moreover, any items that is created in that environment are also bound to their environment’s location.
  • Thirdly, every environment can have zero or one Microsoft Dataverse database, which provides storage for your apps.
  • Next, when we create an app in an environment, that app is only permitted to connect to the data sources that are also deployed in that same environment

Permissions in an Environment

The environments offers two built-in roles that provide access to permissions within an environment –

  • Environment Admin role can perform all administrative actions on an environment including – Add or remove a user or group, Provision a Dataverse database, View and manage all resources and Set data loss prevention policies.
  • Environment Maker role can create resources within an environment including – apps, connections, custom connectors, gateways, and flows using Power Automate.

Types of Environment

There are various types of environment indicating the purpose and characteristics of an environment.

Production

Some of the features of the Production environment include –

  • First, the production environment is used for permanent work in an organization.
  • Second, it can be created and owned by an administrator or anyone with a Power Apps license with 1 GB available database capacity.
  • It is also created for each existing Dataverse database when it is upgraded to version 9.0 or later.
  • Next, the production environments are used for any environments on which you can depend.
  • Then in terms of security, production offers full control
Default

Some of the features of the default environment include –

  • First, the production environment is used for permanent work in an organization.
  • Secondly, it can be created and owned by an administrator or anyone with a Power Apps license with 1 GB available database capacity.
  • Also, it is created for each existing Dataverse database when it is upgraded to version 9.0 or later.
  • The production environments are used for any environments on which you can depend.
  • Then, in terms of security, default offer limited control. All licensed users* have the Environment Maker role.
Sandbox

Some of the features of the sandbox environment include –

  • Firstly, these are non-production environments, taht offer features including copy and reset.
  • Secondly, sandbox environments are used for development and testing, separate from production.
  • Also, provisioning sandbox environments can be restricted to admins.
  • Moreover, converting from a production to a sandbox environment can’t be blocked.
  • Lastly, Sandbox offers Full control. Also, when used for testing, only user access is needed. Developers require Environment Maker access to create resources
Trial

Some of the features of the trial environment include –

  • Firstly, trial environments are designed to support short-term testing needs and are cleaned automatically after a short time span.
  • Trial environment expires after 30 days and are limited to one user.
  • Also, provisioning trial environments can be restricted to admins.
  • Lastly, Trial environment offer full control
Developer
  • Firstly, developer environments are primarily created by users that have Community Plan license.
  • Secondly, developer environments are specifically for use by the owner, and they can’t be shared with other users.
  • Also, provisioning developer environments can’t be restricted unless through a support ticket.
  • Lastly, in this environment only a single user account with the Community Plan has access.
Microsoft Dataverse for Teams
  • Firstly, Dataverse for Teams environments are created automatically for the selected team
  • Secondly, when we create an app in Teams using the Power Apps app for the first time or install a Power Apps app from the app catalog.
  • The environment offers limited control.
  • Admins have limited settings available for Teams environments.
  • Also, No customizations of security role or assignments are available.
  • Lastly, Teams members are automatically mapped to their Teams membership type – Owners, Members, and Guests – with a corresponding security role assigned by the system.
Menu