{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigylugbu7y3fg6msb3jox5f52bugvxt4y6ecb5fo5bmpexxs7ukvm",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mkbqdemedoa2"
  },
  "description": "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 2...",
  "path": "/m365-message-center/message/mc1290821/",
  "publishedAt": "2026-04-25T00:00:05.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "560822"
  ],
  "textContent": "**[Introduction]**\n\nWe 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.\n\nThis message is associated with **Microsoft 365 Roadmap ID** 560822.\n\n**[When this will happen]**\n\n**General Availability (Worldwide):** Rollout will begin in**late June 2026** and is expected to complete by**late July 2026**.\n\n**[How this affects your organization]**\n\n_Who is affected_\n\n  * Users who create eSignature requests in _Microsoft Word_\n  * Microsoft 365 tenants that use**eSignature for Microsoft 365**\n\n\n\n _What will happen_\n\n  * The **first person** in the _recipient group_ to sign fulfills the signing requirement for the group.\n  * Signature workflows are less likely to stall due to individual signer availability.\n  * The feature is **enabled by default** and respects existing tenant policies.\n\n\n\nUsers can assign**up to 10 people** to a single recipient slot:\n\n**[What you can do to prepare]**\n\n  * No action is required from admins.\n  * Consider informing users who rely on eSignature workflows about this improvement.\n\n\n\n**[Compliance considerations]**\n\n**Question**| **Answer**\n---|---\nDoes 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.",
  "title": "MC1290821: eSignature for Microsoft 365 - Recipient groups",
  "updatedAt": "2026-04-25T00:00:05.641Z"
}