For Dynamics administrators, compliance teams, and anyone running AI-drafted customer email at scale, this is a real change in what governance actually covers. It also has limits worth knowing before you rely on it.
What Microsoft shipped, and when
Microsoft first announced the feature through Microsoft 365 Message Center item MC1396314. The item was published June 18, 2026, and said the ability to apply governance policies to email attachments in Dynamics 365 Customer Service will reach general availability on July 3, 2026. Microsoft's release-plan entry for the 2026 release wave 1 gives the same July 3 date and lists no public preview. It also says admins, makers, or analysts must turn the feature on for users. It does not switch itself on.
Microsoft then confirmed the wider rollout on the Dynamics 365 blog. It announced that Governance in Dynamics 365 Customer Service is now generally available, helping organizations enforce policies, reduce risk, and manage AI-generated emails. Attachment checks were the headline addition: Governance now extends beyond the email body to text-based attachments.
One housekeeping note: the Learn release-plan page for this feature says that, as of October 2026, it is archived and no longer maintained. Microsoft points readers to the AI at Work roadmap for current plans and to Microsoft Learn product documentation for authoritative guidance.
Section summary: Generally available since July 2026, worldwide commercial cloud, web only, and admins must enable it.
How attachment governance works
According to Microsoft's feature description, the checks run when a user sends an email:
- Every attachment is scanned. Each document is checked separately, and every applicable policy runs against every file. If an email carries five attachments, all five are checked.
- One bad file blocks the whole email. If any attachment breaks a configured policy, for example by containing restricted content or failing a compliance rule, the entire email is blocked from sending.
- Only plain text is analyzed for now. The first release looks at plain text in supported document types. Microsoft names Word and PDF as examples. Its GA blog says the process evaluates PDFs, Word documents, and text files for policy compliance before they reach customers.
- Images and embedded content are skipped. Microsoft says it excluded non-text elements in this phase to keep processing predictable and efficient.
- Admins choose which policies check attachments. Attachment checks are a per-policy option. You can update existing policies to add attachment analysis, and set new policies to include it by default.
- Results are logged and explained. Each attachment evaluation is logged, including which file caused a violation and why. The person sending sees feedback explaining the block, so they can fix the problem and resend.
The image exclusion matters more than it might seem. A scanned contract saved as a PDF, a screenshot of a spreadsheet, or a chart pasted into a Word file may contain exactly the sensitive data you care about, and this release won't read it. Treat the feature as a text-layer check, not a full inspection of everything in a document.
Microsoft's documentation also doesn't list every supported file type, any size limits for scanning, or how text is pulled out of files. Don't assume anything beyond the formats Microsoft names.
Section summary: Text in Word, PDF, and text files gets checked one file at a time. Any single failure blocks the send. Images and embedded objects go unchecked.
Where this sits in the broader governance system
Attachment checks extend an existing governance framework. Microsoft Learn describes that framework as checking outbound messages, both those written by service representatives and those generated by AI agents, against configurable policies on the email channel. Depending on your settings, a detected violation can trigger a warning or a block, be logged for review, or be routed for manual approval. Admins can review detection logs, spot repeated risk patterns, and adjust policy descriptions to tune the underlying prompts.
The GA announcement adds two controls. First, strictness: Organizations can configure Low, Medium, High, or Very High strictness levels to enforce policies with the right balance of sensitivity, accuracy, and business risk for each scenario. Second, testing: Microsoft says simulation and reporting tools help validate and optimize policies before rolling them out broadly. The trade publication CX Magazine explained the enforcement modes this way: flagged emails get held for human review; blocked ones go nowhere until someone steps in.
One detail is unclear in Microsoft's own wording. The release-plan entry says one violating attachment blocks the entire email. The GA blog, meanwhile, describes admins choosing enforcement behaviors (flag or block) alongside attachment checks. The documentation doesn't say whether every enforcement option behaves the same way when the violation is in an attachment. Test this in a sandbox before you write user-facing guidance.
Section summary: Attachment scanning plugs into the same governance engine that checks message bodies, with strictness levels and simulation tools for tuning.
Setting it up: prerequisites and enablement
Microsoft Learn documents how to enable governance itself. It does not describe a separate attachment toggle, because attachment checks are set inside individual policies. Here is the documented groundwork.
Prerequisites
- Roles: Administrators need the CSR Manager security role. Representatives need the Customer Service Representative role.
- Custom roles for representatives: Grant Read at Global access level on
msdyn_governanceagent_status. - Custom roles for administrators: Grant Read, Create, Write, Delete, Append, Appendto, and Assign at Global access level on these tables:
msdyn_governanceagent_statusmsdyn_guardrail_consumer_mappingmsdyn_guardrail_execution_infomsdyn_guardrail_rulemsdyn_guardrail_rule_versionmsdyn_guardrail_scenariotype
- Copilot credits: Set up Microsoft Copilot credits.
- Data residency consent: Consent to potential data movement across regions.
- AI agents: Enable AI agents for your Dynamics 365 environment in the Power Platform admin center.
Turning governance on
- In the Copilot Service admin center site map, go to Customer Support and select Quality management.
- On the Quality management page, select Manage for Governance.
- On the Governance page, turn on the governance toggle.
Adding attachment checks to policies
Once governance is on, edit an existing policy or create a new one and include attachment checks during setup. Microsoft documents this as a per-policy option but doesn't publish the exact field label in the sources reviewed here, so check the label in your own tenant. Then use the simulation tools to test the policy before enforcing it.
How you know it's working: Send a test email with an attachment that deliberately contains text your policy prohibits. The send should be blocked, the sender should see feedback naming the problem, and the governance log should record which attachment failed and why.
Common snags
- Governance toggle missing or greyed out: Check that AI agents are enabled in the Power Platform admin center, that Copilot credits are set up, and that cross-region data movement consent has been given.
- Admins can't save policies: If they use custom roles, check the full set of Global-level permissions on all six governance tables listed above.
- A violating file got through: Check that the policy actually has attachment checks enabled, and whether the offending content was an image or embedded object, which this release doesn't analyze.
Don't confuse this with attachment blocking
Dynamics 365 Customer Service already offered attachment controls, and they do a different job. According to Microsoft's email configuration documentation, administrators can set file-size limits and blocked file types. The default file size limit for attachments is 5 MB. The size limit for attachments can be increased to a maximum of 132 MB per file.
Those settings decide whether a file can be attached at all. Governance decides whether the text inside an allowed file breaks policy. A blocked-extensions list won't catch a perfectly ordinary .docx containing a customer's account details, and governance won't stop someone uploading a 200 MB video. Use both.
| Control | What it checks | Outcome |
|---|---|---|
| Blocked file extensions | File type | Upload refused with an error |
| Attachment size limit | File size | Upload limited (default 5 MB, max 132 MB) |
| Attachment governance | Plain text inside supported documents | Send blocked or acted on per policy, with violation logged |
Analysis: a sensible fix, with some fine print
The case for the feature is easy to make. As more support email gets drafted by AI agents, attachments become an obvious blind spot. Checking the body perfectly means little if the attached quote or policy document goes out unchecked. CX Magazine gave a fair example: a financial services firm sending renewal emails could catch the attachment that accidentally includes internal pricing.
The trade-offs are just as real, and Microsoft's release material doesn't quantify any of them. It gives no figures for scanning latency, false-positive rates, or detection accuracy, and it doesn't claim the feature will catch all sensitive content. Because one attachment can block a whole email, an overly strict policy could stall representatives who routinely send long customer-facing documents. That's why strictness levels and simulation are more than nice extras.
There's also a people side. Microsoft's governance documentation says customers are responsible for complying with laws on monitoring, recording, and storing communications. Where the law requires it, customers must notify users and get consent. Microsoft also encourages telling representatives that their communications may be monitored. And Microsoft says plainly that the feature is meant to help managers improve team performance and customer satisfaction, not to make decisions about pay, rewards, seniority, or other employee entitlements.
The practical advice: turn on attachment checks first for policies that protect truly sensitive content, run simulations against realistic documents, and be clear with users that scanned PDFs and images are not yet covered. This is an overdue extension of governance to where sensitive data often sits. It's a strong first release, but it doesn't inspect everything in a file.
References
- Dynamics 365 Customer Service: Workforce engagement management - Enforce governance policies on email attachments Microsoft 365 Roadmap · 2026-10-23T23:10:35.843898Z
- Enforce governance policies on email attachments | Microsoft Learn learn.microsoft.com
- Governance Now Available for Dynamics 365 Customer Service microsoft.com