Skip to content
digitapulia.com
Fixed-price engagements

Azure cost review

Our cloud bill keeps growing and we do not understand why.
What we do
We look for unused resources, databases larger than they need to be and storage that costs more than it should.
How we do it
With read-only access to your Azure subscription, we read the billing of recent months and compare it with what is really used: virtual machines left running that no one uses, disks and snapshots that are no longer needed, databases with more capacity than they use, and data kept in a more expensive storage tier than it needs. We note each possible saving with its estimated amount and its risk: what could stop working if it is applied and how to check that beforehand. We go through the list with your technical team, who know which resources are critical, and hand it to you sorted by amount and by risk.
What you receive
A list of possible savings, each with its estimated amount and its risk.
What changes for you
You know what can be removed or reduced on the Azure bill without putting what works at risk. Saving decisions are taken with the risk written next to them, not by switching something off to see what happens.
What we need from you
Read-only access to the Azure subscription and its billing, and someone on your technical team who knows what each resource is for.
Who it is for
Finance and IT
How you buy it
At a fixed price or as a share of the savings achieved: the formula and the price are written down before we start and we give them to you when you ask.

Example use cases

These are examples: they do not describe a real client.

  • A fashion company in Italy that also sells online in Spain, with its store on Azure

    The situation

    The online store and its ordering system have been on Azure for years. For each peak season, bigger servers and databases were added, and afterwards no one scaled them back down. Each month the bill is higher than the month before, and finance receives a document many pages long that no one knows how to read.

    What we do

    We read the billing and compare it with the real use of each resource. We find servers sized for peak season running all year, a test database with the same capacity as the store's, and image storage in the most expensive tier that is hardly ever read. Each saving goes on the list with its estimated amount and its risk, and with the technical team we decide which ones are applied now and which are tested first.

  • A packaging machinery maker in Italy with a subsidiary in Chile, which moved its servers to Azure as they were

    The situation

    A few years ago the company moved its servers to Azure one by one, without changing them. Since then the Chilean subsidiary has added resources of its own, and no one has a list of what belongs to whom. The bill reaches the parent company in Italy, and finance does not know which part could be removed.

    What we do

    We read the subscription and sort the resources by use. We find virtual machines copied from the old servers with more capacity than they use, disks from servers that no longer exist, and test environments running at night and at weekends. Each saving goes on the list with its estimated amount and its risk, and with the technical teams in Italy and Chile we decide what is applied first and what is tested beforehand.

Frequently asked questions

Is anything changed in my subscription during the review?

No. The review is done with read-only access. Which savings are applied, and when, is your decision, with the list in hand.

What does the risk of each saving mean?

What could stop working if that saving is applied, and how to check it beforehand. Switching off a test environment at night carries little risk; scaling down the online store's database is tested first.

How does the price work as a share of the savings?

Instead of a fixed price, a share of what you save with the changes applied can be agreed; the formula and how the saving is measured are written down before we start.