You’re offline. This is a read only version of the page.
Announcements
When using the Design Studio in Power Pages, switching between Azure AD B2C configurations does not remove the original site settings. Legacy identity provider configurations and client IDs persist in Dataverse, even though they are hidden from view within the Design Studio interface.
This introduces a serious security risk. During soft launches or production cutovers, it is entirely possible for non-production identity providers to remain active and registered with a live portal, without any visible trace in the design interface.
From a security and governance perspective, this is untenable. Any tool used to configure authentication, user flows, or form behavior must provide full traceability, visibility into changes, and administrative control. Until Design Studio meets these standards, I will continue directing my developers to bypass it entirely, use direct HTML and Liquid editing, and manage all site settings explicitly through the backend.
Does anyone have visibility into the Design Studio roadmap, especially around change tracking, reversibility, and secure configuration handling? Frankly speaking, this entire tool is a trap for newcomers to PowerPages and frequently creates desynchronization between Dataverse and whatever storage the design studio uses.
Share
Report
All responses (
Answers (
53,315
