Disable notification and governance flows by default to prevent unexpected emails on upgrade #10648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After upgrading to v4.50.7 (Core) and v3.27.6 (Audit), 18 notification and governance flows were auto-enabled, sending thousands of emails and potentially executing destructive actions (environment deletion, app quarantine) without admin configuration.
Changes
Flow state changes (18 flows)
StateCodefrom0(Active) to1(Draft)StatusCodefrom1(Activated) to2(Draft)Affected flows:
Documentation added:
NOTIFICATION_FLOWS_GUIDE.md: Flow catalog, configuration, best practicesSTOP_AUTOMATIC_EMAILS.md: Immediate fix for affected usersCHANGE_SUMMARY.md: Technical details and impact analysisREADME.md: Prominent notice linking to guidesExample
Admins must now explicitly enable flows through Power Automate or the Setup Wizard. This prevents surprise activations while maintaining full functionality when intentionally enabled.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.