Azure portal
Slide deck explaining the Azure portal: web-based unified console for managing Azure through a GUI. Covers portal tasks, relationship with Azure Resource Manager (ARM), when to use portal vs CLI/PowerShell, access control via Entra ID and RBAC, and best practices.
Azure portal
Introduction to the Azure portal: web-based unified console for managing Azure through a Graphical User Interface (GUI).
Azure portal
Introduction to the Azure portal: web-based unified console for managing Azure through a Graphical User Interface (GUI).
What is the Azure portal?
A web-based, unified console for managing Azure through a Graphical User Interface (GUI). Browser-based interface (no local install). Unified place to work with Azure services. Graphical User Interface (GUI): click and navigate. It can trigger real changes to resources.
Common portal tasks
The portal is where you create, configure, monitor, and manage Azure resources. Create and configure resources. Organize with resource groups. Dashboards, health status, and metrics. Basic cost and usage views.
Portal vs Azure Resource Manager (ARM)
The portal sends management requests to Azure Resource Manager (ARM), which applies changes in Azure. Azure Resource Manager (ARM) equals management layer / control plane. Portal actions become ARM management requests. Create / update / delete happens through ARM. Portal equals interface, ARM equals management service.
Different tools, same management layer
Portal, Azure CLI, and Azure PowerShell often reach the same result via ARM. Azure Command-Line Interface (Azure CLI). Azure PowerShell. Representational State Transfer (REST) APIs. Software Development Kits (SDKs). Many actions ultimately go through ARM.
When the portal shines
Use the portal for interactive setup, discovery, and quick checks. Fast, guided setup (wizards and forms). Easy discovery of available options. Quick dashboards and status checks. Powerful, but not as repeatable as automation.
When to prefer Azure CLI / PowerShell
Prefer command-line and templates when you need repeatability and consistency. Repeat the same setup reliably. Apply changes across environments. Easier to review and track changes. Still uses Azure Resource Manager (ARM) underneath.
Portal vs subscription
A subscription is a billing and access boundary; the portal is just the interface. Subscription equals billing plus access boundary. Subscription contains resources. Portal equals interface to manage subscriptions/resources. Seeing something does not equal having control.
Access control in the portal
Access depends on Microsoft Entra ID (Entra ID) and Azure role-based access control (Azure RBAC). Microsoft Entra ID (Entra ID) equals identity. Azure role-based access control (Azure RBAC) equals permissions. Permissions are assigned at a scope. Scope examples: subscription, resource group, resource.
Portal access is real access
Portal permissions can change production resources, so least privilege matters. Clicks can create/modify/delete real resources. Broad roles increase risk (especially at subscription scope). Apply least privilege: minimum roles needed. Scope permissions carefully.
Recap
Portal equals interface; ARM equals control plane; access equals Entra ID plus Azure RBAC with least privilege. Azure portal equals web-based GUI to manage Azure. Many actions go through Azure Resource Manager (ARM). Portal does not equal subscription (billing plus access boundary). Access via Entra ID plus Azure RBAC; use least privilege.