Stage

Instructions/CloudLabs.AI/01-Create a virtual machine.md

@@ -6,28 +6,29 @@ In this walkthrough, we will create a virtual machine in the Azure portal, conne
 
 # Task 1: Create the virtual machine
 
-In this task, we will create a Windows Server 2019 Datacenter - Gen1 virtual machine. 
+In this task, we will create a Windows Server 2019 Datacenter - Gen2 virtual machine. 
 
 1. Click on the Azure Portal icon on the VM desktop and login with the Azure credentials from the Lab Environment output page.
 
-2. From the **All services** blade, search for and select **Virtual machines**, and then click **+ Add** and choose **+Virtual machine**.
+2. From the **Search resources, Services, and docs(G+/)** blade, search for and select **Virtual machines**, and then click **+ Create** and choose **Azure virtual machine**.
 
 3. On the **Basics** tab, fill in the following information (leave the defaults for everything else):
 
     | Settings | Values |
     |  -- | -- |
     | Subscription | **Choose your subscription**|
-    | Resource group | **myRGVM-[DeploymentId]** (use existing) |
+    | Resource group | **myRGVM-<inject key="DeploymentID" enableCopy="false"/>** (use existing) |
     | Virtual machine name | **myVm** |
     | Location | **(US) East US**|
-    | Image | **Windows Server 2019 Datacenter - Gen1**|
+    | Image | **Windows Server 2019 Datacenter - Gen2**|
     | Size | **Standard_D2s_v3**|
     | Administrator account username | **azureuser** |
     | Administrator account password | **Pa$$w0rd1234**|
-    | Inbound port rules - Allow select ports | **RDP (3389)** and **HTTP (80)**|
+    | Inbound port rules  | **Allow select ports**|
+    | Select inbound ports | **RDP (3389)** and **HTTP (80)**|
     | | |
 
-> Note: Deployment ID can be obtained from the Lab Environment output page.
+   > **Note** : DeploymentID can be obtained from the Lab Environment output page.
 
 4. Switch to the Networking tab, and look for the **Select inbound ports**:
 
@@ -38,7 +39,7 @@ In this task, we will create a Windows Server 2019 Datacenter - Gen1 virtual mac
 
     **Note** - Verify that both port 80 and 3389 are selected
 
-5. Switch to the Management tab, and in its **Monitoring** section, select the following setting:
+5. Switch to the **Monitoring** tab, select the following setting:
 
     | Settings | Values |
     | -- | -- |
@@ -51,64 +52,98 @@ In this task, we will create a Windows Server 2019 Datacenter - Gen1 virtual mac
 
 8. You will receive updates on the deployment page and via the **Notifications** area (the bell icon in the top menu).
 
-* **Verify Port 80 and 3389 were opened**
 
 # Task 2: Connect to the virtual machine
 
 In this task, we will connect to our new virtual machine using RDP. 
 
-1. Search for **myVM** and select your new virtual machine.
+1. Search for **myVm** and select your new virtual machine.
 
     **Note**: You could also use the **Go to resource** link on the deployment page or the link to the resource in the **Notification** area.
 
-2. On the virtual machine **Overview** blade, click the **Connect** button and choose **RDP**.
+2. On the virtual machine **Overview** blade, click the **Connect** button and choose the **RDP** tab.
 
-    ![Screenshot of the virtual machine properties with the Connect button highlighted.](../images/0101.png)
+    ![Screenshot of the virtual machine properties with the Connect button highlighted.](../images/01-01.png)
 
     **Note**: The following directions tell you how to connect to your VM from a Windows computer. On a Mac, you need an RDP client such as this Remote Desktop Client from the Mac App Store and on a Linux computer you can use an open source RDP client.
 
-2. In the **Connect to virtual machine** page, keep the default options to connect with the public IP address over port 3389 and click **Download RDP File**.
+3. Within the **Connect with RDP** section of the RDP tab, keep the default options to connect with the public IP address over port 3389 and click **Download RDP File**.
 
-3. **Open** the downloaded RDP file and click **Connect** when prompted. 
+4. **Open** the downloaded RDP file and click **Connect** when prompted. 
 
     ![Screenshot of the virtual machine properties with the Connect button highlighted. ](../images/0102.png)
 
-4. In the **Windows Security** window, select **More choices** and then **Use a different account**. Provide the username (.\azureuser) and the password (Pa$$w0rd1234). Click **OK** to connect.
+5. In the **Windows Security** window, select **More choices** and then **Use a different account**. Provide the username (.\azureuser) and the password (Pa$$w0rd1234). Click **OK** to connect.
 
     ![Screenshot of the Windows security dialogue with use a different account selected and the username azure user entered and a password.](../images/0103.png)
 
-5. You may receive a certificate warning during the sign-in process. Click **Yes** or to create the connection and connect to your deployed VM. You should connect successfully.
+6. You may receive a certificate warning during the sign-in process. Click **Yes** or to create the connection and connect to your deployed VM. You should connect successfully.
 
     ![Screenshot of the Certificate warning dialogue informing the user of an untrusted certificate, with the Yes button highlighted. ](../images/0104.png)
 
 Congratulations! You have deployed and connected to a Windows Server virtual machine in Azure
 
-# Task 3: Install the web server role and test
+# Task 3: Host a Basic Website on your New Cloud VM
 
-In this task, install the Web Server role on the server and ensure the default IIS welcome page can be displayed.
+In this task, install the Web Server role on the server and host a basic website.
 
-1. Open up a PowerShell command prompt on the virtual machine, by clicking the **Start** button, typing **PowerShell**, right clicking **Windows PowerShell**, and selecting **Run as administrator** in the right-click menu.
+1. In the Server Manager (which should launch automatically) once you connect to the vm, select **Add roles and features** as shown below in the screenshot: 
 
-    ![Screenshot of the virtual machine desktop with the start button clicked and PowerShell selected with run as an administrator highlighted.](../images/0105.png)
+    ![server manager](../images/az900-t3_s1.png)
 
-2. Install the **Web-Server** feature in the virtual machine by running the following command in the PowerShell command prompt. You can copy and paste this command.
+2. Within the **Add Roles and Features Wizard** dialog box, click on **Next**.
 
-    ```
-    Install-WindowsFeature -name Web-Server -IncludeManagementTools
-    ```    
-
-3. When completed there will be a prompt stating **Success** with a value **True**. You do not need to restart the virtual machine to complete the installation. Close the RDP connection to the VM.
+3. Ensure **Role-based or feature-based installation** is selected. Click Next.
+
+4. Ensure **Select a server from the server pool** is selected, and that your VM appears in the list below. Click on **Next**.
+
+5. In the Server roles list, scroll to near bottom of the list and check **Web Server (IIS)**. Click on **Add Features**.
+
+    ![server pool](../images/az900-t3_s5.png)
+
+6. Click on **Next** until you reach the **Confirm installation selections** page and make sure **Restart the destination server automatically if required** is checked. Then click on **Install**.
+
+    ![Restart the destination check box](../images/az900-t3_s7.png)
+
+    >**Note**: If a pop-up appears warning about the automatic server restart, select **Yes**.
+
+7. When the installation completes, back on the server manager portal, go to **Tools** > **Internet Information Services (IIS) Manager**.
 
-    ![Screenshot of the windows PowerShell command prompt with the command Install-WindowsFeature -name Web-Server -IncludeManagementTools successfully completed and output stating it was successful.](../images/0106.png)
+    ![](../images/az900-t3_s9.png)
+
+8. In the Internet Information Services (IIS) Manager window, locate your server’s Default Web Site in the Connections tree.
+
+    ![](../images/az900-t3_s10.png)
+
+9. Now, click on **Basic Settings** in the **Actions** menu. In the new pop-up dialog box, locate the **Physical Path**. This is where you'll put your website html file.
+
+    ![](../images/az900-t3_s12.png)
+
+10. Create a very basic html file. Save it as **Default.htm** and place it in the Physical Path location specified in the Basic Settings. For example:
+
+    ```
+    <html>
+    <body>
+        <h1>Demo Website</h1>
+        <p>This is my first cloud hosted website.</p>
+    </body>
+    </html>
+    ```
 
-4. Back in the portal, navigate back to the **Overview** blade of myVM and, use the **Click to clipboard** button to copy the public IP address of myVM, open a new browser tab, paste the public IP address into the URL text box, and press the **Enter** key to browse to it.
+11. Now back in the Azure portal, navigate back to the Overview blade of myVM and use the Copy to clipboard button to copy the public IP address of myVm.
 
-    ![Screenshot of the Azure portal virtual machine property pane with the IP address copied.](../images/0107.png)
+    ![](../images/az900-t3_vm_pip.png)
 
-5. The default IIS Web Server welcome page will open.
+12. Open a new browser tab, paste the public IP address into the URL text box, and press the Enter key to browse to it. The custom created basic website shows up.
 
-    ![Screenshot of the default IIS web server welcome page being accessed via the public ip address in a web browser.](../images/0108.png)
+    ![](../images/az900-t3_last.png)
 
-Congratulations! You have created a web server that is accessible via its public IP address. If you had a web application to host, you could deploy application files to the virtual machine and host them for public access on the deployed virtual machine.
+    > - **Congratulations** on completing the task! Now, it's time to validate it. Here are the steps:
+    > - Click the (...) icon located at the upper right corner of the lab guide section and navigate to the Lab Validation Page.
+    > - Hit the Validate button for the corresponding task.If you receive a success message, you can proceed to the next task. 
+    > - If not, carefully read the error message and retry the step, following the instructions in the lab guide.
+    > - If you need any assistance, please contact us at [email protected]. We are available 24/7 to help you out.
 
+13. Select the **Resources** tab, then in actions select deallocate for deallocate the VM, it will be Cost effective.
 
+You have successfully completed this lab.

Instructions/CloudLabs.AI/02-Create a Web App.md

@@ -1,62 +1,69 @@
 # 02 - Create a Web App
 
-In this walkthrough, we will create a new web app that runs a Docker container. The container displays a Welcome message. 
+In this walkthrough, we will create a new web app that runs a Docker container. The container displays a Welcome message.
 
 # Task 1: Create a Web App
 
 Azure App Service is actually a collection of four services, all of which are built to help you host and run web applications. The four services (Web Apps, Mobile Apps, API Apps, and Logic Apps) look different, but in the end they all operate in very similar ways. Web Apps are the most commonly used of the four services, and this is the service that we will be using in this lab.
 
-In this task, you will create an Azure App Service Web App. 
+In this task, you will create an Azure App Service Web App.
 
-1. Click on the Azure Portal icon on the VM desktop and login with the Azure credentials from the Lab Environment output page. 
+1. Click on the Azure Portal icon on the VM desktop and login with the Azure credentials from the Lab Environment output page.
 
-2. From the **All services** blade, search for and select **App Services**, and click **+ New**
+2. From the **Search resources, Services, and docs(G+/)** blade, search for and select **App Services**, and click **+ Create**
 
-3. On the **Basics** tab of the **Web App** blade, specify the following settings (replace **xxxx** in the name of the web app with the Deployment ID). Leave the defaults for everything else, including the App Service Plan. 
+3. On the **Basics** tab of the **Create Web App** blade.
+
+    **Note:**  **DeploymentId** can be obtained from the Lab Environment output page.
 
     | Setting | Value |
     | -- | -- |
     | Subscription | **Choose your subscription** |
-    | Resource Group | **myRGWebApp1-[DeploymentId]** (use existing) |
-    | Name | **myDockerWebAppxxxx** |
+    | Resource Group | **myRGWebApp1-<inject key="DeploymentID" enableCopy="false"/>** (use existing) |
+    | Name | **myDockerWebApp<inject key="DeploymentID" enableCopy="false"/>** |
     | Publish | **Docker Container** |
     | Operating System | **Linux** |
     | Region | **East US** (ignore any service plan availability warnings) |
-    | | |	
+    | | |
 
-    **Note** - Remember to change the **xxxx** so that it makes a unique **Name**. Deployment ID can be obtained from the Lab Environment output page.
 
-4. Click **Next > Docker** and configure the container information. The startup command is optional and not needed in this exercise. 
+4. Click **Next > Docker** and configure the container information. The startup command is optional and not needed in this exercise.
 
-    **Note:** This is same container that was used in the Container Instances walkthrough to display a hello world message. 
+    **Note:** This is same container that was used in the Container Instances walkthrough to display a hello world message.
 
     | Setting | Value |
     | -- | -- |
     | Options | **Single container** |
     | Image Source | **Docker Hub** |
     | Access Type | **Public** |
-    | Image and tag | **microsoft/aci-helloworld** |
-    | | |	
-
+    | Image and tag | **mcr.microsoft.com/azuredocs/aci-helloworld** |
+    | | |
 
-5. Click **Review + create**, and then click **Create**. 
+5. Click **Review + create**, and then click **Create**.
 
 # Task 2: Test the Web App
 
 In this task, we will test the web app.
 
 1. Wait for the Web App to deploy.
 
-2. From **Notifications** click **Go to resource**. 
+2. From **Notifications** click **Go to resource**.
 
-3. On the **Overview** blade, locate the **URL** entry. 
+3. On the **Overview** blade, locate the **Default Domain** entry.
 
-    ![Screenshot of the web app properties blade. The URL is highlighted.](../images/0801.png)
+    ![Screenshot of the web app properties blade. The URL is highlighted.](../images/AZ-900-module-02-app-service.png)
 
 4. Click on the **URL** to open the new browser tab and display the Welcome to Azure Container Instances page.
 
     ![Screenshot of the Welcome to Azure Container Instance page.](../images/0802.png)
 
-5. Switch back to the **Overview** blade of your web app and note that it includes several charts. If you repeat step 4 a few times, you should be able to see correspoding telemetry being displayed in the charts. This includes number of requests and average response time. 
+5. Switch back to the **Overview** blade of your web app and note that it includes several charts. If you repeat step 4 a few times, you should be able to see correspoding telemetry being displayed in the charts. This includes number of requests and average response time.
+
 
+  > **Congratulations** on completing the task! Now, it's time to validate it. Here are the steps:
+  > - Click the (...) icon located at the upper right corner of the lab guide section and navigate to the Lab Validation Page.
+  > - Hit the Validate button for the corresponding task.If you receive a success message, you can proceed to the next task. 
+  > - If not, carefully read the error message and retry the step, following the instructions in the lab guide.
+  > - If you need any assistance, please contact us at [email protected]. We are available 24/7 to help you out.
 
+6. Select the **Resources** tab, then in actions select deallocate for deallocated the VM, it will be Cost effective.