microsoft / microsoft/Power-CAT-Copilot-Studio-Kit
Bug: Copilot Studio Governance Kit sends malformed welcome email with blank agent name during first-time deployment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 450
- Forks
- 95
- Avg merge
- 26m
- Merged PRs (30d)
- 5
Description
Description
Product
Microsoft Copilot Studio Governance Kit
Severity
High
Impact
- All makers received an unexpected email.
- Email subject contains an empty agent name (""), reducing confidence in the governance solution.
- Creates confusion during initial rollout.
Environment
- First-time installation of the Copilot Studio Governance Kit.
- All solution flows were enabled immediately after deployment.
Steps to reproduce
Steps to Reproduce
- Install the Copilot Studio Governance Kit.
- Configure the solution.
- Turn on all Power Automate flows.
- Wait for onboarding notifications to be sent.
Actual Result
All makers receive an email with the subject:
Welcome to Copilot Studio Governance for “” – What Makers Need to Know
The agent/governance name is blank.
Expected behavior
Expected Result
The email should either:
- Populate the configured governance or agent name correctly, or
- Use a default value when no name is configured, or
- Prevent sending until the required configuration is complete.
Suggested Product Improvement
Microsoft could improve the Governance Kit by:
- Validating required configuration before notification flows are enabled.
- Preventing onboarding emails until mandatory fields are populated.
- Providing default fallback values in email templates.
- Including a deployment health check to detect missing configuration.
This would prevent unintended communications during first-time deployment and improve the
administrator experience.
Actual behavior
All makers hundreds of them receive an email from me with the subject:
Welcome to Copilot Studio Governance for “” – What Makers Need to Know
The agent/governance name is blank.
Environment
No response
Additional context or logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.