Key concepts for building Azure apps

Before you get too far in designing your application to run on Azure, chances are you'll need to do a little planning ahead of time. As you get started, there are some basic Azure concepts that you need to understand to make the best decisions for your scenario. Considerations include:

Azure regions

A region is a set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. Azure gives you the flexibility to deploy applications where you need to, including across multiple regions to deliver cross-region resiliency when necessary.

Typically, you want all of the resources for a solution to be in the same region to minimize latency between different components of your application. This means if your solution consists of an Azure App Service, a database, and Azure Blob storage, all of these resources should be created in the same Azure region.

Not every Azure service is available in every region. The Products available by region page can help you find a region where the Azure services needed by your app are available.

Azure resource group

A Resource Group in Azure is a logical container to group Azure Resources together. Every Azure resource must belong to one and only one resource group.

Resource groups are most often used to group together all of the Azure resources needed for a solution in Azure. For example, say you've a web application deployed to Azure App Service that uses a SQL database, Azure Storage, and also Azure Key Vault. It's common practice to put all of the Azure resources needed for this solution into a single resource group.

A diagram showing a sample resource group containing an App Service, SQL database, Blob storage, and a Key Vault.

This makes it easier to tell what resources are needed for the application to run and what resources are related to each other. As such, the first step in creating resources for an app in Azure is usually creating the resource group that will serve as a container for the app's resources.


If you've developed on-premises, you are familiar with promoting your code through dev, test, and production environments. In Azure, to create separate environments you would create a separate set of Azure resources for each environment you need.

A diagram showing DEV, TEST, and PROD environments with a separate set of Azure resources in each environment.

Since it's important that each environment be an exact copy, it's recommended to either script the creation of resources needed for an environment or use Infrastructure as Code (IaC) tools to declaratively specify the configuration of each environment. This makes sure that the environment creation process is repeatable and also give you the ability to spin up new environments on demand, for example for performance or security testing of your application.

DevOps Support

Whether it's publishing your apps to Azure with continuous integration or provisioning resources for a new environment, Azure integrates with most of the popular DevOps tools. You can work with the tools that you already have and maximize your existing experience with support for tools like: