CRM Crate

Understand and enable default environment routing in Power Platform

We will get to know the concept & fundamentals of default environment routing and learn to activate it in Power Platform. Before we start, make sure to subscribe to CRM Crate so that you can stay up to date in the field of Power Platform.

Understanding & activating default environment routing in Power Platform?

A Power Platform environment serves as a hub for managing, overseeing, and disseminating your company’s business data, applications, chatbots, and workflows. Moreover, it serves as a compartmentalization tool to differentiate applications based on different roles, security requirements, or target user groups, such as sandbox and production environments.

Further, the developer environments are unique environments designed exclusively for the owner’s use. While you have the option to limit users from generating developer-type environments through the Power Platform admin center, it’s important to note that if a user possesses a Microsoft Power Apps for Developer license, a developer environment will automatically be generated upon the user’s next login.


Concept of default environment routing in Power Platform

Default environment routing stands as a high-quality governance feature, granting Power Platform administrators the ability to guide new makers seamlessly into their individual developer environments upon their initial visit to Power App Maker Portal (make.powerapps.com).

Now, with the Default Environment Routing setting activated, a new maker, upon their initial visit to make.powerapps.com, opens a dedicated personal developer environment rather than the default environment. New Power Platform makers don’t need to learn about which environment to work in since this happens automatically from backend.

The below diagram demonstrates the working of default environment routing.

Microsoft Dataverse is accessible within developer environments, which are Managed Environments featuring preconfigured admin settings like solution checker. System admins can now rest assured that their makers are not working in the default environment, mitigating the risk of conflicts with others’ work.
Important Note (As of January 2024):
1. Currently the Default Routing feature is a preview feature.
2. Preview features are not intended for production use and might have limited functionality. They are offered before an official release to grant customers early access, allowing them to provide feedback.
3. By default, all developer environments are created through environment routing are managed.


Enabling default routing feature

Below are the two ways to enable the default routing feature in Power Platform.

Power Platform Admin Center

1. Within the navigation pane of the Power Platform admin center, choose “Settings.”
2. Navigate to the Tenant settings page and choose “Environment routing (preview).”
3. Enable the “Create personal developer environments for new makers” option in the Environment routing pane.

PowerShell Snippet

1. Open PowerShell and log in to your Microsoft tenant account.
2. Fetch and store your Microsoft tenant settings in tenantSettings.
3. Enabling the default routing by setting the enableDefaultEnvironmentRouting flag to True.
Below is the PowerShell code for each of the above steps.
$Add-PowerAppsAccount -Endpoint "prod" -TenantID <Tenant\_ID>
$tenantSettings = Get-TenantSettings
$tenantSettings.powerPlatform.governance.enableDefaultEnvironmentRouting = $True

Set-TenantSettings -RequestBody $tenantSettings

5 1 vote
Article Rating
Subscribe
Notify of
2 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Create a Virtual Table in Power Apps using OData v4 Data Provider [Complete Guide] - CRM Crate
5 months ago

[…] In Power Apps, a virtual entity is a representation or abstraction of data that doesn’t physically exist within the Dataverse database. Instead, it is a dynamic table that retrieves and displays data from an external data source such as OData v4 in real-time. Virtual tables leverage external data sources through the OData v4 Data Provider, allowing users to interact with and manipulate data seamlessly within the Power Apps environment. […]

Advantages & disadvantages of using Virtual Tables in Power Apps - CRM Crate
5 months ago

[…] OData v4 Data Provider, allowing users to interact with and manipulate data seamlessly within the Power Apps environment. By creating virtual tables, users can integrate and work with data from external systems without […]

error: CRM Crate Security Engine - Disabled Right Click & Selection!

Congratulations!

Well Done,
Welcome to CRM Crate

Stay tuned with us and get all latest updates and learning in Microsoft CRM and related techonologes.