Comments
Arguably the most critically important and long-overdue feature request ever submitted to the Power Platform Ideas forum, and I mean every word of that.The silent, invisible removal of security group assignments is nothing short of a governance nightmare. One moment your environment is locked down tight. The next, after a routine sandbox-to-production conversion or a backup restoration, the gates are wide open and nobody received so much as a single email. The exposure window could span hours, days, or even weeks before anyone notices. In enterprise security, that is an eternity.Every single available workaround, including Power Automate, Microsoft Purview, Microsoft Graph API, and Microsoft Defender, has been evaluated and confirmed incapable of covering this scenario. Administrators are left flying completely blind on a platform trusted by tens of thousands of enterprise organizations worldwide.A native, built-in email notification system within PPAC, scoped at both the environment and tenant level, with configurable recipients and real-time delivery, would single-handedly elevate Power Platform's security and governance story to an entirely new tier. And by laying the foundation for a broader PPAC notification framework covering DLP policy changes, environment type conversions, and Managed Environment updates, this idea has the potential to become the cornerstone of proactive Power Platform governance for years to come.Every enterprise administrator on the planet will immediately put this to use and wonder how they ever lived without it. Highest possible vote of confidence. Ship this. Please. Yesterday.
Suggested Enhancement ScopeTo minimize implementation impact while maximizing flexibility, we propose:1. Organization-Wide Default Setting (Primary Requirement) Allow administrators to define a default font family and size for the Rich Text Editor across the organization. This ensures consistent formatting with minimal behavioral changes.2. Rich Text Editor Default Configuration (Optional / Advanced) Allow configuration of default font settings at the Rich Text Editor control level, enabling:Different defaults per entity (Email, Case, Knowledge Article)Different defaults per field (optional)Future extensibility without breaking existing behaviorThis approach minimizes impact while providing long-term flexibility and maintainability.
Main purpose: Enable organization-wide default house style to ensure consistent formatting, accessibility compliance, and professional communication across all emails and rich text fields.Need : reasonably high , we now have to select all communication in de edtior before sending, Go way down in the font pulldown (no first letter press support) and then select our size. Editor easily shifts back to Segoe UI 9 which is NOT our standard. Gives user the idea that de editor is working faulty