Skip to main content
🦉
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderM365 ReportPortfolio
🦉
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderM365 ReportPortfolio

Connect

© 2026 M365 Message Center. Created with ❤ by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center • Not affiliated with Microsoft

  1. Home
  2. /
  3. MC1290821

eSignature for Microsoft 365 - Recipient groups

Informational

Message ID

MC1290821
View in Admin Center

Roadmap ID

560822
View in Roadmap

Services

Microsoft 365 suite
SharePoint Online

Affected Platforms

Desktop

Summary

Microsoft 365 eSignature introduces recipient groups, allowing up to 10 people per recipient slot where the first signer fulfills the requirement. This reduces delays in signature workflows, is enabled by default, respects tenant policies, and will roll out worldwide from late June to late July 2026.

Details

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 late June 2026 and is expected to complete by late July 2026.

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.

Timeline

Published
Apr 24, 2026
Message published to Message Center
Updated
Apr 24, 2026
Message content updated
End Date
Aug 31, 2026
Message timeline ends

Tags

#New feature#User impact#Admin impact

Category

Stay Informed

Related Messages

Similar updates

MC1289720

Microsoft 365 Apps: Cloud Update adds update health reporting

Apr 23, 2026
MC1287368

Team site homepages will automatically collapse inactive News web parts

Apr 21, 2026
MC1282683

Create and edit SharePoint pages with Copilot-powered AI

Apr 16, 2026
MC1279072

Microsoft 365 Copilot Chat: Use prepaid Copilot Credits without Pay‑As‑You‑Go billing

Apr 13, 2026
MC1279068

Microsoft Purview | Information Protection: Sensitivity label inheritance for Teams meeting artifacts

Apr 13, 2026