Shpend Kelmendi is a Software Engineer and Cloud Architect at bbv Software Services AG. He leads the Cloud Community. He helps teams build solutions that are simple, sustainable, and customer-focused. His playground: Azure, DevOps, and cloud architecture — where complexity is optional, clarity is required. As a Microsoft Certified Trainer (MCT), he shares what he learns and helps others succeed in the cloud.
View all authors
You have to deploy your workload.
You follow best practice and provision your workload per IaC and CI/CD pipelines.
Now that sounds easy.
But how do you do this when you need to deploy your workload to multiple Entra ID tenants?
In this blog post you will learn how this works and how you can do it by yourself step by step.
Managing costs in the cloud is crucial to avoid unexpected expenses.
How many times have I read "Azure just charged me 1k dollars because of a misconfiguration".
Did it happen to you as well? Me too. And I know how stupid you feel after that.
Sometimes it is not even our fault. (cough* strange defaults from Azure *cough)
So to avoid that, we can setup budgets and get notified when we reach certain thresholds.
It's important to know which scope you want to set the budget on. It can be at management group level, subscription level or resource group level.
Choose the scope you are responsible for and want to monitor costs for.
What are the options? Let's explore them.
Organizing Azure resources is one of those rare tasks that sounds straightforward until you actually start doing it.
Suddenly you’re trying to balance cost allocation, security boundaries, governance rules, domain ownership, deployment pipelines, and team autonomy. All while the number of services grows faster than your architecture diagram can keep up.
If designing cloud boundaries feels like organizing a city while it’s still being built, that’s because it is.
And like any good city, Azure needs structure: districts, buildings, addresses, zoning rules, and a way to understand who owns what.
Why? Because moving buildings (or Azure resources) is not always easy.
This guide takes a practical look at how to design resource boundaries in Azure—using concepts from Domain-Driven Design (DDD), Team Topologies, CAF, Well-Architected Framework.