Power Platform Community Forum Thread Details

A recent change has caused a change in behavior when creating powerapps environment. This has ties into dynamics now.

When I create a new PA environment, and select to also create a database, it creates a NEW dynamics 365 instance.

I have tested with a normal user, and they are also able to create "trial" environments, which also creates a trial dynamics instance.

Why is this? I have no need of an additional Dynamics instance. I do not want to pay for it. I just want a backend CDS DB.

The fact that an average user cannt also create trial environments could also cause lots of needless work for support to clean up.

On top of all that, there is NO documentation that I can find that explains this in any way shaore of form.

I think this is hugely irresponsible on the part of MS.

If this is how it is to work, I need a way to restrict the ability to create new environments.

Categories:

Microsoft Dataverse with Power Apps

Hi @Anonymous - I'm sorry to hear this has caused problems. The latest version of CDS using the same platform as Dynamics 365 applications, which is why you are seeing Dynamics 365 instances, this is intentional. You however only need to be licensed for PowerApps or CDS, you don't also need to worry about getting a Dynamics 365 instance. The intent is that it gives you the same CDS functionality available in the past.

You can read more about the updates and changes here : https://powerapps.microsoft.com/en-us/blog/cds-for-apps-march/ and https://powerapps.microsoft.com/en-us/blog/powerapps-spring-announce/

As for restricting creation, I'm adding @ManasMSFT from the admin team.

Thanks,

Clay.