(Updated) eSignature for Microsoft 365 - Recipient groups

Message ID

MC1290821

Services

Microsoft 365 suiteSharePoint Online

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.

Details

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

Question	Answer
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.

Change History

Show

Published: April 24, 2026

Last Updated: June 12, 2026

June 12, 2026 at 6:30 PM Updated

Title

eSignature for Microsoft 365 - Recipient groups

New

(Updated) eSignature for Microsoft 365 - Recipient groups

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.

New

Last Updated Date

2026-04-24T21:43:43.317Z

New

2026-06-12T16:16:53.807Z

Tags

New feature,User impact,Admin impact

New

Updated message,New feature,User impact,Admin impact

Body Content

[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 <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=560822" target="_blank">560822</a>.[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<ul><li>Users who create eSignature requests in Microsoft Word</li><li>Microsoft 365 tenants that use eSignature for Microsoft 365</li></ul>What will happen<ul><li>Users can assign up to 10 people to a single recipient slot: <img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/9a5a40a8-98d0-4e90-80d6-95854664eef2/f649439f3aad840115b7b48708ddf4f4b85eaaf9.png" style="width: 400px;" alt="user settings"> </li><li>The first person in the recipient group to sign fulfills the signing requirement for the group.</li><li>Signature workflows are less likely to stall due to individual signer availability.</li><li>The feature is enabled by default and respects existing tenant policies.</li></ul>[What you can do to prepare]<ul><li>No action is required from admins.</li><li>Consider informing users who rely on eSignature workflows about this improvement.</li></ul>[Compliance considerations]<table class="table table-bordered"><tbody><tr><td>Question</td><td>Answer</td></tr><tr><td>Does the change alter how existing customer data is processed or accessed?</td><td>Yes. Signature completion logic is updated so that one signer in a recipient group can fulfill the signing requirement for the group.</td></tr></tbody></table>

New

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 <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=560822" target="_blank">560822</a>.[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<ul><li>Users who create eSignature requests in Microsoft Word</li><li>Microsoft 365 tenants that use eSignature for Microsoft 365</li></ul>What will happen<ul><li>Users can assign up to 10 people to a single recipient slot: <img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/9a5a40a8-98d0-4e90-80d6-95854664eef2/f649439f3aad840115b7b48708ddf4f4b85eaaf9.png" style="width: 400px;" alt="user settings"> </li><li>The first person in the recipient group to sign fulfills the signing requirement for the group.</li><li>Signature workflows are less likely to stall due to individual signer availability.</li><li>The feature is enabled by default and respects existing tenant policies.</li></ul>[What you can do to prepare]<ul><li>No action is required from admins.</li><li>Consider informing users who rely on eSignature workflows about this improvement.</li></ul>[Compliance considerations]<table class="table table-bordered"><tbody><tr><td>Question</td><td>Answer</td></tr><tr><td>Does the change alter how existing customer data is processed or accessed?</td><td>Yes. Signature completion logic is updated so that one signer in a recipient group can fulfill the signing requirement for the group.</td></tr></tbody></table>

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.

Explore Dashboard Sign Up Free