Azure Basics 1
Azure Basics 1
Administration Tools
Azure provides 3 administration tools to choose from
1. The Azure Portal
2. The Azure CLI
3. Azure PowerShell
Azure Portal
● We can use the Azure GUI portal website (portal.azure.com) to create,
configure, and alter our
Azure subscription resources.
● We can locate the resource needed and execute any changes. We have wizards and tooltips
to
guide you through various administrative tasks.
● Please note that we cannot use the portal to perform repetitive tasks like creating 12 VMs
etc.
● We need to use other tools to avoid errors, and it will also be a time-consuming process to
do
on the portal.
The Azure portal can be divided into 3 sections.
1. Left — A list of resources and services to create and manage your Azure environment.
2. Center — A dashboard that you can tailor to meet your (Public or Private dashboards)
needs.
3. Top — A search bar to quickly find resources and services, a notification icon, access to a
web-based command line, and more.
(Source: Microsoft Docs)
● Let’s try to create a resource and see how to use the Portal. For example, let us create a
resource group called Whizlabs.
--Back to Index-- 3
● Click on the Burger menu on the left top and select Resource group and click on it. You
will get a new Panel.
(Source: Microsoft Documentation)
● Click on the +Create icon. On the new Panel, add the name of the resource group and
choose the desired location.
(Source: Microsoft Documentation)
● Click Next, and you will get a new panel to add Tags. Tags are helpful for accounting and
segregation but are not mandatory.
(Source: Microsoft Documentation)
● Click NEXT, and at this point, Azure will validate all the options chosen.
● If there is any error, it will put a red dot on the tab where the error occurred, and you will
need to go back to the tab and fix it before proceeding.
● If validation is passed, you would see the Validation passed with a green tick message. At
this point, you can click CREATE, and the resource will be created.
--Back to Index-- 4
● You can also click on “Download a template for automation” and download the template
and save it to the library additionally for future use.
(Source: Microsoft Documentation)
You will get a notification when the resource is created. You can also click the bell icon on Top
Right to view the notification.
(Source: Microsoft Documentation)
If we go back to the Resource Groups, we can see this new resource group. This is a simple
example of the usage of the Portal. We can use the portal for lots of activities.
We can use the Azure Portal for
● Creating/ Modifying/ Deleting resources
● Billing and accounting
● Help and Support – Contact Microsoft
● Online Help
● Health and Service Dashboards
● Microsoft Defender for Cloud
● Access Microsoft Entra and create applications
● Azure Monitor
● Access Documentation
● Azure Marketplace for third party products and solutions
● Access Cloudshell (On top right)
--Back to Index-- 5
Azure CLI
Azure CLI means → Azure Command Line
Interface. It’s a cross-platform command-line
program to connect and execute administrative commands on Azure resources.
Sample command:
az VM create --resource-group WLRG --name WLVM1 --image UbuntuLTS
Azure CLI can be accessed inside a browser via Cloud Shell or with a local install on
any OS like
Windows/Linux or MacOS and Docker. It can also work with multiple clouds.
Let’s see an example.
First, we invoke the MSI installer either in the command line or by downloading.
Here is the command line below:
Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi;
Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Then we sign in with the login command az login.
on any OS and then run the New-AzVM command that creates a virtual
machine in our
subscription as follows:
--Back to Index-- 7
Azure Resource Manager
● Azure Resource Manager provides a management layer to create, update, and
delete
resources in your Azure account.
● We use management features, like access control, locks, and tags, to secure
and
organize your resources after deployment.
● When a user sends a request from any of the tools, APIs, or SDKs, the Resource Manager
receives the request and authenticates/authorizes it.
● Then it sends to Azure services to take action. Since it acts as a central point, it leads to
consistent results.
(Source: Microsoft Documentation)
Benefits of Resource Manager:
● Declarative templates so we don’t have to worry about the current state.
● Allows group deployments
● Define dependencies so the correct order of deployment is done.
● Apply tags to organize resources logically
● Allows for redeployment and confidence that the same results will be achieved
● Applies access control via RBAC natively