REKKY first. Mission complete.
AWS and Azure cost review
It's done.
A walk through the AWS accounts and Azure subscriptions already on the invoice. What is still running, who can create more, and whether finance and the on-call see the same platform.
Why this is its own review
The cloud cost page asks who owns the spend. An AWS and Azure cost review opens the consoles those invoices come from. The two clouds are not the same shape. AWS tends to arrive as accounts, regions, and a long tail of services someone turned on. Azure tends to arrive as subscriptions, resource groups, and a tenant that outlived the team that created it. The review uses the shape you have, not a generic checklist pasted over both.
Say which cloud is on the bill. If you run only one, the scope is that one. We do not tour a cloud you do not pay for. If you run both, the scope says whether they are one review or two, because the people who can open them are often not the same person.
We do not resell either cloud. There is no marketplace offer on this page and no commitment we ask you to buy.
What we look at in AWS
Accounts first. Which accounts exist, which ones still receive a bill, and which ones nobody will claim. Then regions. A region that was a test and is now a quiet bill is a common finding. Then the services that are easy to leave running: instances, load balancers, addresses, volumes, and logs that were never given an end.
Who can create more is as important as what is already there. A wide identity that can open resources in an account with no owner will rebuild the bill after you clean it. We look at that ability with the person who administers access. We do not export a policy and leave.
Commitments already purchased, such as a savings plan or a reservation, are compared with the usage the account can show. A match is noted. A mismatch is noted. A recommendation to buy a new commitment is not the product.
What we look at in Azure
Subscriptions and resource groups first. A subscription created for a project, a migration, or a team that has since moved is a usual place for spend with no owner. Resource groups named for a date or a person are read with someone who was there, not guessed from the name.
We look at what is still allocated: compute that is off but paid, disks that outlived the machine, and services left in a region you thought you had left. The tenant's ability to create another subscription matters as much as the resources inside the current one.
If Azure and AWS both bill you, we do not merge them into one number and stop. Each platform keeps its owners. A shared finding is only a finding if the same gap is real in both, such as nobody who can explain the largest line.
- Accounts or subscriptions that still bill, and the person who will claim each one.
- Regions or resource groups left from work that ended.
- Who can create the next resource without a second person.
- Commitments already on the invoice, set next to visible usage.
What you leave with
A written list of what is running and unowned, what is running and required, and who can still create more. The order is practical: what is safe to stop with the owner present, what needs a maintenance window, and what should not be touched.
Nothing is deleted during the review unless the scope explicitly includes a change and the owner is in the session. A review that surprises production is a failed review. We run the engagement end to end and work around your normal operations, but we'll need access to the right areas and the right people while we do.
The narrower cloud cost page is the right start if you are not yet sure the pain is AWS or Azure specifically. The Recon Assessment, starting at $15,000 plus expenses, is the four-day form when this review needs to sit beside the platform and the on-call.
Questions on this work
Is an AWS and Azure cost review the same as a general cost pass?
The general pass asks who owns the spend. This review opens the AWS accounts and the Azure subscriptions: regions, projects that ended, who can create resources, and whether the bill the finance team sees is the platform the on-call runs.
Do you resell cloud commitments?
No. We do not sell reserved capacity, savings plans, or a marketplace listing. If a commitment is already on the bill, we say whether it matches the usage we can see.
What if we run only one of the two clouds?
Say which one. The review is scoped to the accounts that exist. We do not tour a cloud you do not run.
Contact
Describe the platform you have.
Say AWS, Azure, or both, and name the person who can open the account. We run the engagement end to end and work around your normal operations, but we'll need access to the right areas and the right people while we do.
Recon Assessment, starting at $15,000 plus expenses. Four days on site with your team, then a written report within about two weeks.