Add FAQ documentation for Inactivity Notification flows governance #10769
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.
Users deploying Inactivity Notification flows commonly misunderstand environment scope (believing flows only scan environments visible in the Environment table) and test mode configuration (wanting to redirect approvals to their own account during testing).
Changes
CenterofExcellenceResources/FAQ-InactivityNotifications.md: Comprehensive FAQ addressing environment scope, test mode configuration, orphaned resource handling, customization, and troubleshooting for the Governance/Audit Components inactivity flows
docs/issue-response-templates.md: Reusable response template for inactivity notification questions
CenterofExcellenceResources/README.md: Index for all FAQ documents in the directory
Documentation/README.md: Links FAQ section to improve discoverability
Key Technical Clarifications
Environment Scope: Flows query entire
admin_apps/admin_flowstables across all tenant environments. Only filters onadmin_excusefromarchivalflows ne trueandadmin_environmentdeleted ne true. The Environment table is metadata storage, not a query filter.Test Mode: When
admin_ProductionEnvironment = No, approvals route to theadmin_AdminMailenvironment variable value (not to a separate test user variable). Change this variable to redirect test approvals.Flow logic reference:
Documentation validated against flow definitions in
CenterofExcellenceAuditComponents/SolutionPackage/src/Workflows/AdminInactivitynotificationsv2*.json.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.