Power Platform 2023 Release Wave 1: Five Features and Governance Gaps
Diesen Beitrag auf Deutsch lesen
Jukka Niiranen reviews five 2023 Release Wave 1 items, including manual administrator role assignment and governed personal Dataverse environments.
TL;DR
The 2023 Release Wave 1 plan introduces manual assignment of the System Administrator role and personal environments with Dataverse. Personal environments do not expire, do not require tenant administrator provisioning, and can be disabled by admins. Because makers can use premium capabilities independently, organizations should apply governance and DLP policies.
Original by Jukka Niiranen, on Jukka Niiranen Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Assess manual System Administrator assignment so tenant admin roles do not automatically expose all Dataverse business data.
- Admins/CoE: Decide whether personal environments should be enabled and apply DLP policies, because makers can provision them without administrator help.
- Makers: Test the new model-driven controls and responsive canvas layouts carefully, because the model-driven visual update initially uses an opt-in switch and may cause breakage.
- Leadership/Business: Treat release plans as changeable, since features may be added, delayed, postponed or cancelled before the wave ends.
Frequently asked questions
How does manual System Administrator role assignment change Dataverse access for tenant administrators?
It lets customers assign the System Administrator role to selected users instead of relying entirely on automatic assignment. This can reduce unnecessary business data access.
Can Power Apps personal environments use Dataverse without administrator provisioning?
Yes, personal environments let makers access premium capabilities such as Dataverse without tenant administrator provisioning. Administrators can disable the feature if governance requires it.
Why should organizations monitor the Power Platform Release Planner instead of reviewing release waves twice a year?
Release plans can change during the wave, with items added, delayed, postponed or cancelled. Regular monitoring gives a more current view of planned features.