We deploy the real environment, you take the scenario-based labs on us. Hands-on, from anywhere, at any time.
In this lab, you will apply Network Security Group (NSG) rules to a subnet containing a virtual machine running nginx. You will see how a predefined rule that blocks inbound traffic prevents internet connections to that VM, how adding a rule with a smaller priority number allows public connections, how the statefulness of NSG-controlled connections affects the processing of inbound and outbound rules, and how reordering inbound rule priorities affects connectivity.
This lab allows you to use social media logins with Web Apps, via the built-in App Service authentication/authorization provider. You will create a Facebook application for authentication, configure the Web App to use that application, and see the information provided to your Web App via Facebook once a user logs in.
In this lab, you will use Windows PowerShell cmdlets to create an Azure virtual network, a public IP address, a network security rule and network security group, a network interface, and finally, an Ubuntu VM. Then, you'll use PuTTY to connect to that VM, validating its correct configuration.
This lab will show you how a load balancer manages web traffic between two Linux virtual machines running Ubuntu and Apache. Specifically, you'll review the settings for the load balancer, see how traffic is routed between the machines, see what happens when each VM is stopped, and see how port forwarding through the load balancer allows you to SSH into each VM on the same public IP address.
In this lab, you will use Windows PowerShell cmdlets to create an Azure virtual network, a public IP address, a network security rule and network security group, a network interface, and finally, an Ubuntu VM. Then, you'll use PuTTY to connect to that VM, validating its correct configuration
This lab will guide you through the process of understanding, linting, validating, and executing an ARM template and its affiliated parameters file using the Azure CLI 2.0. You will first inspect the template and its parameter file to understand what it will deploy; then fix technical problems with both the ARM template and the parameters file; execute the ARM template; then see the template's results in the portal.