Articles on Azure Portal
Azure originally provided only the classic deployment model or the Service Management model in which each resource existed independently; there was no way to group related resources together. To deploy a solution, you had to either create each resource individually through the Classic Portal or create a script that deployed all the resources in the correct order. In 2014, Azure introduced Resource Manager, which added the concept of a resource group. A resource group is a container for resources that share a common lifecycle. For Compute, Storage, and Networking resources, you have the option of using either Resource Manager or Classic deployment in the Azure Portal which was initially referred as Preview Portal. In December 2015, portal.azure.com (codename Ibiza), achieved general availability (GA) status and is the default portal for Azure. Microsoft guidance for new deployments is to make use of the Azure Resource Manager (ARM) model The Azure Portal is on...