No-code policy enforcement for AI and human-authored customer emails, now in public preview
Microsoft announced Governance for Dynamics 365 Customer Service on April 29, 2026. The feature is now available in Public Preview. In short, it checks every outbound customer email before it gets sent. It validates the email against policies that administrators define. This applies to emails written by service reps and emails generated by AI. At launch, Governance covers the email channel only. Microsoft chose email first because it carries the highest compliance and brand risk.
How Dynamics 365 Customer Service governance works
As AI adoption grows in customer service, organizations face a new challenge. How do you make sure AI-generated emails follow your internal policies? How do you stay compliant with regional regulations? That’s exactly what Governance is designed to solve.
The feature works as a real-time enforcement layer. Before an email leaves the organization, the system checks it against active policies. If it finds a violation, it can block the message, log the issue, or send it for manual review. The rep then sees what failed and can update the draft accordingly.
Governance features and capabilities at a glance
Governance includes five core capabilities out of the box:
For example, an admin can write a policy like “Block any mention of competitor names.” The system then automatically enforces that rule on every outgoing email. No coding or technical support is required.
Where governance lives inside Dynamics 365 Customer Service
Governance is delivered as a skill within the Quality Evaluation Agent in Dynamics 365 Customer Service. It sits alongside the Quality Evaluation skill, which reviews past interactions for quality standards. Together, these two skills create a connected framework for compliance, quality, and policy enforcement.
This is also significant in the context of the 2026 Release Wave 1. Microsoft has been deepening the capabilities of its four AI agents that reached general availability in October 2025. Governance is the newest addition to that suite. It extends the Quality Evaluation Agent’s reach from reviewing past interactions to preventing compliance issues before they happen. You can review the full scope of changes in the Dynamics 365 CRM 2026 Release Wave 1 summary.
Who should use Dynamics 365 Customer Service governance
Governance is relevant to any organization using Dynamics 365 Customer Service at scale. However, it’s especially valuable for teams in regulated industries. Healthcare, legal, and financial services organizations often need to enforce strict rules around sensitive data, high-risk advice, and restricted terminology. Governance automates those checks so reps don’t have to remember every rule manually.
Beyond regulated industries, the feature also helps any team with brand standards or multi-region communication requirements. If your organization uses Copilot to draft customer emails, Governance adds an important safeguard.
Technical requirements before enabling governance
Before enabling Governance, administrators should confirm a few requirements are in place.
First, administrators need the CSR Manager role. Service reps need the Customer Service Representative role. Custom roles require additional permissions across several governance-related entities in Dataverse. Second, organizations must set up Microsoft Copilot credits through the pay-as-you-go model. Third, they must enable AI agents in the Power Platform Admin Center and provide consent for potential data movement across regions.
In other words, Governance is built on top of the existing Microsoft Copilot and agentic AI infrastructure. Organizations that haven’t yet enabled or budgeted for Copilot credits will need to do that first. For full setup instructions, visit the governance policy configuration guide on Microsoft Learn.
Next steps for Dynamics 365 Customer Service administrators
Governance fills a real gap for organizations scaling AI-assisted customer service. It automates compliance checks that were previously manual, inconsistent, or missing altogether. As a next step, administrators should confirm Copilot credit prerequisites are in place and identify the highest-priority policies to configure first. Starting in simulation mode before enabling full enforcement is the smart approach. If your organization needs help getting set up, working with an experienced Dynamics 365 Customer Service partner can help ensure policies are configured effectively from day one.
