There have been a few incarnations of the Microsoft Azure Management Portal over the years. The current state is a fairly easy to use Web Application that is built as a Single Page Application (SPA). But, why is the Azure Portal a Web App instead of a Universal Windows Platform (UWP) app distributed through the Windows Store? Why isn’t it a native app in all the popular App Stores? This post digs into the specifics of why the Azure Portal is a Web App, as well as explains a few of the benefits and trade-offs of being a Web App. Read More
In the early days of Microsoft Azure the Portal was the primary tool to go in and configure your cloud components. After some time the Azure Service Manager API’s were introduced as a set of both PowerShell and Command-Line tools (X-Plat CLI). These tools allowed for Azure Automation to be scripted, however they were still a bit cumbersome as they were procedural based. More recently Microsoft overhauled the entire Azure Portal that exists today as well as a brand new set of Azure Resource Manager API’s. The purpose of Azure Resource Manager is more than just replacing Azure Service Manager. It’s real purpose is a story about automation and DevOps. Read More
The Azure Portal duality has been a source of confusion for many almost since the original launch of Microsoft Azure. There’s been 2 separate portals for a really long time. Recently, they’ve been renamed the “Current Azure Portal” and the “Classic Azure Portal”. However, neither portal has the same Azure feature support. This makes for a bit of confusion until you learn what can be managed from which portal.
Thankfully to make things much easier than pure discovery, Microsoft has an Azure portal availability chart. Like much of the documentation on any product, things can get buried in the mass. So, I thought I’d bring this little nugget to light and draw some attention to it. Read More