Microsoft licensing built around what you use next
Microsoft licensing is no longer just a seat count. Renewal dates, commitment terms, Copilot, agents, Azure and usage-based services can all change what you should buy and when.
We help you plan the next commitment, source the licensing and put the agreed services into operation.
Start the review around 60 days before your renewal date
Start with your subscription export, renewal position or the change you are planning. We will map:
The first review is free.
The date can matter as much as the licence
Three rules worth knowing before the next renewal.
Billing frequency and commitment are different decisions. An annual subscription paid monthly still carries an annual term.
For CSP New Commerce licence-based subscriptions, reductions generally need to be made within seven days of the relevant purchase, seat addition or renewal. Adding new seats does not reopen the reduction window for older seats.
An eligible CSP-to-CSP transfer keeps the existing subscription term and renewal settings. It does not create a new cancellation window, and it does not require a tenant migration.
Buy, renew and change Microsoft licensing with the technical work around it
Map the subscriptions, quantities, terms and renewal dates. Decide what should change before the next commitment starts, including new users, security requirements and Copilot adoption.
We move your licensing across through the right Microsoft transfer route and manage the handover with your current provider.
Bring licensing and implementation together for Microsoft 365, Copilot, identity, device management, security and Power Platform requirements.
Complete the agreed purchase or provider transition, then configure the services, security controls and migration work that go with it.
Committed seats and usage-based services need separate budgets and controls
Microsoft 365 and Copilot user licences are committed quantities. Azure, Copilot Studio and other usage-based services can change with consumption. Put them in one budget and you lose sight of where the money goes.
For user and device licensing, plan the right quantity, term, billing frequency and renewal date before the commitment is made.
For Azure, agents and consumption services, agree who owns the spend, how usage is monitored, which budgets or limits apply and what happens when a threshold is reached.
Separate the people who need a paid Copilot licence from the workflows or agents that create additional consumption. The commercial model should follow the use case.
You can change the commercial relationship without moving your tenant
A licensing-provider change is not automatically a Microsoft 365 migration.
Web-direct, Enterprise Agreement and other purchasing arrangements follow different transition paths. We establish that route before proposing the change.
- How the subscriptions are purchased today
- Which subscriptions are eligible for the Microsoft transfer process
- The renewal dates and existing commitments
- The customer approvals required
- The new billing and support responsibilities
- Any administrative access required for implementation or support
Compare the licence mix, or bring us the renewal
Use it when the question is:
Which Microsoft 365 licences fit our people, security and Copilot requirements, and what could the mix cost?
Use it when the question is:
What should we buy or change at the next renewal, and how should the commercial arrangement be structured?
Licensing that fits how you work
From on-premises Exchange to a managed Microsoft 365 environment.
We moved VLI Conveyors from on-premises Exchange to Microsoft 365, including identity, Intune and a security baseline, followed by ongoing managed IT across Microsoft 365, infrastructure, backup and security.
The difference is that we license the same environment we run and support.
Microsoft licensing and renewal questions
Can you supply Microsoft licensing without taking over our IT?
Yes. You can buy licensing on its own and add implementation or support only if you want it.
What should we send for a licensing review?
A subscription export from your Microsoft admin portal or your current provider, showing products, quantities, terms, billing frequency and renewal dates. Add the change you are planning, such as Copilot, new staff, a provider move or a security requirement.
When should we start the review?
Around 60 days before the renewal date, and earlier for larger or more complex environments. That leaves time to agree seat changes, terms and any provider move before the next commitment starts.
Can we reduce seats during an annual commitment?
Generally only within the seven-day window after a purchase, seat addition or renewal. After that, reductions usually wait for the next renewal. We confirm the rule for the actual subscription before making a change.
Does changing CSP provider move our data or start a new term?
No. An eligible CSP-to-CSP transfer keeps the same tenant and continues the existing term. A tenant-to-tenant migration is a separate technical project.
Can you review Copilot and agent costs as part of the renewal?
Yes. Paid Copilot seats are planned alongside agent, Copilot Studio and Azure consumption, so committed licences and usage-based costs are budgeted separately.
Plan the next Microsoft commitment before the renewal window closes
Send us your subscription export, renewal position or the Microsoft change you are planning. We will establish the decisions that need to be made, the applicable purchasing route and the implementation work around it.
Working out who needs what? Compare Microsoft 365 licences
Prefer email? contact@inlightit.com.au