Add documentation for filtering maker notifications by environment and user

[Copilot]

Users asked if maker notifications can be restricted to specific environments or pilot users. The CoE Starter Kit supports this through flow customization, but lacked documentation.

Documentation Added

Created comprehensive guides in CenterofExcellenceResources/:

• ANSWER-RestrictMakerNotifications.md - Direct answer with solution overview
• QuickReference-MakerNotificationFiltering.md - Quick reference for common scenarios and troubleshooting
• FilteringMakerNotifications.md - Complete overview of filtering approaches, best practices, and upgrade considerations
• HowTo-RestrictNotificationsToEnvironment.md - Step-by-step environment filtering implementation with PowerShell commands
• HowTo-RestrictNotificationsToPilotUsers.md - Step-by-step pilot user filtering with multiple implementation methods
• README.md - Navigation index for all resources

Implementation Approaches

Users can filter notifications via:

1. Environment filtering - Create environment variable admin_NotificationAllowedEnvironments with comma-separated GUIDs
2. Pilot user filtering - Create environment variable admin_NotificationPilotUsers with semicolon-separated emails
3. Hybrid - Combine both approaches for maximum control
4. Simple - Turn off flows in non-pilot environments

Example Configuration

# Environment Variable for Environments
Name: admin_NotificationAllowedEnvironments
Value: env-guid-1,env-guid-2,env-guid-3

# Environment Variable for Pilot Users
Name: admin_NotificationPilotUsers
Value: user1@contoso.com;user2@contoso.com;user3@contoso.com

Flows require condition logic to check maker's environment/email against these lists before sending notifications. Implementation time: 20-45 minutes depending on approach.

Affected Flows

• Admin | Welcome Email v3
• Admin | Compliance Details Request eMail (Apps/Flows/Connectors/Chatbots/Desktop Flows)

Documentation includes flow modification examples, troubleshooting guides, and upgrade considerations.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[CoE Starter Kit - QUESTION] can we target maker notification email to specific environment?</issue_title>
<issue_description>### Does this question already exist in our backlog?

• I have checked and confirm this is a new question.

What is your question?

Hi Team, I want to restrict the maker notification email to specific environment. Kindly suggest do we have any configuration settings for the same or can we restrict the maker notification emails to specific set of users to do test pilot run

What solution are you experiencing the issue with?

Governance

What solution version are you using?

No response

What app or flow are you having the issue with?

No response

What method are you using to get inventory and telemetry?

None</issue_description>

<agent_instructions>Can we restrict maker notification for specific environment.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.

• Fixes [CoE Starter Kit - QUESTION] can we target maker notification email to specific environment? #10594

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.