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.
If the Microsoft pages you are reading say “document processing” where this page says SharePoint Premium, the service is the same and only its name has changed. As of September 2026, Microsoft’s Overview of document processing for Microsoft 365 states: “The pay-as-you-go services previously offered under Microsoft Syntex are now referred to as document processing services. The features and functionality of these services remain unchanged.” The meters in the table below are the ones Microsoft publishes for those services.
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.
Whether the SharePoint licensing you already hold qualifies is answered in Microsoft’s own eligibility sentences. The older Microsoft Syntex service description, which still carries the previous name, states: “Users must have a valid Office 365, Microsoft 365, or SharePoint Online license to be eligible to use Microsoft Syntex.” The current Licensing for document processing for Microsoft 365 page states: “Any user in your tenant can use the services, provided they have a Microsoft 365 license.” Our reading of those two sentences, as of September 2026: SharePoint Online Plan 2 seats are a SharePoint Online license in the service description’s words, the SharePoint included in Microsoft 365 E3 or E5 is a Microsoft 365 license in the licensing page’s words, and either qualifies without a separate seat purchase for the pay-as-you-go services. That reading is for commercial tenants on pay-as-you-go. For a government tenant, start with the government section below. A tenant still holding older per-user licenses keeps them only until they expire, because the same licensing page states: “Existing licenses can still be assigned to new users. Once expired, you must switch to pay-as-you-go to continue using services.”
What a qualifying tenant adds is a billing setup. Microsoft’s Set up pay-as-you-go billing for document processing page lists two prerequisites, an Azure subscription in the same tenant as the service and an Azure resource group in that subscription, and states: “You must be a SharePoint Administrator or Global Administrator to be able to access the Microsoft 365 admin center and set up the service.” That billing route carries one budgeting fact. Microsoft’s pay-as-you-go pricing page states: “While these services leverage an Azure subscription for billing purposes, they do not apply to the Microsoft Azure Consumption Commitment (MACC) that your organization might have.” For budgeting, that means these charges do not draw down an Azure consumption commitment.
SharePoint Advanced Management follows a different licensing route from the document processing meters, and one of its conditions names Plan 2. Microsoft’s SharePoint service description states: “SharePoint Advanced Management is available as part of Microsoft 365 Copilot or as an add-on.” Its Prerequisites for SharePoint Advanced Management page lists the Plan 2 route as one qualifying condition, “Your subscription includes SharePoint K, P1, or P2, and your organization purchases the SharePoint Advanced Management Plan 1 add-on”, and the Copilot route as another: “If your organization has at least one Microsoft Copilot license assigned to a user, your SharePoint administrators automatically receive access to SharePoint Advanced Management capabilities to support your Copilot deployment”. If a Copilot rollout is the reason SharePoint Advanced Management is on the table, the permissions work that comes first is covered in SharePoint Permissions Cleanup Before Microsoft 365 Copilot.
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. The governance side of that information-architecture work is set out in Governance-First SharePoint Information Architecture for Large Enterprises.
Can a GCC or GCC High Tenant Run a SharePoint Premium Pilot?
A records team in a GCC or GCC High tenant that asks for a document processing pilot runs into Microsoft’s own terms before it reaches a budget. Microsoft’s Document processing pay-as-you-go terms of service state that “Document processing pay-as-you-go is not available for Office 365 government plans”, and, as of September 2026, the Licensing for document processing for Microsoft 365 page states: “For Government Community Cloud (GCC) organizations, pay-as-you-go licensing-and the services that require pay-as-you-go licensing-aren’t yet available.”
The same licensing page carries two sentences a GCC buyer has to read together. One states: “GCC organizations can continue to purchase and use per-user licenses until pay-as-you-go becomes available.” The other states: “Per-user licenses for these services are no longer available for purchase.” Microsoft’s page does not reconcile the two, so the rule for any government tenant, GCC or GCC High, is to confirm the purchase route with Microsoft before budgeting a pilot.
The storage-side services are further along in GCC. Microsoft’s Overview of Microsoft 365 Archive states: “Microsoft 365 Archive for SharePoint sites is now available for Government Community Cloud (GCC) organizations.” Its Overview of Microsoft 365 Backup states: “Microsoft 365 Backup is now available for Government Community Cloud (GCC) organizations.” Both statements name GCC; for a GCC High or DoD tenant, confirm availability with Microsoft as well.
If the pilot question is part of a larger move to GCC High, GCC High SharePoint Migration: A Defense Contractor’s Pre-Migration Guide to Customizations, Compliance, and Partner Selection covers that move.
Where the move is off SharePoint Server or out of several tenants, enterprise SharePoint migration services carry content, sites and permissions into SharePoint Online as one sequenced plan.
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.
If you are budgeting for SharePoint Premium, the budget is your document volume multiplied by the meters you switch on, plus the configuration work to point the right models at the right libraries.
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.
Is SharePoint Premium compatible with SharePoint Online Plan 2?
Microsoft’s Syntex service description states: “Users must have a valid Office 365, Microsoft 365, or SharePoint Online license to be eligible to use Microsoft Syntex.” Its licensing page for document processing states: “Any user in your tenant can use the services, provided they have a Microsoft 365 license.” Our reading is that SharePoint Online Plan 2 seats and the SharePoint included in Microsoft 365 E3 or E5 qualify without a separate seat purchase. What the tenant adds for pay-as-you-go billing is an Azure subscription in the same tenant as the service and an Azure resource group in that subscription. Government tenants are the exception covered in the next question.
Can a GCC or GCC High tenant use SharePoint Premium document processing?
As of September 2026, Microsoft’s pay-as-you-go terms of service state that “Document processing pay-as-you-go is not available for Office 365 government plans”, and its licensing page states: “For Government Community Cloud (GCC) organizations, pay-as-you-go licensing-and the services that require pay-as-you-go licensing-aren’t yet available.” The same licensing page also says “GCC organizations can continue to purchase and use per-user licenses until pay-as-you-go becomes available” and “Per-user licenses for these services are no longer available for purchase.” Microsoft does not reconcile those two sentences on the page, so for a GCC or GCC High tenant, confirm the purchase route with Microsoft before budgeting a pilot.
