Events
May 19, 6 PM - May 23, 12 AM
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register todayNote
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The term resource is used in the same way in both Azure and Amazon Web Services (AWS). A resource is a manageable item. It could be a virtual machine, storage account, web app, database, or virtual network, for example.
AWS resource groups vs. Azure resource groups
Resource groups in Azure and AWS are used to organize and manage resources. There are, however, some key differences:
- Deleting an AWS resource group doesn't affect the resources. Deleting an Azure resource group deletes all the resources in it.
- In Azure, you must create a resource group before you create a resource. A resource must be part of a single resource group.
- In Azure, you can track costs by resource group. In AWS, you can use cost allocation tags to filter on specific resources.
Resource deployment options
Azure provides several ways to manage your resources:
Azure portal. Like an AWS dashboard, the Azure portal provides a web-based management interface for Azure resources.
REST API. The Azure Resource Manager REST API provides programmatic access to most of the features that are available in the Azure portal.
Azure CLI. Azure CLI provides a command-line interface that you can use to create and manage Azure resources. Azure CLI is available for Windows, Linux, and macOS.
Azure PowerShell. You can use the Azure modules for PowerShell to run automated management tasks by using a script. PowerShell is available for Windows, Linux, and macOS.
ARM Templates. Azure Resource Manager (ARM) templates provide JSON template-based resource management capabilities that are similar to those of the AWS CloudFormation service.
Bicep. Bicep is a domain-specific language that uses declarative syntax to deploy Azure resources.
Terraform. You can use Terraform to define, preview, and deploy cloud infrastructure by using HCL syntax.
With each of these interfaces, the resource group is central to the creation, deployment, or modification of Azure resources. The implementation is similar to the stack implementation that's used to group AWS resources during CloudFormation deployments.
Tagging
Tagging, in both Azure and AWS, enables you to organize and manage resources effectively by assigning metadata to the resources. Tags are key-value pairs that help you categorize, track, and manage costs across your cloud infrastructure. Both AWS and Azure support attribute-based access control (ABAC) based on tag values. Although Azure and AWS tagging are similar, there are some differences:
- Azure tags are case-insensitive for operations, but casing can be preserved. AWS tags are case-sensitive.
- Azure provides tag inheritance through policies. AWS doesn't natively support tag inheritance between parent and child resources. AWS does support tag inheritance for AWS Cost Categories.
- AWS provides a tag editor tool for adding tags, whereas Azure provides tagging capabilities via the Azure portal and management interfaces.
Contributors
This article is maintained by Microsoft. It was originally written by the following contributors.
Principal author:
- Srinivasaro Thumala | Senior Customer Engineer
Other contributor:
- Adam Cerini | Director, Partner Technology Strategist
To see non-public LinkedIn profiles, sign in to LinkedIn.