New from Microsoft this week: PowerApps Environments.
The quick and short story is that environments will be another taxonomy-element-like container.
- In SharePoint we have: Site Collections –> Webs –> List and Libraries.
- In PowerApps we’ll have: Environments –> Apps, Flows, and Common Data Service databases.
As with site collections in SharePoint, Environments will be the containers with ‘high fences’ between them. All part of the same tenant (or ‘server farm’ in legacy SharePoint-speak). Environments will give us a convenient way to group and isolate objects – for management, permissions, and Dev/Test/Prod scenarios.
Also in the blog post comments: There is an announcement coming soon regarding GA (General availability) timeline – getting past ‘preview’ stage). Woo hoo!
Environments have a few roles defined.
- Environment Admins will operate much like tenant or server admins in that they can create environments and manage the settings and policies for them.
- Environment Makers are somewhat analogous to Site Collection Administrators or Site Designers. They’ll be able to create new apps, connections, etc. and assign permissions to users of those apps.
PowerApps Admin Center
A new feature to PowerApps for managing environments and more. More to come on the details of this one, but I expect it’ll be a blend of what we’ve seen with other O365 Admin controls and/or similar to what we’ve seen with ‘site settings’ in SharePoint in the past.
- There’s a webinar on 10/27
- Blog post coming this week for more migration details:
No new links available yet in the Learn section, but I expect them to be available soon…