(Updated) eSignature for Microsoft 365 - Recipient groups
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Rollout
- Ends
- 18 Jan 2027
- Roadmap
- 560822
- Platforms
- Desktop
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
- Microsoft's start date
- 24 Apr 2026
- Last changed by Microsoft
- 21 Sep 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedUpdated 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
| 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. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.