Azure Cloud Shell’s browser-based model frees IT teams from installation headaches but presents some formatting and timeout issues that admins need to watch for.
While Azure management tools, such as a PowerShell module or the Azure command-line interface, can help admins control their resources, these locally installed systems have their downsides, including software dependences, potential configuration challenges and latency from having to reach an Azure data center that’s potentially thousands of miles away.
Azure Cloud Shell — a browser-based command-line tool — reduces these burdens. That said, it can also introduce its own set of challenges if admins aren’t careful.
Accessible via a browser, Azure Cloud Shell provides admins with either a PowerShell console, still in preview, or a Bash console. It has the same look and feel of a command-line interface and supports various libraries and tools, as well as Node.js and Linux shell interpreters.
Upon initial connection, as shown in Figure 1, Azure Cloud Shell brings up a Linux container in the background and opens either a Bash or PowerShell Core console. For first-time users, the service will create an associated Azure Storage account. Then, it uses Azure Files to mount a drive in the user’s shell of choice, which provides storage for profiles, scripts or any other kind of file…