MC1152319 – M365 Change Digest

One-line summary

Word eSignature requests will support free text fields, letting users collect custom signer info; feature is on by default for tenants with eSignature enabled.

Similar updates

Details

RoadmapIds

499024

Summary

Microsoft Word's eSignature feature will support free text fields starting October 2025, allowing users to collect custom signer information. This feature is on by default for tenants with eSignature enabled, requires no admin changes, and has no impact unless eSignature is active.

Platforms

Desktop

Body (from Message Center)

[Introduction:]

We're adding support for free text fields in eSignature requests within Word. This enhancement allows users to collect custom information—such as job title, phone number, address, or full name—from signers, improving flexibility and alignment with real-world document workflows.

This update is associated with Microsoft 365 Roadmap ID 499024.

[When this will happen:]

General availability (Worldwide): We will begin rolling out in early October 2025 and expect to complete by early January 2026.

[How this affects your organization:]

Who is affected: Users and admins in tenants with eSignature enabled in Microsoft Word.

What will happen:

Users will be able to insert free text fields into eSignature requests in Word documents.
These fields can be used to collect custom information from signers.
The feature will be ON by default for tenants with eSignature enabled.
No changes to existing admin policies are required.
There is no impact to end-user workflow unless eSignature is enabled.

Screenshot 1 - Create a signature request:

user settings

Screenshot 2 - View of document with signature:

user settings

[What you can do to prepare:]

If eSignature is already enabled in your tenant, no action is required.
If not enabled, you can turn it on in the Microsoft 365 admin center.
To enable eSignature, follow the instructions at Overview of eSignature | Microsoft 365 | Microsoft Learn.
Consider notifying helpdesk staff and updating internal documentation to reflect this new capability.

[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": null,
    "ai_actions": [
      "Enable eSignature if desired",
      "Notify helpdesk staff",
      "Update internal documentation"
    ],
    "ai_master_tags": [],
    "ai_model": "gpt-4.1",
    "ai_summary": "Word eSignature requests will support free text fields, letting users collect custom signer info; feature is on by default for tenants with eSignature enabled.",
    "ai_topics": [
      "Microsoft 365",
      "Microsoft 365 Apps",
      "Word"
    ],
    "category": "stayInformed",
    "details_map": {
      "Platforms": "Desktop",
      "RoadmapIds": "499024",
      "Summary": "Microsoft Word\u0027s eSignature feature will support free text fields starting October 2025, allowing users to collect custom signer information. This feature is on by default for tenants with eSignature enabled, requires no admin changes, and has no impact unless eSignature is active."
    },
    "id": "MC1152319",
    "importance": 1,
    "is_major_change": false,
    "last_modified": "2025-09-12T23:06:34Z",
    "ms_products": [
      "Microsoft 365",
      "Microsoft 365 Apps"
    ],
    "platforms": "Desktop",
    "roadmap_ids": [
      "499024"
    ],
    "services": [
      "Microsoft 365 suite",
      "Microsoft 365 apps"
    ],
    "severity": "normal",
    "tags": [
      "New feature",
      "User impact",
      "Admin impact"
    ],
    "title": "eSignature: Free text field support in Word"
  }
}