Châteauguay
IT services in Châteauguay: a cloud bill you can actually read
Azure is billed by usage and Microsoft 365 by licence, month after month. That is convenient, until the day nobody can say what a given line is for. OKTO Solutions offers SMBs in Châteauguay a follow-up of that bill: read it, remove what no longer serves, keep the rest in hand. The work is done from Trois-Rivières, about 165 km away.
A cloud bill drifts when nobody looks at it: a test machine left running, a disk still billed after its server was deleted, a Microsoft 365 licence paid for an employee who left. In Châteauguay, OKTO Solutions offers Azure consumption tracking and seat-by-seat licence adjustment, remotely, from Trois-Rivières.
Who keeps an eye on the Azure and Microsoft 365 bill of a Châteauguay business?
OKTO Solutions offers SMBs in Châteauguay the management of their cloud, bill included. In Azure, consumption is followed with the same weight as patching: spending is reviewed once a month and variances are explained, test environments are shut down outside working hours, oversized resources are scaled down when the measurements allow it, and orphaned disks, addresses and backups are removed. Resources are also tagged by department, so it is clear who consumes what. On the Microsoft 365 side, the plan is chosen seat by seat, based on real usage, then revised when someone changes roles or leaves, because a dormant licence costs as much as one in use. OKTO publishes no prices: costs are presented on request, once the inventory is done. The service runs from Trois-Rivières, about 165 km from Châteauguay, where OKTO has neither an office nor a technician. By default, data stays hosted in Canada.
The problem
Why does a cloud bill climb when nobody decided it should?
Because in the cloud, creating takes one click and forgetting costs nothing on the spot. Three scenarios keep showing up. A virtual machine built for a trial in February is still running in November. A server gets deleted, yet its disk stays behind and keeps being billed. A resource sized for the busiest week holds that size all year.
None of these is an outage. Everything works, which is why nobody sees them: the line joins the total, and the total gets paid. With a server in a back room, the purchase was made once and capacity never moved again. Here, spending follows usage, up as well as down, provided someone is minding it.
The first sorting happens before any migration. At inventory time, each system is classified: what can move as is, what should be modernized, what is better left on site. A system with no business in Azure will never turn up on the bill.
Migration plan Approve A sample screen, with a fictitious company and dates: five systems, one written decision for each, between Azure, staying on site and retirement.
The picture
On-site server, Azure or hybrid: where does the spending come from?
All three models cost something. What changes is when you pay and what needs watching afterwards.
| Model | How you pay | What gets left out of the math | What to watch |
|---|---|---|---|
| On-site server | A purchase every few years: the machine, the storage, the licences | Electricity, floor space, replacement when the time comes and the hours of upkeep | Capacity frozen on purchase day, so sized for the worst week of the year |
| Azure | No hardware to buy: a recurring expense that tracks real usage | Whatever was created for a passing need and never switched off | Consumption, line by line |
| Hybrid | A smaller purchase on site, the remainder as an operating expense | A bit of both lists | Where each system lives, put in writing |
An honest comparison puts every one of those lines on the scale, on both sides. The cloud and Microsoft Azure page describes the three models in detail, and the vCIO module is there to place a migration at the right moment in the budget.
The method
Which habits keep Azure consumption in hand?
Six habits, always the same ones. None is complicated. What is usually missing is someone whose job it is.
- Tag every resource by department. Without a tag, there is no telling who consumes what, or whom to ask before switching something off.
- Review consumption once a month. A variance gets looked at and explained. Writing it down is not enough.
- Shut down test environments outside working hours. The shutdown is scheduled, so it relies on nobody’s memory.
- Shrink what is too big. A resource is scaled down when the measurements allow it, never by guesswork.
- Clear out the orphans. Disks, addresses and backups that outlived the resource they served.
- Reserve capacity when the load is steady. A commitment is made on what is predictable, not on a hope.
Microsoft 365
And on the Microsoft 365 side, where does the money go?
Into licences. When we pick up an environment nobody has ever managed, two findings keep coming back: licences still paid for employees who left, and subscriptions at a higher tier than the job requires. A dormant licence costs exactly what a licence in use costs.
The fix takes few words to describe. The plan is chosen seat by seat, starting from the real job: mail and nothing else, desktop applications, managed devices, or the advanced security features. One subscription for everybody is seldom the right math. The choice is revisited when someone changes roles or leaves.
A word on Copilot: it is a licence that sits on top of a plan, never in its place. So it is decided seat by seat as well. Costs are presented on request, when the inventory of workstations is complete.
A sample screen, with fictitious names and figures: one arrival, one departure, and the licence counter follows the headcount.
The ground
Châteauguay, about 165 km from Trois-Rivières
Châteauguay sits on Lac Saint-Louis, and the river of the same name runs through it. The city belongs to the Roussillon regional county municipality, in Montérégie; Autoroute 30 and Routes 132 and 138 pass through. There were 53,508 residents in 2025: the Institut de la statistique du Québec notes that this figure is provisional.
A cloud bill is read in Microsoft’s portals, not in a server room. That work lends itself to remote delivery, and this is how we offer it: OKTO has one office, in Trois-Rivières, and nobody stationed in Châteauguay. If a server stays within your walls, in a hybrid setup, it joins the same monitoring as everything else. A visit is planned when the mandate requires it, and we announce no on-site response time.
For an outage that blocks work after closing, an emergency line exists: it is included in the Complet plan. The content of each level is detailed on the packages page, and the map of the territory on the service areas page. To get started, the contact page is enough: keep your latest bill within reach.
Questions and answers
Your questions about the cloud bill in Châteauguay
Do you have an office in Châteauguay?
How much does Azure cost for a business in Châteauguay?
Is tracking the Azure bill part of a managed Azure mandate?
How do we spot a Microsoft 365 licence paid for nothing?
Does everything have to move to Azure for it to be worthwhile?
Does our data leave Canada?
Do you know what every line of your bill is for?
Show us an Azure invoice or the list of your Microsoft 365 licences. We tell you what we read in it, line by line, and what deserves a question.
Reviewed by Antonio Pazzi, president of OKTO Solutions · updated