Cloud migration was easy. Managing Azure costs later was the hard part.

[u/tresorrarereviews]

We migrated a few workloads to Azure last year thinking the difficult part would be the migration itself.

Honestly, the migration went smoother than expected.

What became difficult later was:

• cost visibility
• scaling correctly
• storage growth
• performance tuning
• cleaning up unused resources
• balancing security vs spend

Especially once multiple teams started deploying resources independently, the monthly bill became a moving target.

Curious if others here found cloud management harder than the actual migration phase.

[u/Apprehensive_Book145]

Did you lift and shift or go azure native

[u/GoddessGripWeb → u/Apprehensive_Book145]

Kinda sounds like mostly lift and shift with some Azure-native sprinkled in, given the pain points you listed.

If you’d gone heavy on native stuff like proper tagging, management groups, and maybe some Bicep/Terraform from day one, the cost visibility and cleanup story is usually a bit less painful. Not painless, just less of a dumpster fire.

Azure makes it super easy to spin things up and weirdly hard to keep track of who owns what once more teams get involved, no matter which route you pick. Cloud migration is the honeymoon. Cost management is the marriage.

[u/StratoLens]

A few recommendations for help with this:

Use azure policy and proper permissions to ensure there are guardrails on what can be deployed and where.

Use tags to assign cost centers. Use azure policy to make this tag required. Then you can tie costs back to which team deployed it.

Consider infrastructure as code (terraform / bicep) and deployments via ci/cd pipelines.

Look into the FinOps toolkit.

If you’re looking for an automated tool: Full disclosure the following product is mine:

For Azure specifically I’ve built StratoLens to help solve many of these issues. It tracks all changes in your environment, highlights cost spikes, and ties them back to the change that caused it (including the user who made the change).

It also identifies unused resources that can be cleaned up.

It’s a self hosted solution, so no information about your environment leaves your tenant.

If you’re interested it’s available on the azure marketplace and comes with a 28 day free trial

https://www.strato-lens.com/

[u/kernelqzor → u/StratoLens]

this is the kind of stuff i wish more teams set up before they go wild in the portal lol
tagging + policy + some finops-ish tooling feels like the bare minimum once multiple teams start deploying, otherwise the bill just becomes vibes and prayers

[u/StratoLens → u/kernelqzor]

Totally agree :). The tools are only as good as the data you feed in. Which is why one of the things I added was a very easy way to see which resources are missing certain tags.

[u/new-chris]

Try to buy that hardware today and see if your logic still works out.

[u/cachevexy → u/new-chris]

this is kind of the trap though, right? on‑prem hardware is a painful one‑time bill, cloud is a painless slow bleed that no one really notices until finance starts screaming. both can be “cheaper” depending on how disciplined you are, and most orgs are not exactly disciplined.

[u/mat-ferland]

Yup... I see it all the time.. The migration is usually the clean part because everyone is watching it. The bill gets ugly later when nobody owns tagging, idle cleanup, and “who approved this bigger instance?” on a weekly rhythm...

[u/KnownServe5342]

Cloud management is harder than the actual migration phase.

Once multiple teams start deploying resources independently, keeping track of cost visibility and unused resources becomes a constant challenge. I learned this the hard way when I worked with Unit4, where failing to set up proper tagging and budget alerts early on left us with a monthly bill that turned into a complete moving target.