NextTables Azure Marketplace Privacy Notice
TABLE OF CONTENTS
loading...
NEXTTABLES METERING POLICY
Last modified: 19.12.2025This Metering Policy explains how NextTables measures usage for billing of Users and Tables under Microsoft Azure Marketplace plans. It is intended to be linked from Marketplace plan listings, plan-level pricing descriptions, contractual amendments, and (where applicable) our Azure Marketplace Privacy Notice.
Precedence. If there is a conflict between (a) your Azure Marketplace order and the applicable Marketplace plan listing (including included entitlements and prices) and (b) this Metering Policy, the Marketplace order and plan listing prevail. This Metering Policy defines how we measure usage (for example, what counts as an “Active User” or an “Active Table”) for the included entitlements and for any overage meters described in the plan listing.
KEY TERMS
User
An individual with a unique account authorized by Customer to access the Service.Active User
A User whose account is marked as active in the Service and is permitted to access the Service.Included Users
The number of Active Users included in the applicable Marketplace plan (as stated in the plan listing).Billable User
An Active User. Customer’s plan includes up to the number of Active Users stated in the Marketplace plan (“Included Users”). Any Active Users above Included Users are overage usage and may be billed via Marketplace meters as described in the applicable plan listing.USERS: LIMITS, OVERAGES, AND SAFEGUARDS
User limits and overage confirmation
If Customer attempts to activate more Users than included/paid for, the Service may (a) block additional activations or (b) require confirmation of paid overage, as indicated in the applicable Marketplace plan.Overage confirmation may be implemented either:
- case-by-case (e.g., for each additional activation), and/or
- via account-level settings that allow pre-approval of overage (e.g., enabling Customer’s employees to activate additional Users without confirming each individual activation),
Activation safeguards
To prevent abuse or circumvention of license limits, changes to a User’s active status may be subject to reasonable technical safeguards, including limits on the frequency of activation or deactivation (for example, no more than one change per User per day).How Users are measured (monthly)
During each Monthly Measurement Period (see “Monthly Measurement Period and telemetry” below), Billable Users are measured as the maximum (peak) number of Active Users at any time during that Monthly Measurement Period. This approach is predictable and helps prevent circumvention by frequent activation/deactivation.TABLES: DEFINITIONS AND MEASUREMENT
Editable Table
A table or data object that Customer has explicitly enabled in the Service for create, update, delete, or writeback operations (each a Write Operation), as configured in the Service.Tables configured solely for read-only access (including lookups, reference data, validations, or display) are not Editable Tables.
Active Table (Billable Table)
An Active Table is an Editable Table for which at least one (1) successful Write Operation occurred during the applicable Monthly Measurement Period, regardless of whether the Write Operation is initiated through the Service user interface, an API, automation, or an integration.Write Operation
A successful create, update, delete, or writeback action executed through the Service and committed to the target system.Bulk operations are treated as Write Operations on the affected table.
Non-billable Tables
Read-only or lookup tables, internal system tables, and internal system writes are not Active Tables and are not billable.Clarification: Test/system writes are not counted if they do not commit to the customer’s target system. Internal tables and writes to internal tables are not counted.
How Tables are measured (monthly)
During each Monthly Measurement Period, a table is billable if it became an Active Table (i.e., at least one successful Write Operation occurred).PRICING PRESENTATION AND BILLING VIA AZURE MARKETPLACE
Included entitlements
Customer’s subscription plan (including Included Users, Included Tables/metrics if applicable, term, and fees) is as shown in the applicable Marketplace order and plan listing.Overage billing (“Additional … / Month”)
If Customer exceeds included entitlements for Users or Tables, Customer will be charged for overage usage via Marketplace meters as shown in the applicable Marketplace plan and/or Pricing & Metering documentation.Overage is presented in the Marketplace plan as:
- Additional Table / Month (price per table per month, as stated in the applicable plan)
- Additional User / Month (price per user per month, as stated in the applicable plan)
- An “Additional Table / Month” means a table that qualifies as an Active Table in that calendar month (see “Tables: Definitions and Measurement”).
- An “Additional User / Month” means a user that contributes to the peak count of Active Users in that calendar month (see “Users: Limits, Overages, and Safeguards”).
Disputes
Billing disputes must be raised within thirty (30) days of the Marketplace charge.MONTHLY MEASUREMENT PERIOD AND TELEMETRY
Monthly Measurement Period
Usage is measured on a monthly basis using the calendar month (e.g., January 1–31, February 1–28/29, etc.).Subscription terms (monthly and annual) and monthly overage
Customer may subscribe to a monthly or annual subscription term, as stated in the applicable Marketplace plan listing.Regardless of whether the subscription term is monthly or annual, any overage for Users and Tables is calculated on a monthly basis (per calendar month) and billed via Marketplace meters in accordance with the applicable plan listing.