<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8211560\x26blogName\x3dTech+Tips,+Tricks+%26+Trivia\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://mvark.blogspot.com/search\x26blogLocale\x3den\x26v\x3d2\x26homepageUrl\x3dhttp://mvark.blogspot.com/\x26vt\x3d-5147029996388199615', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Tech Tips, Tricks & Trivia

by 'Anil' Radhakrishna
An architect's notes, experiments, discoveries and annotated bookmarks.

Search from over a hundred HOW TO articles, Tips and Tricks


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 one of the biggest, and most complex Single Page Applications (SPA) in the world.

This Azure portal availability chart shows Services which are available exclusively in one of the portals.

Bruno Terkaly has published detailed articles with screenshots on both the old & new portals.

Microsoft Azure management portal terms (from the Microsoft Press book, Programming Microsoft Azure Service Fabric)  -
As you click links in the portal, the display areas that expand to the right are called blades. You
also may see the following terms used in talks and articles:

* Hub - A hub gathers and displays information from multiple data sources. For instance, all
notifications from different services are displayed in a centralized notification hub, which
can be brought up by the Bell icon on the top command bar.

* Dashboard - The home page after you log in is called a dashboard, where you can pin various
types of resources for quick access.

* Tile - Each item you pin on the dashboard is represented by a tile.

* Journey - As you go through a workflow, your navigation steps are recorded as a journey.
You can see the history of your journey at the top of the page, and you can click any of the
steps to track back or to jump ahead. Journeys are recorded automatically, and you can access
previous journeys by clicking the down arrow icon beside the Microsoft Azure label

Labels: , ,

Tweet this | Google+ it | Share on FB

« Home | Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »

»

Post a Comment