SharePoint Embedded Billing Meters

SharePoint Embedded employs a pay-as-you-go (PAYG) billing model through an Azure subscription. Billing is determined by how much data in GB you store in SharePoint Embedded, transactions used to access and modify the container and container contents, and data that is egressed from SharePoint Embedded platform. Each of these factors contributes to the overall cost, ensuring that you only pay for the resources and services you use. You can view this usage and billing details in the Azure Cost Management.

SharePoint Embedded has three billing meters:

SharePoint Embedded Service Meters	Meter Unit
Storage	$/GB
API Transactions	$/Transactions
Egress	$/GB

Storage

Storage consumption meters in SharePoint Embedded apply to the storage used by files and documents along with their metadata and versions. Storage consumption also includes all content in the recycle bin and deleted container collection within SharePoint Embedded.

API Transactions

Each Microsoft Graph call made explicitly by the SharePoint Embedded application are counted one transaction and customers are billed based on the transaction count. See the examples of Microsoft Graph calls that can be made by a SharePoint Embedded application.

However, calls made by internal services to the containers, which the application has no control over, are not charged. Some examples of such nonchargeable transactions include:

1. Queries performed by the eDiscovery service to search through container content for compliance or legal purposes.
2. Admin actions taken by the SharePoint Embedded Admin or Global Admin on containers through SharePoint Admin Center or SPO PowerShell.

Egress

Egress refers to the data downloaded from the SharePoint Embedded platform to the customer's client device such as a desktop or mobile device.

However, certain types of data transfers are exempt from egress charges. These exemptions ensure that customers aren't billed for data transfers occurring within integrated Microsoft services, promoting seamless usage without extra costs for these specific internal operations. Some examples of these exemptions include:

1. File downloads from the SharePoint Embedded application server to the customer's Office Desktop client aren't charged.
2. File downloads from the SharePoint Embedded application server to the Web Application Companion (WAC) aren't charged.