Note
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.
In any cloud migration journey, organizing and understanding your on-premises environment is critical. Azure Migrate provides tagging capabilities that help you group, organize, and analyze discovered workloads based on business and technical attributes.
Tags in Azure Migrate let you apply key value metadata to servers and workloads so you can manage large inventories more effectively, scope assessments, and plan migrations aligned to business priorities.
This article provides a high-level overview of tagging in Azure Migrate and links to detailed guidance for common tagging scenarios and tasks.
What are tags in Azure Migrate?
Tags are custom key value pairs that you assign to discovered workloads in Azure Migrate. You can use tags to group workloads based on attributes such as:
- Application or service
- Department or cost center
- Environment (production, test, development)
- Business criticality
- After tags are applied, you can use them across Azure Migrate experiences to filter inventory, scope assessments, and generate reports.
Why use tags during migration?
Using tags helps you:
- Organize large inventories by grouping related workloads
- Improve visibility into applications, environments, and ownership
- Simplify migration planning by scoping assessments and reports
- Align technical data with business context, such as departments or priorities
- Tags are especially useful when managing complex environments with multiple applications, business units, or migration waves.
Types of Tags
Azure Migrate supports two types of tags:
Reserved tags: Environment and Migration Intent. These tags add operational and migration context to workloads and applications. They affect cost modeling, SKU recommendations, assessment scoping, and wave planning.
Custom tags: User-defined key-value pairs that help organize workloads and applications by attributes such as department, cost center, owner, or compliance. Custom tags support filtering, scoping, chargebacks, and reporting, but they don’t affect cost modeling or sizing.