MC1290821 - eSignature for Microsoft 365 - Recipient groups

Message Center

Summary

Microsoft 365 eSignature will introduce recipient groups, allowing up to 10 people per recipient slot, with the first signer fulfilling the requirement. This reduces delays in signing workflows. Rollout begins early September 2026, completes by end of September, enabled by default, with no admin action needed.

Last Updated

Jun 12, 2026

Published Apr 24, 2026

View version history

Service

Microsoft 365 suite
SharePoint Online

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Desktop

More information

Updated June 12, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

We are introducing recipient groups for eSignature in Microsoft 365. Recipient groups allow a single recipient slot to be assigned to multiple people, where the first person to sign fulfills the signing requirement. This update helps make signature workflows more reliable by reducing delays when a specific signer is unavailable, without changing existing tenant policies.

This message is associated with Microsoft 365 Roadmap ID 560822.

When this will happen

General Availability (Worldwide): Rollout will begin in early September 2026 (previously late June) and is expected to complete by end of September 2026 (previously late July).

How this affects your organization

Who is affected

  • Users who create eSignature requests in Microsoft Word
  • Microsoft 365 tenants that use eSignature for Microsoft 365

What will happen

  • Users can assign up to 10 people to a single recipient slot: 

    user settings

  • The first person in the recipient group to sign fulfills the signing requirement for the group.
  • Signature workflows are less likely to stall due to individual signer availability.
  • The feature is enabled by default and respects existing tenant policies.

What you can do to prepare

  • No action is required from admins.
  • Consider informing users who rely on eSignature workflows about this improvement.

Compliance considerations

QuestionAnswer
Does the change alter how existing customer data is processed or accessed?Yes. Signature completion logic is updated so that one signer in a recipient group can fulfill the signing requirement for the group.

Version history

2 versions tracked

Updated 1 time since Apr 24, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Jun 12, 2026 · 04:16 PMLatest · v2

    Changed: Body, Tags, End date

  2. Apr 24, 2026 · 09:43 PMOriginal · v1

    Changed: Initial version