Title
Allow Organization-Wide Default Font Settings for Rich Text Editor in Dynamics 365 / CRM
Description
In Dynamics 365 and Dynamics CRM (including on-premises environments), organizations currently have no supported way to configure a default font for the Rich Text Editor, particularly for email bodies and other rich text fields.
This results in inconsistent formatting across users, emails, templates, and records. The default font (typically Segoe UI) is automatically applied by the editor, overriding organizational formatting standards.
Organizations — especially government, archival, legal, and customer-service organizations — often require:
- Consistent email formatting
- Archival-friendly fonts (e.g., Verdana, Arial)
- Accessibility-compliant fonts
- Corporate branding standards
- Uniform communication across users
Currently, administrators must rely on unsupported or fragile workarounds such as:
- JavaScript form manipulation
- Signature formatting
- Email template enforcement
- DOM manipulation after load
- Custom plugins
These approaches are:
- Difficult to maintain
- Inconsistent across UI updates
- Unsupported by Microsoft
- Error-prone across environments
Requested Feature
Provide an Organization-Wide Default Font Setting for the Rich Text Editor that allows administrators to configure:
- Default font family (e.g., Verdana, Arial, Segoe UI)
- Default font size (e.g., 10pt, 11pt)
- Default font color (optional)
- Default line spacing (optional)
This setting should apply to:
- Email body (Email entity)
- Rich text memo fields
- Templates
- Signatures
- Knowledge articles
- Timeline rich text inputs
Additional Desired Scope
Ideally, administrators should be able to configure:
- Organization-wide default
- Entity-specific default (Email, Case, Knowledge Article, etc.)
- Field-specific default (optional advanced feature)
Business Impact
This feature would:
- Improve consistency across communications
- Reduce unsupported customizations
- Improve accessibility compliance
- Improve archival readability
- Reduce administrative overhead
- Improve professional presentation of customer communications
Current Impact Without This Feature
Without this functionality:
- Users send emails in mixed fonts
- Templates become inconsistent
- Organizations implement unsupported scripting
- UI updates break formatting logic
- Increased support and maintenance overhead
Environments Affected
- Dynamics 365 Online
- Dynamics CRM On-Premises
- Unified Interface
- Customer Service environments
- Government and archival organizations
Comments
Further research learns that you HAVE implemented personal and org wide setting of this in D365. Please port this through to on prem.
Category: Email
Suggested Enhancement ScopeTo minimize implementation impact while maximizing flexibility, we propose:1. Organization-Wide Default Setting (Primary Requirement) Allow administrators to define a default font family and size for the Rich Text Editor across the organization. This ensures consistent formatting with minimal behavioral changes.2. Rich Text Editor Default Configuration (Optional / Advanced) Allow configuration of default font settings at the Rich Text Editor control level, enabling:Different defaults per entity (Email, Case, Knowledge Article)Different defaults per field (optional)Future extensibility without breaking existing behaviorThis approach minimizes impact while providing long-term flexibility and maintainability.
Category: Email
Main purpose: Enable organization-wide default house style to ensure consistent formatting, accessibility compliance, and professional communication across all emails and rich text fields.Need : reasonably high , we now have to select all communication in de edtior before sending, Go way down in the font pulldown (no first letter press support) and then select our size. Editor easily shifts back to Segoe UI 9 which is NOT our standard. Gives user the idea that de editor is working faulty
Category: Email