Manage & organize Azure resources

organization of your Azure resources is much more than just being neat and tidy good organization helps you secure manage and track the costs of your Azure environment [Music] my name is Eric Boyd I'm an Azure MVP a Microsoft Regional director and the founder of responsivex where we help customers run workloads and develop applications in Azure in this video I'm going to show you how to organize your Azure environment I will explain the hierarchical strategies and I will show you how to use tags to organize resources into a taxonomy there are several organizational approaches you can take you will have to find the approach that works best for your organization and requirements when you create Azure resources they get created in resource groups resource groups are simply collections of azure resources you can almost think of it like a directory on your file system you can add various types of files to that directory name that directory control permissions to that directory and manage the life cycle of that directory Azure resource groups work similarly you can add multiple resources of multiple types to a resource Group resource groups and resources are created within an Azure subscription and you can have multiple Azure subscriptions too you can group and manage multiple subscriptions with management groups and to learn more about organizing your resources and subscriptions you will find additional guidance in this decision guide in the cloud adoption framework sometimes hierarchies aren't the ideal organizational tool and within a hierarchy you need to be able to segment and filter resources this is where tagging comes to the rescue tags can be applied to resources resource groups and subscriptions and they give you a way to organize them into a taxonomy in addition to the hierarchical organization you get with resource groups tags are simply name value Pairs and you can use them to add your own metadata to a resource and you can then search for resources with your tags for example you could use a tag to label a resources environment with values like development test or production you could use a tag to associate a department or cost center to a resource you could use a tag to indicate that a resource doesn't belong to a specific cost center but instead is a shared resource to learn more about naming and tagging your resources you can find additional guidance in this decision guide in the cloud adoption framework I'm going to browse to the Azure portal to quickly show you how you can organize your resources I'm going to browse my resource groups where you will find the resource groups named in a consistent way you might notice a couple of resources that don't follow my convention but those were automatically created by Azure for the network Watcher service and the Azure Cloud shell it's important for me to follow a consistent convention for naming and a convention that provides identifying information for each resource at a glance I typically like to structure the naming convention to include tokens that represent the resource type the workloader application the environment and the Azure region lastly I append an incrementing numerical value or a unique token in scenarios where I have the potential of having multiples I like to limit them with a hyphen where possible but not all resources can support hyphens in the name for example storage accounts don't allow for hyphens uppercase letters and several other characters and you need to be aware of constraints on the length of resource names for example virtual machine names can only have 15 characters so for certain resources you might deviate from your standard naming convention but I still recommend you are consistent with how you structure the names of all the resources of a given type notice I didn't prescribe the exact order of the items to include in the names of your resources because it's situational and often a personal preference based on your environment how you want to work with the resources and how you'd like them sorted I commonly structure the names with the resource type a hyphen the workload or application a hyphen the region a hyphen the environment another hyphen and then a counter but you'll find variations out there however I wouldn't encourage you to attempt to encode all the description descriptive information about a resource into the resource name this is where tags help while the name is useful and uniquely identifying the resource and naming conventions help you find resources in your subscription they aren't easy to search without parsing the names of resources with tools like grep and tags are searchable you'll see that the information encoded in my naming convention are also expressed as tags because I can easily search and group resources using the tags I can also add additional information with the tags without being concerned with the limits of size and allowed characters in the resource name in my tags you'll see additional information associated with a resource as well as the information included in the names of the resources as shown here now when I browse my resources I can add filters on the properties of the resource including the resources tags in the next video of this series I will provide an overview of the Azure Global infrastructure and help you determine which regions are best for your workloads before I wrap up I'd like to invite you to join me at our weekly Azure live q a session during the 30 minute session I will host an interactive and live q a to answer your Azure questions [Music] foreign

Channel: Microsoft Azure Developers

Views: 5,873

Keywords: Azure, Functions, Serverless, Computing, azure app service, azure developers, azure dev cli, azure functions

Id: OEdZGF1JcEI

Length: 5min 37sec (337 seconds)

Published: Thu May 25 2023