Default Environment Purpose - No Backup for CDS

[mike528]

I learned over the last few days that CDS backups are not supported in default environment. This was the official response from Microsoft support. I find this odd, it's not documented anywhere that I could find, and there is no error message when you try to get to the backups through the admin portal, you simply can't get to that functionality. New experience doesn't even show the backup/restore link.

So, my open question is "what is the purpose and intended use for the default environment?".  Power Apps using CDS certainly would not be one since it can't be backed up. Anyone know of a good article on this topic or have otherwise determined when it's appropriate to use the default environment? Or the intent to always create another environment. However, last time I checked, you cannot use Data Gateway in environments other than default. 

Thanks

[v-yutliu-msft · Accepted solution]

Hi @mike528 :
1)the usage of default environment

Whenever a new user signs up for PowerApps, they are automatically added to the Maker role of the default environment.

So you could see default environment as a public environment of your tenant.

The data and apps are public by default in this environment.

Here's a doc about default environment for your reference:

https://docs.microsoft.com/en-us/power-platform/admin/environments-overview

2)the reason why you need to create other environments

You could see environment as a space including data and apps.

The data and apps belong to one environment, then other environments can not use them.

So you could see environment separating data and apps in different spaces.

On one hand, it could help distinguish data and apps. For example, usually, we will use an environment for development, one for production.

On the other hand, it could ensure data's security. Make different users have different permission on different environments.

What's more, it could also ensure data's integrity by creating different data loss policy in different environments.

3)can not use gateway in other environments except default environment

Yes, it is gateway's limit.

Gateways and on-premises connections can only be created and used in the user's default environment.

Here's a doc about it for your reference:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/gateway-management

Best regards,

[mike528]

@v-yutliu-msft 

Thank you for the post but I fail to see the point to having an environment (default) that will allow you to create a CDS database and create apps updating it, with no ability to back it up.

I do understand the point to the other environments. Unfortunately, trying to move my CDS customizations to a new environment continues to fail with no real error message. I've since decided to go back to Azure SQL DB where I have control. Running into too many issues with CDS and getting black box error messages. Sad, I was looking forward to utilizing it. Maybe after some bugs are worked out.

With reference to the gateway, how would you expect to create an app in an environment other than default that needs to access on-prem data? ALM using environments goes out the window. Are there no exceptions to using gateways in other environments?

Thanks

[Anonymous]

This question is unanswered. What is the purpose of the Default Environment. The answer above and link provided does not answer this. Anyone from Microsoft out there that can clarify please?

[mjburley]

Being cynical, I would say the point of the default environment is to make work for IT admins.

Really, it's for non IT users to play around with Flows/apps. And to handle a few scenarios like Flows to run from buttons in Teams (only works in Default a few months ago).

In my org, I have created 3 new power app environments, dev, test, prod. These are where "real" applications / apps / flows are built and deployed, primarily by IT techies.

Use the MS centre of excellence to monitor apps/flows built in Default to check on usage and shared users, and if it gets to a certain point contact that user and see if the app/flow needs to be pushed into the dev/test/prod environments.

The Default environment soon becomes very messy with people making entities (CDS) left, right and centre, modifying the User entity etc.