Microsoft Licensing

What we build

• Azure subscriptions under Azure Plan — provisioned inside the landing zone and management group structure we designed, not bolted on afterwards
• Microsoft 365, Dynamics 365, and Power Platform licences — assigned, tracked, and adjusted as headcount moves
• Consolidated billing — one monthly invoice covering licences and Azure consumption
• CloudOI as partner of record — we hold the support relationship and escalate to Microsoft on your behalf
• Tier-1 support from the engineers who built the platform — not a service desk seeing your estate for the first time
• Cost governance from day one — tagging, budgets, reservations, and savings plans reviewed against actual consumption
• Monthly right-sizing — idle resources and unassigned licences surfaced as they appear, not at renewal
• Subscription hygiene — naming, management groups, and Azure Policy applied to every subscription we provision
• Clean transfer in or out — moving from another channel, or away from us, without downtime

What this does not change

• Your tenant, your directory, and your data stay yours — ownership does not move to CloudOI
• Subscriptions stay portable: you can transfer to another partner or direct to Microsoft at any time
• Build work is still scoped in writing and still invoiced only when you are satisfied
• If your volume makes an Enterprise Agreement or direct Microsoft contract the better commercial fit, we will say so

The result

One partner is accountable for the architecture, the subscriptions, and the bill. When consumption moves, the people who can explain it are the people who built what is consuming it.

Why CloudOI

Most organisations buy licences from one supplier and architecture from another, then discover the two were never talking — capacity nobody designed, licences nobody assigned, and a bill nobody can attribute. As a CSP indirect reseller we close that gap.