Category
planForChange
Severity
normal
Major change
True
Last modified
2026-05-20 16:13:12
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
—
Action by (AI)
2026-05-15 00:00:00
Services
Microsoft Purview
Tags
Updated message, Feature update, User impact
Master tags
User, Admin, Security
Roadmap IDs
One-line summary
eDiscovery will block +, =, @, /, and * in case, hold, search, and review set names and descriptions starting mid-June 2026; existing records remain unaffected unless edited.
Similar updates
More like thisMC1162273 Microsoft Purview | eDiscovery - Metadata field enhancements in process reporting
Microsoft Purview | eDiscovery - Metadata field enhancements in process reporting Microsoft Purview eDiscovery will enhance item.csv metadata reporting with new fields for improved traceability and automation, starting rollout in October 2025. [Introduction:] To improve transparency and streamline post-export workflows, Microsoft Purview.
MC1181768 Microsoft Purview: eDiscovery admin content access restrictions when not in compliance with Entra policies
Microsoft Purview: eDiscovery admin content access restrictions when not in compliance with Entra policies Microsoft Purview will enhance audit logging and enforce Entra conditional access for eDiscovery admins; non-compliant admins will be blocked from SharePoint content in Purview. To strengthen Microsoft’s security posture, we’re introducing .
MC1148532 Microsoft Purview |eDiscovery - Graph APIs for Standard eDiscovery
Microsoft Purview |eDiscovery - Graph APIs for Standard eDiscovery Microsoft Graph APIs for Standard eDiscovery license tenants enable automated case, search, hold, and export management; public preview starts September 2025, GA in November 2025. Introduction We’re introducing Microsoft Graph APIs for tenants with Standard eDiscovery licenses ,.
MC1162966 Microsoft Purview | Information Protection: Updates to Microsoft built-in Sensitive Information Types (SITs)
Microsoft Purview | Information Protection: Updates to Microsoft built-in Sensitive Information Types (SITs) Microsoft is updating five bundled EU Sensitive Information Types in Purview to improve detection accuracy; rollout completes by mid-October 2025 with no admin action required. [Introduction] To improve detection accuracy across EU.
MC1189685 Power Platform - Improved security for column-level audit events in Microsoft Purview
Power Platform - Improved security for column-level audit events in Microsoft Purview Audit events for columns with security restrictions in Microsoft Purview will filter before-and-after values in logs starting December 1, 2025, enhancing sensitive data protection. We are announcing enhancements to the handling of audit events that capture,.
MC1199763 Microsoft Purview | Data Security Investigations – Introducing new purge mitigation action
Microsoft Purview | Data Security Investigations – Introducing new purge mitigation action Microsoft Purview Data Security Investigations adds a purge action for admins to quickly delete sensitive or overshared content during investigations, available by default and respecting existing policies. [Introduction] We’re introducing a new purge.
Details
Summary
Starting mid-June 2026, Microsoft Purview eDiscovery will restrict special characters (+, =, @, /, *) in naming and description fields for new or edited cases, holds, searches, and review sets. Existing entities remain unaffected. No admin action is required, but users should update naming practices accordingly.
Body (from Message Center)
Updated May 20, 2026: We have updated the timeline. Thank you for your patience.
[Introduction]
We’re making a change to the characters allowed in naming and description fields across Microsoft Purview eDiscovery. As part of ongoing security hardening efforts, this update strengthens input validation for eDiscovery cases, holds, searches, and review sets to improve service resilience and reliability.
[When this will happen:]
General Availability (Production, GCC, GCC High, DoD): This change will begin rolling out in mid-June 2026 (previously mid-May) and is expected to be completed by end of June 2026 (previously late May).
[How this affects your organization:]
Who is affected:
Organizations with users or administrators who create or manage Microsoft Purview eDiscovery:
- Cases
- Holds
- Searches
- Review sets
What will happen:
- Beginning May 15th, 2026, the following special characters will no longer be permitted in naming or description fields when creating or editing:
- + (plus sign)
- = (equals sign)
- @ (at sign)
- / (forward slash)
- * (asterisk)
- This restriction applies to:
- Case name and description
- Hold policy name and description
- Search name and description
- Review set name and description
- Existing entities are not affected.
- Cases, holds, searches, and review sets that already contain these characters will continue to function normally.
- Editing triggers enforcement:
- If a user edits an existing entity's name or description (e.g., updating an eDiscovery case name) that contains a restricted character, they will see a validation message prompting them to remove the special character before saving. Note that this does not apply when an existing hold policy is being reapplied or when data sources are added to or removed from hold policies.
- The original name and description are preserved until the user chooses to make changes.
- New entities are enforced immediately:
- Any newly created case, hold, search, or review set must not contain restricted characters in name or description fields.
[What you can do to prepare:]
No admin action is required to enable this change. However, we recommend the following:
- Inform your eDiscovery users that the characters + = @ / and * will no longer be accepted in entity names and descriptions.
- Review and update existing naming conventions or templates that include these characters.
- Update internal documentation or guidance for eDiscovery naming standards.
- Communicate this change to helpdesk and compliance teams to prepare for validation messages when editing existing entities.
Learn about eDiscovery (Premium) | Microsoft Learn
No data loss will occur. Existing entities retain their current names and continue to function. Enforcement applies only at the time of creation or editing.
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization.
Raw JSON (for debugging)
Expand/collapse the full payload below.
Show/hide raw
{
"snapshot_item": {
"action_required_by": null,
"ai_action_required_by": "2026-05-15T00:00:00Z",
"ai_actions": [
"Notify eDiscovery users of new character restrictions",
"Update naming conventions and documentation",
"Prepare helpdesk/compliance teams for edit validation messages"
],
"ai_master_tags": [
"User",
"Admin",
"Security"
],
"ai_model": "gpt-4.1",
"ai_summary": "eDiscovery will block +, =, @, /, and * in case, hold, search, and review set names and descriptions starting mid-June 2026; existing records remain unaffected unless edited.",
"ai_topics": [
"Purview"
],
"category": "planForChange",
"details_map": {
"Summary": "Starting mid-June 2026, Microsoft Purview eDiscovery will restrict special characters (+, =, @, /, *) in naming and description fields for new or edited cases, holds, searches, and review sets. Existing entities remain unaffected. No admin action is required, but users should update naming practices accordingly."
},
"id": "MC1282562",
"importance": 5,
"is_major_change": true,
"last_modified": "2026-05-20T16:13:12Z",
"ms_products": [
"Purview"
],
"platforms": null,
"roadmap_ids": [],
"services": [
"Microsoft Purview"
],
"severity": "normal",
"tags": [
"Updated message",
"Feature update",
"User impact"
],
"title": "(Updated) Microsoft Purview eDiscovery: Naming and description fields will restrict certain special characters"
}
}