Using the Azure Portal to deploy and manage your Azure resources
You can also manage resources through Azure PowerShell and Azure CLI. For more information about using those interfaces, see Using Azure PowerShell with Azure Resource Manager and Use the Azure CLI for Mac, Linux, and Windows with Azure Resource Manager. For more information about deploying solutions through Visual Studio, see Creating and deploying Azure resource groups through Visual Studio.
To create an empty resource group, select New, Management, and Resource Group.
Give it a name and location, and, if necessary, select a subscription.
After you create a resource group, you can deploy resources to it. To start a deployment, simply select New and the type of resource you would like to deploy.
If you do not see the type of resource you would like to deploy, you can search the marketplace for it.
Depending on the type of resource you have selected, you will have a collection of relevant properties to set before deployment. Those options are not shown here, as they vary based on resource type. For all types, you must select a destination resource group. The following image shows how to create a new web app and deploy it to the resource group you just created.
Alternatively, you can decide to create a new resource group when deploying your resources. Instead of selecting one of the existing resource groups in your subscription, select New and give the resource group a name.
Your deployment will begin. This could take a few minutes. When the deployment has finished, you will see a notification.
After deploying your resources, you may decide that you need to add more resources to the group. You can add resources to a resource group by using the Add command on the resource group blade.
After setting up your resource group, you may want to view the Resource Manager template for the resource group. Exporting the template offers two benefits:
You can easily automate future deployments of the solution because all of the infrastructure is defined in the template.
Through the portal, you can either generate a template that represents the current state of your resource group, or retrieve the template that was used for a particular deployment. Both options are shown in this topic.
Exporting the template for a resource group is helpful when you have made changes to a resource group, and need to retrieve the JSON representation of its current state. However, the generated template contains only a minimal number of parameters and no variables. Most of the values in the template are hard-coded. Before deploying the generated template, you may wish to convert more of the values into parameters so you can customize the deployment for different environments.
Exporting the template for a particular deployment is helpful when you need to view the actual template that was used to deploy resources. The template will include all of the parameters and variables defined for the original deployment. However, if someone in your organization has made changes to the resource group outside of what is defined in the template, this template will not represent the current state of the resource group.
The export template feature is in preview, and not all resource types currently support exporting a template. When attempting to export a template, you may see an error that states some resources were not exported. If needed, you can manually define these resources in your template after downloading it.
From the resource group blade, you can export the template that represents the current state of the resource group.
To view the template for a resource group, select Export template.
Resource Manager generates 4 files for you:
The template that defines the infrastructure for your solution
A parameter file that you can use to pass in values during deployment
An Azure PowerShell script file that you can execute to deploy the template
An Azure CLI script file that you can execute to deploy the template
First, look at the template that represents the current resource group.
Within the resources section, you will see the definitions for the resources to deploy.
In the parameters file, you can save parameter values to pass in during deployment.
There is a script file for deploying the template through Azure PowerShell.
And, a script file for deploying the template through Azure CLI.
The portal offers three options for working with this template. To re-deploy the template right now, select Deploy. To download all of the files locally, select Download. To save the files to your Azure account for later use through the portal, select Save template.
From within the resource group blade, you can see the date and status of the last deployment for this resource group. Selecting the link, displays a history of deployments for the group.
Selecting any deployment from the history shows details about that deployment. Every time you deploy resources, Resource Manager persists the template that you used. You can retrieve the actual template that was used for the deployment by selecting View template.
You will see the template used for this deployment. It contains all of the parameters and variables as you defined them.
As noted earlier, this might not be a complete representation of the resource group. If you added or deleted resources outside of this deployment, those actions are not reflected in the template. You can view the template, parameters file, and script files as shown in the previous section. You can also re-deploy, download, or save the template as shown in the previous section.
You can browse all resource groups by clicking Resource groups.
When you select a particular resource group, you see a resource group blade that gives you information about that resource group, including a list of all of the resources in the group.
You can add more graphs and tables to the resource group blade by selecting Add a section below the summary.
You are presented with a tile gallery to select the information you would like to include in the blade. The types of tiles that are displayed are filtered by the resource type. Selecting a different resource will change the available tiles.
Drag the tile you need into the available spaces.
After selecting Done at the top of the portal, your new view is part of the blade.
For quick access to a resource group, you can pin the blade to your dashboard.
Or, you can pin a section of the blade to your dashboard by selecting the ellipsis (...) above the section. You can also customize the size the section in the blade or remove it completely. The following image shows how to pin, customize, or remove the CPU and Memory section.
After pinning the section to the dashboard, you will see the summary on the dashboard.
And, selecting it immediately takes you to more details about the data.
Since resource groups allow you to manage the lifecycle of all the contained resources, deleting a resource group will delete all the resources contained within it. You can also delete individual resources within a resource group. You want to exercise caution when you are deleting a resource group because there might be resources in other resource groups that are linked to it. The linked resources will not be deleted but they may not operate as expected.
You can apply tags to resource groups and resources to logically organize your assets. For information about working with tags through the portal, see Using tags to organize your Azure resources.
If you saved a template to your account, you can view it later by select Browse and Templates.
You will see your own collection of templates.
If you want to execute a deployment but not use any of the templates in the Marketplace, you can create customized template that defines the infrastructure for your solution. For more information about templates, see Authoring Azure Resource Manager templates.
To deploy a customized template through the portal, select New, and start searching for Template Deployment until you can select it from the options.
Select Template Deployment from the available resources.
After launching the template deployment, you can create the custom template and set values for the deployment.
Or, you can select a pre-existing template from the Azure quickstart templates. These templates are contributed by the community. They cover many common scenarios, and someone may have added a template that is similar to what you are trying to deploy. You can search the templates to find something that matches your scenario.
After selecting a template, it is loaded in the editor.
You can view information about your subscription and the rolled-up costs for all of your resources. Select Subscriptions and the subscription you want to see. You might only have one subscription to select.
Within the subscription blade, you will see a burn rate.
And, a breakdown of costs by resource type.
Access to the information displayed by most tiles in the portal are governed by Azure Role Based Access Control. In order to seamlessly integrate dashboards into the ecosystem all published dashboards are implemented as Azure resources. From an access control perspective dashboards are no different from a virtual machine or a storage account.
Here is an example. Let's say you have an Azure subscription and various members of your team have been assigned the roles of owner, contributor, or reader of the subscription. Users who are owners or contributors will be able to list, view, create, modify, or delete dashboards within the subscription. Users who are readers will be able to list and view dashboards, but cannot modify or delete them. Users with reader access will be able to make local edits to a published dashboard (e.g. when troubleshooting an issue), but will not be given the option to publish those changes back to the server. They will have the option to make a private copy of the dashboard for themselves.
Note that the individual tiles on the dashboard will enforce their own access control requirements based on the resources they are showing data for. This means that you can design a dashboard that can be shared more broadly while still protecting the data on individual tiles.
- To view audit logs, see Audit operations with Resource Manager.
- To troubleshoot deployment errors, see Troubleshooting resource group deployments with Azure Portal.