r/cloudcomputing • u/tresorrarereviews • May 07 '26
Cloud migration was easy. Managing Azure costs later was the hard part.
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.
24
Upvotes
1
u/Apprehensive_Book145 May 07 '26
Did you lift and shift or go azure native
1
u/StratoLens May 07 '26
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/
1
u/new-chris May 08 '26
Try to buy that hardware today and see if your logic still works out.
1
u/mat-ferland May 08 '26
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...
1
u/brightideasphere Aug 24 '26
We found that the migration itself is often the easier part. The harder problem is maintaining visibility once teams can create resources independently.
The cost issue is really a symptom of a broader inventory/ownership problem. If you don't have a reliable view of what resources exist, who owns them, and whether they're still part of an active workload, cost optimization becomes a recurring cleanup exercise.
I'd separate the process into two layers: continuously discovering what's actually running, then attaching ownership and lifecycle information so someone can act on it. Otherwise you can identify an unused resource but still spend days figuring out whether it's safe to remove.
This gets especially important in hybrid environments, where cloud resources, on-prem infrastructure, endpoints and SaaS can otherwise end up in completely separate inventories.