Announcements
I found that there is less support on model-driven apps... They are not captured with get-adminpowerapp cmdlet, they are not captured with "Get Apps as Admin" Power Automate action, ...
If anyone can advise?
Hello @patrickpoon02,
This is probably because Canvas Apps and Model-Driven Apps are different, historically and technically.
You can still get a list of Model-Driven Apps from an environment, using the Dataverse connector.
Model-Driven Apps are stored in the "appmodules" table. Microsoft is using this in the Center of Excellence "Admin | Sync Template v3 (Model Driven Apps)" flow:
Yes I know about CoE and dataverse connector thing. However there is no PowerShell command to get the details and probably the app run detail, while still allow everyone to create such kind of apps (at least in default environment) is a nightmare to the Admins......
If we can expect only privileged user can create model-driven apps to perform something like Power BI, that makes sense and we don't need to worry a normal user will blindly create bunch of model-driven apps for testing.
I can understand your concern.
You can of course govern resource creation more granularly in non-default environments, but I'm not sure if this helps in your case.
Still, using the Dataverse connector mentioned earlier, you can at least manage apps that have been created in your default environment. The default environment is a "playground" by design, so every user has the Environment Maker role by design.
Have you tried removing the privilege for creating model-driven apps from the Environment Maker role in the default environment? I just tested this, and it seems to prevent users from creating model-driven apps.
Sorfy may I know how to prevent the environment maker to create model-driven apps?
Hi @patrickpoon02 ，
Sure. You could modify your maker role.
Best Regards,
Wearsky
Hi @v-xiaochen-msft ,
Thanks so much! Can this change applies to the default environment, that every licensed user will become Environment Maker automatically? We hope there is some control on default environment actually.
Patrick
Hi @patrickpoon02 ,
At my knowledge, you cannot change the permissions of users in the default environment .
Then we are still headache of unknown of any model-driven app created for whatever reason, in the default environment, by any user.....
So I think , you could use another environment instead of the default environment.
Because you cannot restrict users' behavior in the default environment.
Hi, the actual problem is, we cannot restrict any user from creating in default environment but we want to. We cannot just simply declare the default environment is a place for fun and allow unlimited (yet it is limited) creation of model-driven apps or allow anything happens - create any apps you want...we as admin need to know their existence and ask the creator to do the compliance thing. Without powershell or Power Automate action support this cannot happens.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 462
WarrenBelz 425 Most Valuable Professional
Vish WR 291
