Work 365 Usage Based Subscriptions are used to invoice customers in arrears based on consumption. Currently in Work 365 the main consumption and Usage based subscription is used to Bill for Azure based Subscriptions.
Azure is a usage-based subscription which means customers pay for their services after the usage of the services is reported.
Usage based subscriptions don’t have an initial quantity. They are billed to the end customer using the Markup as shown in the figure below:
Microsoft retail price is $100 partners get billed $85. Standard Azure Margin is 15%. Which effectively means that the cost has to be marked up by 17.64 percent to equal retail price.
- Note: Microsoft calculates PEC for Azure Plan subscriptions which impacts how Work 365 calculates margin for Azure plan. Refer to Azure Plan for an overview of Azure plan in Work 365.
- To see a breakdown of how Azure plan is calculated in Work 365, refer to Azure Plan Calculations.
On the usage-based subscription, there are important fields to take note of:
- Consumption Threshold: A maximum threshold amount on a customer’s consumption
- Threshold Status: The percentage a customer has used up their consumption threshold amount. An email notification is sent to the Billing Contract Owner and the Manual Provider Email Recipient whenever a usage-based subscription reaches the 80% and 100% threshold marks. See the email template below.
- Markup Percentage: The profit margin on the subscription.
- Note: Effective v3.0 a default markup % can be added at a global level in the Work 365 Configuration Settings .
- Current Cycle Consumption: The customer’s actual consumption.
- Allow End User Modification: Usage Based Subscriptions are not allowed for user modification on the self-service portal.
The daily usage details are imported every day into the Work 365 application through the Data Import mechanism in Dynamics 365.
The price information under the usage summary are tentative prices, and they are only an estimate on usage consumption.
- Note: Usage detail records are not used to calculate the total amount due on the invoice. However, these usage detail records are captured in the attached csv file of the invoice found in the details section.
- Note: Work 365 currently does not support pulling in usage detail records for Azure Plan subscriptions or subsequent entitlement subscriptions.
Usage Summary and Details
The monthly summary data is imported through the Provider Invoice. Microsoft Partner center makes the Provider Invoice available at the Billing Date and this data is synchronized with work 365. The customer-facing invoice, and the attached csv file, is created using the Markup percentage specified in the subscription. As the records on the usage summary get pulled in, the Current Cycle Consumption field on the subscription get updated automatically.
Usage information and Invoices
All the usage summary data from Microsoft’s invoice and reconciliation files is automatically sorted and assigned to the appropriate Azure Subscription and customer. Usage-based subscriptions have the billing information for the previous month’s billing cycle on the billing contract invoices. The billing information will appear as a single line item on the invoice for the customer’s total consumption from the previous month.
- If an existing usage-based subscription does not have consumption from the previous billing cycle, the subscription is not included in the billing contract invoice as a line item because there is nothing to bill the customer.
- If you want an Azure subscription to be billed separately from your license or service-based subscriptions, you would need to have a separate billing contract set up only for the Azure subscription.
Work 365 also notifies the Billing Contract owner and the Manual Provider Email Recipient email specified in the email template when certain consumption thresholds are met.
Note: Work 365 does not manage consumption levels; it only tracks consumption and notifies on consumption threshold statuses.