Microsoft 365 eSignature Licensing, Pricing and Limitations

Microsoft 365 eSignature is not licensed like a normal per-user Microsoft 365 add-on. It uses pay-as-you-go billing through Azure.

That can be great for occasional signing. It can also be a nasty surprise if every department starts sending low-value signature requests because the button is convenient.

This article is part of the Microsoft 365 eSignature guide. For setup steps, read How to enable Microsoft 365 eSignature in your tenant. For vendor selection, use the comparison table.

How billing works

Microsoft lists eSignature under Microsoft 365 document processing pay-as-you-go services. Before users can send requests, you need a linked Azure subscription.

That means usage becomes consumption. Someone has to own the bill. Someone has to review the volume. If nobody does, the feature will still work, but finance may discover it later in the least pleasant way.

Current Microsoft-listed price

Microsoft’s pay-as-you-go pricing page currently lists eSignature like this:

• Meter: electronic signature requests created
• Included recipients: up to 10 recipients per request
• Price: USD $2.00 per request

Check Microsoft’s pricing page before you quote this internally. Pricing pages change, and procurement will not care that an old blog post looked confident.

Trial note

Microsoft’s overview currently says that through June 2026, tenants with pay-as-you-go billing set up can try a limited amount of eSignature by sending up to five requests at no cost.

That is enough to test the flow. It is not enough to prove your operating model.

Quick cost examples

Because the meter is request-based, the rough math is simple:

• 50 requests/month: about USD $100/month
• 250 requests/month: about USD $500/month
• 1,000 requests/month: about USD $2,000/month

The useful question is bigger than “what will this cost?” Ask which signing requests are worth formalizing in the first place.

If teams start using paid signature requests for things that should be simple approvals, the governance model is wrong.

Limits that matter

Based on Microsoft Learn, these are the limits I would put in front of admins before a pilot:

• Microsoft 365 public cloud availability, excluding Indonesia.
• Multi-geo tenants: home geo only.
• Simple electronic signatures, so legal fit must be checked.
• Unencrypted PDFs only.
• Microsoft troubleshooting guidance references PDFs under 10 MB for request creation.
• Up to 10 recipients per request.
• Up to 50 fields total in a PDF request.
• At least one required signature field per recipient.
• Word signing requires subscription Word desktop, .docx, an unencrypted file, an enabled SharePoint site and a supported update channel.
• New requests cannot be started from documents that were previously signed.

None of these are shocking. They are just the kind of details users only notice when a real document fails five minutes before a deadline.

The hidden costs

The bill is only one part of the cost.

You also need time for:

• external sharing decisions;
• guest access and conditional access testing;
• site owner training;
• sensitivity label testing;
• retention decisions for signed PDFs;
• audit review;
• service desk documentation.

This is why I would not treat eSignature as “free because we already have Microsoft 365”. You may not buy a separate license, but you still pay in operations.

When the model works well

Pay-as-you-go works well when signing volume is moderate, sporadic or limited to a few departments. It is also useful when you do not want to buy named licenses for people who only send a few requests per year.

If signing is a core business process with high volume, templates, routing or contract operations behind it, compare the total picture against Adobe Acrobat Sign or DocuSign. The Microsoft 365 eSignature vs Adobe Sign vs DocuSign article covers that decision.

Bottom line

The pricing is simple: pay per request.

The decision is not simple. You need to decide which documents deserve a paid signing request, which teams can send them and when a dedicated signing platform is the better tool.