Purpose and Scope
This VMATIX service schedule sets out the commercial and service framework for microsoft licensing, azure consumption, tenant governance, and service administration. It should be read together with the VMATIX Master Service Agreement, any order form, and any supporting implementation documentation agreed with the customer.
The schedule defines the services included, assumptions relied upon during delivery, dependencies on third-party vendors or customer-owned platforms, and the operating standards expected by VMATIX and its customers.
Service Delivery Model
VMATIX will provide microsoft licensing, azure consumption, tenant governance, and service administration using appropriately qualified personnel, approved delivery methods, and documented operating procedures aligned to the customer environment and risk profile.
Where the service depends on nominated suppliers, carriers, hyperscalers, or software publishers, VMATIX will coordinate service delivery and escalation management, while the customer acknowledges that certain underlying service elements may remain subject to third-party terms and platform constraints.
Customer Responsibilities
The customer must provide timely access, accurate technical and commercial information, authorised contacts, and any decisions required to keep implementation, support, security, and change activity on schedule.
The customer remains responsible for lawful use of the services, user behaviour, internal governance approvals, and any data, hardware, or software retained under the customer's control unless expressly included within the contracted VMATIX service scope.
Governance, Billing, and Change
Commercial charging, invoicing frequency, contract term, renewal approach, and any usage-based elements are governed by the signed order documentation and applicable commercial schedules.
Changes to scope, service levels, onboarding assumptions, integrations, or support requirements should be requested through VMATIX change control so operational, security, and commercial impacts can be reviewed before implementation.