Resource organization for HPC in the energy industry

To align with the Ready methodology of the Cloud Adoption Framework for Azure, implement a naming and tagging strategy that includes business and operational details as components of resource names and metadata tags.

Use Azure resource naming and tagging conventions

The business side of this strategy ensures that resource names and tags include the organizational information that you need to identify the associated teams. Include the business owners who are responsible for resource costs. The operational side ensures that names and tags include information that IT teams can use to identify the workload, application, environment, criticality, and other information that's useful for managing resources.

Resources to name include VMs, load balancers, DNS labels, availability sets, virtual networks, subnets, Azure ExpressRoute, NSGs, application security groups, tags, route tables, managed disks, and public IPs. For example, you could label all development VMs with the tag Dev. Doing so makes it easier to pull billing reports and other reports for development VMs. For more information, see Develop your naming and tagging strategy for Azure resources.

Next steps

The following articles provide guidance that you might find helpful at various points during your cloud adoption process. They can help you succeed in your cloud adoption scenario for HPC in the energy industry.

• Azure Billing and Microsoft Entra tenants for energy HPC
• Identity and access management for Azure HPC in energy
• Management for Azure HPC in energy
• Network topology and connectivity for Azure HPC in energy
• Platform automation and DevOps for Azure HPC in energy
• Governance for HPC in energy industries
• Security for Azure HPC in energy
• Compute large-scale HPC application workloads in Azure VMs
• Storage for HPC energy environments
• Azure high-performance computing (HPC) landing zone accelerator