Bug: Copilot Studio Governance Kit sends malformed welcome email with blank agent name during first-time deployment

[zenchong333]

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

1. Install the Copilot Studio Governance Kit.
2. Configure the solution.
3. Turn on all Power Automate flows.
4. 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

[SiddharthPoweCat]

Hi zenchong333 — thanks for the detailed report. You're right, and we've confirmed the root cause.

Root cause

The subject line of the AgentCompliance_WelcomeEmail template (Compliance Hub) has a malformed placeholder in the shipped solution:

Welcome to Copilot Studio governance for “({AgentName}}” — what makers need to know

It should be {{AgentName}}, not ({AgentName}}. The email body uses the correct {{AgentName}} syntax, which is why only the subject renders blank.

Substitution is performed by the Email Template Replacement AI Builder prompt, whose instructions are "Only replace placeholders that have corresponding values… If a placeholder does not have a matching value, omit the sentence that contains the placeholder." Since ({AgentName}} isn't a valid token, it's never matched — so it's dropped, leaving for “”.

Importantly, the data itself is fine: Agent Compliance | Create Case (Child) → Send_Welcome_Email does pass AgentName correctly. This is purely a template typo, not a configuration problem on your side.

Verified in Copilot Agent Kit (solution unique name CopilotStudioAccelerator) version 20260708.6 — the June 2026 release.

Can you confirm your solution version?

So we can scope the fix and confirm you're not also hitting something already addressed:

1. Go to Power Apps → Solutions in your environment.
2. Find Copilot Agent Kit (or Copilot Studio Accelerator on older installs).
3. Share the Version value (e.g. 20260708.6) and the release you installed from.

Immediate fix

Email templates are customizable, so you can correct this now:

1. Open the Compliance Hub app → Settings → Email Templates.
2. Open AgentCompliance_WelcomeEmail.
3. In the Subject, replace ({AgentName}} with {{AgentName}}.
4. Save. New sends will render the agent name correctly.

Preventing the mass send on first deployment

Worth calling out: the welcome email fires the first time a maker is inventoried. On a first-time install the Agent Inventory scan discovers every existing agent at once, so every maker is notified in one burst.

Per COMPLIANCE_HUB.md, leave Admin Approval Before Maker Notification = Yes (the default) during initial rollout. With it enabled, no notifications are sent and no SLA countdowns start until an admin explicitly sends them from the case details screen — letting you tune thresholds and review the caseload first. You can also temporarily set Send Case Alerts To Maker Via Email / Via Teams to No while validating.

[AthenaZen]

hi thanks - for your response
App name: Copilot Studio Kit
Organization name: Power Platform Solutions
Channel: Monthly - July 2026 (app)
Server version: 9.2.26073.00158
Client version: 1.4.12235-2607.3
Time: 17/08/2026 3:38:24 pm GMT+0800 (Singapore Standard Time)

Immediate fix
There is nothing to fix, didn't have bracket
We are reaching out to let you know that your new agent, "{{AgentName}}", has been automatically registered in our internal Agent Inventory.

finally also I can't find the compliance_hub.md