How to Enable Microsoft 365 eSignature in Your Tenant

The switch is the easy part.

The work is everything around the switch: billing, external sharing, site scope, permissions, labels, support and the awkward question of which documents are actually allowed to be signed this way.

This guide is part of the Microsoft 365 eSignature guide. For the actual rollout, I would not start in the admin center. I would start with the tenant readiness checklist and the licensing and limitations overview.

1. Check whether your tenant can use it

Microsoft 365 eSignature is available in the Microsoft 365 public cloud worldwide, with Indonesia excluded in Microsoft’s current documentation. In multi-geo tenants, Microsoft says the service is available in the home geo only.

That matters if your organization has strict data residency expectations. Do not assume a multi-geo tenant means every geo behaves the same way for this feature.

2. Confirm the legal fit

Microsoft describes the service as using simple electronic signatures.

For everyday internal approvals, forms or low-risk business documents, that may be fine. For regulated contracts, high-value agreements or scenarios where signer identity assurance is critical, legal needs to decide whether this is sufficient.

Do this before users fall in love with the button.

3. Use the right admin role

Microsoft says a SharePoint Administrator or Global Administrator can set up eSignature in the Microsoft 365 admin center.

Use SharePoint Administrator where possible. Global Administrator should be the exception, not the daily operating model.

4. Set up pay-as-you-go billing

Microsoft 365 eSignature uses pay-as-you-go billing through a linked Azure subscription. Microsoft’s pricing page currently lists eSignature at USD $2.00 per electronic signature request, with up to 10 recipients included in one request.

The price is easy to understand. The ownership is where tenants get sloppy.

Before rollout, decide who owns the Azure cost, who reviews usage and what volume would trigger a review.

5. Enable eSignature in the Microsoft 365 admin center

Microsoft’s setup path is:

1. Open the Microsoft 365 admin center.
2. Go to Settings > Org settings.
3. Open Pay-as-you-go services.
4. Select the Settings tab.
5. Under Document & image services, select eSignature.
6. Enable Let people in your organization use eSignature.

Microsoft notes that background processes run after activation and the service can take up to 24 hours to become fully operational.

6. Decide what to do with external signers

External signing is where the rollout stops being a simple feature setup.

If external recipients are not already guests, Microsoft says you need Microsoft Entra B2B integration for SharePoint and OneDrive plus guest sharing. That affects security, compliance and support.

Decide this in writing:

• Are new external guests allowed, or only existing guests?
• Are some domains blocked or allowed?
• Can every enabled site send externally?
• Who supports an external signer who cannot access the request?
• Which conditional access policies apply?

7. Start with controlled SharePoint sites

Do not enable every site just because you can.

Start with a pilot: a few sites, clear owners, simple documents and users who will give useful feedback. Good candidates are HR forms, procurement documents, policy acknowledgements or internal approvals where simple electronic signatures are enough.

Avoid ownerless sites, sensitive libraries and chaotic permission structures. They will make troubleshooting miserable.

The governance side is covered in SharePoint eSignature setup and governance.

8. Test before announcing it

At minimum, test:

• an internal signer;
• an existing external guest;
• a new external recipient, if allowed;
• an unencrypted PDF under 10 MB;
• a Word .docx from an enabled site;
• ordered recipients;
• request cancellation;
• completed signed PDF storage;
• Purview audit events;
• Teams Approvals tracking.

Also test what happens when things are wrong: encrypted files, restricted sharing, missing permissions and conditional access friction.

9. Prepare support

The first tickets will sound like feature issues, but many will be SharePoint issues:

• the button is missing;
• the sender cannot share the document;
• the external signer cannot access it;
• a label or encryption blocks the flow;
• the signed document cannot be saved where expected.

Give the service desk the troubleshooting guide before broad rollout.

Bottom line

Enabling Microsoft 365 eSignature is a short admin center task. Rolling it out properly is a governance project.

Start small. Watch the cost. Test external access. Make the rules boring and clear. Boring is good here.