Azure Fundamentals: Tenants, Subscriptions and Resource Groups
Understand how Azure tenants, management groups, subscriptions and resource groups fit together, and how to structure them for access control and billing.
How Microsoft Azure is structured, which services and AI tools matter most, how its pricing and discounts work, and how to get started through official channels.
Microsoft Azure is Microsoft’s public cloud, and this Microsoft Azure overview explains how it is structured, what it charges for and who tends to benefit most. Azure is closely tied to Microsoft Entra ID, Windows Server, SQL Server, Microsoft 365 and GitHub, which makes it a natural fit for organizations already built around Microsoft technology.
Before looking at services, it helps to understand the containers everything sits in. A tenant is your organization’s Microsoft Entra ID directory. Inside it, subscriptions are the billing and access boundaries, and each subscription holds resource groups that bundle related resources so you can deploy, secure and delete them together.
Getting this hierarchy right early makes access control and cost reporting much easier later. Our guide to Azure tenants, subscriptions and resource groups shows practical layouts for small teams and larger organizations.
| Service | Purpose |
|---|---|
| Azure Virtual Machines | Windows and Linux VMs in many sizes, including GPU-enabled series |
| Azure App Service and Azure Functions | Managed web app hosting and event-driven serverless code |
| Azure Kubernetes Service (AKS) | Managed Kubernetes clusters |
| Azure SQL, Cosmos DB, Azure Database for PostgreSQL and MySQL | Managed relational and multi-model databases |
| Azure Blob Storage and Azure Files | Object storage and managed file shares |
| Virtual Network, Load Balancer, Application Gateway | Private networking, layer 4 load balancing and a layer 7 gateway with optional web application firewall |
| Azure DevOps and GitHub Actions | Repositories, pipelines, boards and CI/CD automation |
Azure’s AI offering has two main layers. Azure OpenAI provides API access to OpenAI models hosted in Azure, with Azure networking, identity and data controls, and it is managed through Microsoft Foundry (formerly Azure AI Foundry), which also offers models from other providers. Azure Machine Learning covers the full ML lifecycle for teams that train and deploy their own models. Prebuilt services for speech, vision, language and document processing sit alongside these.
Microsoft renames and reorganizes these products fairly often, so treat any name as a pointer to the current docs. For a developer-focused tour, see our overview of Azure AI services and how developers use them.
Azure bills pay-as-you-go by default, with most compute metered per second or per hour and storage metered per gigabyte per month. Common ways to reduce cost:
Microsoft Cost Management, included with Azure, provides budgets, alerts and cost analysis by subscription, resource group or tag.
The portal is large, and the same task can often be done in several ways (portal, Azure CLI, PowerShell, Bicep, Terraform). Pick one infrastructure-as-code approach early to keep environments consistent.
Pricing pages can be hard to compare because VM series, regions and licensing all change the final cost. Use the official pricing calculator and review Cost Management after the first few weeks.
Subscriptions have default quotas, for example on vCPUs per region and per VM family. Access to some AI models also depends on region and may need approval. Request quota increases through the Quotas page or a support request in the portal.
NewCloudStore is independent and not affiliated with Microsoft; trademarks belong to their owners.
Understand how Azure tenants, management groups, subscriptions and resource groups fit together, and how to structure them for access control and billing.
The Azure services teams build on, how to secure a subscription with Entra ID and NSGs, management habits with tags and resource groups, and how Azure pricing options compare.
Learn the four building blocks of infrastructure monitoring, metrics, logs, alerts and uptime checks, and how to combine them into a practical starter setup.
A stage-by-stage guide to planning a cloud migration, from inventory and dependency mapping to choosing a strategy and running a rehearsed, reversible cutover.
A practical developer guide to Azure AI services, mapping each API to real tasks and explaining resources, authentication, pricing models and quota requests.
How AWS, Azure and Google Cloud differ from developer clouds like DigitalOcean and Hetzner, and how to tell which one your project actually needs.
Send a note and we will point you to the right overview, guide or official documentation.