If you work with Azure close enough, you’ve probably have heard of Nested Virtualization. Yes, it is the feature allowing you to run Hyper-V inside an Azure VM. Why does one need that thing? Well, to build a perfect lab for demos, development, testing, whatever… without buying any extra hardware!
VPN connections provide remote access to the necessary data and you can get information about your company’s assets at any time. The connection to Azure virtual networks is possible by configuring two types of VPN, namely Site-To-Site (S2S) and Point-To-Site (P2S). S2S VPN allows you to connect two networks and constantly maintain communication between them. P2S VPN is effective for connecting to a virtual network from a remote location if you have a small number of clients for whom such an access is needed. You’re asking how to establish a secure connection of individual clients running Windows 10 to the Azure Virtual Network?
In Windows 10 Fall Creator Update, Microsoft introduced a new feature called the “Hyper-V Quick Create Wizard” which is very useful because you can create a Virtual Machine with the default settings and save time. Using this feature, you can create a VM with a single ISO file located on your system, or you can create a VM from the Online Gallery. By default, Quick Create will list a Windows 10 Developer Environment but you can easily add your own Virtual Machine Images from your local/online repository.
In this article, I will describe how to use this feature and how to add a custom VM Image into your own Gallery.
ACI lets you create Linux or Windows Containers without the need to deploy a Container host, so in other words, ACI is serverless, and it works like a charm! So in this article, I will describe how to create a simple Container using Azure Container Instances (ACI). In the first part, I will describe ACI using the Azure Portal and the command line, and in the second part, I will describe Azure Container Registry.
In this article, I will describe how to manage Windows Containers via GUI. Docker provides a great Docker CLI that allows us to create, interact, and delete containers, but sometimes it’s nice to have an interface to manage Containers. There are many admins who much prefer a GUI tool to handle every task and it can be useful to use an interface when you have many containers to manage or if you start working with Docker. In this article, I don’t want to judge which GUI is better because it depends! You must use the GUI that will suit your needs. So do not hesitate to test this GUI.
In this article, I will not explain what is and what is not DevOps. I just want to describe how to implement a DevOps Project in your Azure subscription through the new service called “DevOps Projects”. This new service has been released in November 2017. The “DevOps Projects” service allows you to deploy and monitor your application in Azure. Visual Studio Team Services and Team Foundation Services are Microsoft’s DevOps solutions for Azure. I’m not a VS or TFS expert, but as you will see, implementing DevOps with Azure is very straightforward. Microsoft says that you can implement your project in less than 5 minutes! Let’s see if it’s true.
Official Microsoft description:
“Azure DevTest Lab is a service that helps developers and testers to quickly create environments in Azure while minimizing waste and controlling cost. You can test latest version of your application by quickly provisioning Windows and Linux environments using reusable templates and artifacts.”
In other words, Azure DevTest Labs is a great service that will help you to implement DevOps in your organization. Azure DevTest Labs will allows you to easily deploy Virtual Machines in order to test your workload in Azure. Setting up a development and test environment can take lots of time for your Ops Team.
You may need to move a couple of Azure Virtual Machines from on-premises to your Azure subscription. Thanks to Windows PowerShell, uploading a VM to Azure is really easy to do! You must check only one prerequisite before uploading your VM to Azure: you will need to check what type of virtual hard disk is being used by the virtual machine. Hyper-V can use either VHD or VHDX based virtual hard disks. However, only VHD disks can be uploaded to Azure. Azure does not support VHDX disks.
Microsoft has introduced Azure Cloud Shell, a new way of managing resources from the Azure Portal. Within a browser, you can use Bash to troubleshoot and automate your most common management tasks. Support for Windows PowerShell is expected soon. Azure Cloud Shell will help you to store your favorite scripts in the Cloud.