Tenant announcements

(Updated) eSignature for Microsoft 365 - Recipient groups

MC1290821

All Microsoft 365 Message Center posts · Daily summary

About this page These posts come from a tenant in West Europe and are shown as a reference. Day-by-day digest: MC Summary. Linked to the roadmap via Roadmap ID when Microsoft names one. Items are kept for 12 months. Always check Message Center in your own environment for what applies to you.
Archive This post is no longer in the Microsoft 365 Message Center (last seen on 30 sep 2026). Microsoft removes posts after a while. We keep the last version here as an archive.
MC1290821
Show roadmap information (1)
#560822In development
SharePoint: eSignature for Microsoft 365 - Recipient groups
Rollout startDecember 2026

Added to roadmap: 22 apr 2026 | Last modified: 21 sep 2026

Recipient groups in eSignature allow a recipient slot to be assigned to multiple people, such that any one  of those people can fulfil the signing requirement on behalf of the group.

Updated September 21, 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

Public Preview: Rollout is expected to complete by late September 2026

General Availability (Worldwide): Rollout will begin in early December 2026 (previously early September) and is expected to complete by mid-December 2026 (previously late October).

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:
  • 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

QuestionAnswerDoes 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.