SharePoint Premium, the product formerly called Microsoft Syntex, has no sticker price: it is billed pay-as-you-go through an Azure subscription, at published Microsoft meters of $0.005 per page for unstructured document processing, $0.01 per page for prebuilt models, $0.05 per page for structured and freeform processing, $2.00 per eSignature request, and $15.00 per million characters for document translation. Your budget is therefore your document volume multiplied by the meters you switch on, plus the configuration work to point the right models at the right libraries, and the volume math gets expensive quietly because processing runs on every upload, every update, and once per model applied.
This guide lays out every published meter, shows how to turn them into a budget, and names the usage patterns that make SharePoint Premium either a rounding error or a five-figure monthly surprise. It is written for the IT or information-management lead sizing the service for an enterprise tenant, the same estates our SharePoint development services practice works in daily.
What Do the SharePoint Premium Meters Cost?
Microsoft publishes the full meter list on its pay-as-you-go pricing page, billed in USD through the Azure subscription you connect. The document processing meters as of July 2026:
| Service | Unit | Published price (USD) |
|---|---|---|
| Unstructured document processing | Per page, sheet, slide, or file | $0.005 |
| Prebuilt document processing | Per page | $0.01 |
| Structured and freeform document processing | Per page | $0.05 |
| Autofill columns | Per page, sheet, slide, or file | $0.005 |
| Optical character recognition | Per page or embedded image | $0.001 |
| Image tagging | Per image | $0.001 |
| Taxonomy tagging | Per document | $0.05 |
| Content assembly | Per generated document | $0.15 |
| Document translation | Per million characters | $15.00 |
| eSignature | Per request, up to 10 recipients | $2.00 |
The storage-side services bill the same way: Microsoft 365 Archive at $0.05 per GB per month, Microsoft 365 Backup at $0.15 per GB per month, and SharePoint storage beyond your tenant quota at $0.20 per GB per month. These are separate meters with separate business cases, but they land on the same Azure invoice, so budget them together.
How Do You Turn Meters Into a Budget?
Three inputs decide the number: monthly document volume into the libraries where models are enabled, average pages per document, and which meter class each model uses. The arithmetic is straightforward and worth doing before enabling anything. A contracts library receiving 5,000 ten-page documents a month through an unstructured model processes 50,000 pages, which is $250 a month at the published rate. Put the same volume through a structured model at $0.05 and it is $2,500 a month. Run both models on the same library and you pay both, because processing is counted once per model applied.
Microsoft provides a SharePoint cost calculator for exactly this modeling, and it is worth an hour with your actual library statistics before any meter goes live. The estimates that go wrong are almost never wrong about price; they are wrong about volume, usually because nobody counted document updates.
If you would rather have that model built against your actual library statistics than a template, Talk to a senior SharePoint architect before the first meter goes live.
What Drives SharePoint Premium Cost at Enterprise Scale?
Four behaviors in the billing model do most of the damage in badly scoped deployments:
- Processing repeats on every update. A document edited five times is processed five times, wherever the meter counts processing on upload and update. Libraries with heavy co-authoring multiply their own volume.
- Every model applied bills separately. Two models on one library doubles the page count. Model sprawl, where teams enable overlapping extractors on the same content, is the most common silent cost multiplier we see.
- Library-level enablement is the cost switch. Tagging services bill only where enabled on a library, so enabling broadly “to see what happens” converts the whole tenant’s document flow into billable transactions.
- High-value meters deserve high-value targets. At $0.05 per page, structured processing pays for itself on invoices and contracts where extracted fields feed a downstream process. Pointed at general document storage, it is an expensive way to fill metadata columns nobody queries.
The pattern behind all four: SharePoint Premium is cheap per transaction and unbounded per month. Governance, deciding which libraries, which models, and which volumes, is the actual cost control, which makes it an information-architecture exercise, not a licensing one. Content that is being migrated into SharePoint Online is a special case worth planning deliberately, since a bulk migration through a model-enabled library can process an entire archive in one billable wave; if a platform move is in your future, plan model enablement after the migration, not before, and see our SharePoint migration tool guide for that sequencing and our SharePoint migration cost guide for the full project budget.
When Is SharePoint Premium Worth the Money?
The service earns its meters where a document’s content has to become structured data that something downstream consumes: contract metadata feeding a review workflow, invoice fields feeding an approval process, compliance attributes driving retention. It also earns them where OCR at $0.001 per page makes a scanned archive searchable for a fraction of any manual alternative. It does not earn them where the output is metadata for its own sake. The discipline is to attach each enabled model to a named business process with an owner, which is the same discipline that makes any automation investment defensible.
The transactional meters deserve the same named-process discipline. At $2.00 per request, eSignature competes on price with standalone signature platforms only when the signing volume and the documents already live in SharePoint; at $15.00 per million characters, document translation is inexpensive for policy libraries serving multilingual workforces and expensive as an always-on default. Each meter is a small product with its own business case, and treating the suite as one switch is how organizations end up paying for four services to get value from one.
How i3solutions Approaches SharePoint Premium Deployment
i3solutions has been a Microsoft partner since 1997. All i3solutions SharePoint developers, architects, and consultants are 100% U.S.-based. We treat SharePoint Premium as an information-architecture project with a metered bill attached: inventory the libraries, identify the document classes where extraction feeds a real process, model the volumes against the published meters, then enable narrowly and measure. Enterprise SharePoint strategy assessment engagements typically run four to six weeks elapsed time with two to three i3solutions consultants. A SharePoint Premium scoping fits naturally inside that assessment frame, arriving with the volume model, the shortlist of libraries and models, and the monthly meter estimate already attached, so the enablement decision is made on evidence rather than enthusiasm. Organizations that need delivery capacity rather than strategy can hire SharePoint developers from us directly, and our Microsoft 365 consulting services page covers the broader practice.
If you want the volume math done against your actual libraries before you switch anything on, Talk to a senior SharePoint architect.
Frequently Asked Questions
How much does SharePoint Premium document processing cost per page?
Unstructured document processing is $0.005 per page, prebuilt models are $0.01 per page, and structured or freeform processing is $0.05 per page on Microsoft’s published pay-as-you-go meters. The per-page price is only half the estimate; the other half is that processing counts on upload and on update, once for each model applied to the library.
Is there a per-user license for SharePoint Premium?
The current model is pay-as-you-go: you connect an Azure subscription for billing and pay published meters on usage rather than licensing seats. That inverts the usual Microsoft 365 budgeting exercise, because cost follows document volume and model enablement, not headcount, and it is why volume modeling matters more than license counting. The seat-based side of the Microsoft 365 budget is its own decision, priced in our Microsoft 365 E3 vs E5 cost guide.
What do Microsoft 365 Archive and Backup cost?
On the same published meter list, Microsoft 365 Archive is $0.05 per GB per month, Microsoft 365 Backup is $0.15 per GB per month, and SharePoint storage beyond the tenant quota bills at $0.20 per GB per month. Archive in particular pairs well with large migrations, since cold content can be archived rather than carried in active storage.
How do we estimate a SharePoint Premium budget before enabling it?
Count three things per target library: documents arriving per month, average pages per document, and expected updates per document, then multiply against the meter for each model you plan to apply. Microsoft’s SharePoint cost calculator supports the modeling, and a pilot on one library with real volume for a month is the cheapest accuracy upgrade available before broad enablement.
What makes SharePoint Premium costs spike unexpectedly?
Almost always one of three things: models enabled on broad libraries instead of targeted ones, multiple overlapping models applied to the same content so every page bills more than once, or high-churn libraries where frequent edits reprocess the same documents repeatedly. All three are governance decisions, which is why the cost conversation is really an information-architecture conversation.
How does i3solutions scope a SharePoint Premium engagement?
We start from the business processes that would consume extracted data, not from the feature list: which document classes, which fields, feeding which workflow or system. That inventory produces a short list of libraries and models with volume estimates against the published meters, so the enablement decision arrives with its monthly cost attached and an owner for each model.
