Merge pull request #53953 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-24 17:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -38640,6 +38640,16 @@
       "source_path": "learn-pr/iot/introduction-to-aks-edge-essentials/3-how-aks-edge-essentials-works.yml",
       "redirect_url": "/training/",
       "redirect_document_id": false
+    },
+     {
+      "source_path": "learn-pr/wwl-azure/describe-cost-management-azure/4-exercise-estimate-workload-costs-use-pricing-calculator.md",
+      "redirect_url": "https://learn.microsoft.com/training/modules/describe-cost-management-azure/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/wwl-azure/describe-features-tools-azure-for-governance-compliance/5-exercise-configure-resource-lock.md",
+      "redirect_url": "https://learn.microsoft.com/training/modules/describe-features-tools-azure-for-governance-compliance/",
+      "redirect_document_id": false
     },
     {
       "source_path": "learn-pr/iot/introduction-to-aks-edge-essentials/4-when-to-use-aks-edge-essentials.yml",
@@ -65050,6 +65060,46 @@
       "source_path": "learn-pr/paths/secure-your-cloud-apps/index.yml",
       "redirect_url": "/azure/security",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/index.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/1-introduction.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/2-routing-traffic-with-application-gateway.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/3-exercise-create-web-sites.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/4-create-configure-application-gateway.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/5-exercise-create-configure-application-gateway.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/6-exercise-test-application-gateway.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "learn-pr/azure/load-balance-web-traffic-with-application-gateway/7-summary.yml",
+      "redirect_url": "/azure/application-gateway/",
+      "redirect_document_id": false
     }
   ]
 }

learn-pr/achievements.yml

@@ -7895,3 +7895,8 @@ achievements:
   title: Secure your cloud applications in Azure
   summary: "Learn how to secure your Azure apps and associated data with encryption, certificates, and policy. This learning path can help you prepare for the [Microsoft Certified: Azure Security Engineer Associate certification](/certifications/azure-security-engineer)."
   iconUrl: /training/achievements/secure-your-cloud-apps.svg
+- uid: learn.load-balance-web-traffic-with-application-gateway.badge
+  type: badge
+  title: Load balance your web service traffic with Application Gateway
+  summary: Improve application resilience by distributing load across multiple servers and use path-based routing to direct web traffic.
+  iconUrl: /training/achievements/load-balance-web-traffic-with-application-gateway.svg

learn-pr/achievements/learn.load-balance-web-traffic-with-application-gateway.badge.yml

@@ -0,0 +1,13 @@
+### YamlMime:ModuleUnit
+uid: learn.devrel.deploy-configure-internet-information-services.introduction-internet-information-windows-server
+title: Introduction to Internet Information Services on Windows Server
+metadata:
+  title: Introduction to Internet Information Services on Windows Server
+  description: In this unit, you'll be introduced to Internet Information Services (IIS) on Windows Server. You learn about the architecture of IIS, its components, and the benefits of using IIS as a web server for hosting websites and web applications.
+  ms.date: 03/23/2026
+  author: Orin-Thomas
+  ms.author: orthomas
+  ms.topic: unit
+durationInMinutes: 4
+content: |
+  [!include[](includes/1-introduction-internet-information-windows-server.md)]

learn-pr/advocates/deploy-configure-internet-information-services/1-introduction-internet-information-windows-server.yml

@@ -0,0 +1,13 @@
+### YamlMime:ModuleUnit
+uid: learn.devrel.deploy-configure-internet-information-services.install-web-server-role
+title: Installing the Internet Information Services web server role
+metadata:
+  title: Installing the Internet Information Services Web Server role
+  description: Learn how to install the Internet Information Services (IIS) web server role on Windows Server using both the graphical user interface (GUI) and PowerShell command-line interface.
+  ms.date: 03/23/2026
+  author: Orin-Thomas
+  ms.author: orthomas
+  ms.topic: unit
+durationInMinutes: 5
+content: |
+  [!include[](includes/2-install-web-server-role.md)]

learn-pr/advocates/deploy-configure-internet-information-services/2-install-web-server-role.yml

@@ -0,0 +1,13 @@
+### YamlMime:ModuleUnit
+uid: learn.devrel.deploy-configure-internet-information-services.initial-configure-validate
+title: Initial configuration and validation
+metadata:
+  title: Initial Configuration and Validation
+  description: In this unit, you perform the initial configuration of your web server and validate that the installation was successful. You learn how to use the IIS Manager console to perform basic configuration tasks, such as creating a new website and configuring its settings.
+  ms.date: 03/23/2026
+  author: Orin-Thomas
+  ms.author: orthomas
+  ms.topic: unit
+durationInMinutes: 7
+content: |
+  [!include[](includes/3-initial-configure-validate.md)]

learn-pr/advocates/deploy-configure-internet-information-services/3-initial-configure-validate.yml

@@ -0,0 +1,54 @@
+### YamlMime:ModuleUnit
+uid: learn.devrel.deploy-configure-internet-information-services.knowledge-check
+title: Knowledge check
+metadata:
+  title: Knowledge Check
+  description: Check your knowledge.
+  ms.date: 03/23/2026
+  author: Orin-Thomas
+  ms.author: orthomas
+  ms.topic: unit
+durationInMinutes: 3
+content: |
+quiz:
+  title: Check your knowledge
+  questions:
+    - content: Where is the content root of the Default Web Site on a new IIS installation?
+      choices:
+        - content: C:\wwwroot\
+          isCorrect: false
+          explanation: Incorrect. This path doesn't exist by default; the correct path includes the "inetpub" directory.
+        - content: C:\inetpub\wwwroot\
+          isCorrect: true
+          explanation: Correct! The Default Web Site's content root is C:\inetpub\wwwroot, where the default welcome file iisstart.htm is located.
+        - content: "%SystemDrive%\\Web\\Default Site\\"
+          isCorrect: false
+          explanation: Incorrect. This is not a valid default IIS path.
+        - content: C:\Program Files\IIS\Default\
+          isCorrect: false
+          explanation: Incorrect. IIS doesn't store website content under Program Files.
+    - content: Which of the following is one of the default document file names for IIS?
+      choices:
+        - content: Default.js
+          isCorrect: false
+          explanation: Incorrect. Default.js isn't in the IIS default document list.
+        - content: index.md
+          isCorrect: false
+          explanation: Incorrect. index.md isn't in the IIS default document list.
+        - content: home.aspx
+          isCorrect: false
+          explanation: Incorrect. home.aspx isn't in the default IIS document list.
+        - content: iisstart.htm
+          isCorrect: true
+          explanation: Correct! iisstart.htm is in the IIS default document list.
+    - content: Which firewall port must be open to allow users to access a website on HTTP, and which additional port is needed for HTTPS?
+      choices:
+        - content: Port 80 for HTTP, and port 443 for HTTPS
+          isCorrect: true
+          explanation: Correct! Port 80 is the standard HTTP port; port 443 is the standard HTTPS port. Both must be open for users to access IIS-hosted websites.
+        - content: Port 443 for HTTP, and port 80 for HTTPS
+          isCorrect: false
+          explanation: Incorrect. These are reversed. Port 80 is HTTP, port 443 is HTTPS.
+        - content: Port 25 for HTTP, and port 110 for HTTPS
+          isCorrect: false
+          explanation: Incorrect. Port 25 is SMTP email; port 110 is POP3 email. Neither is used for web hosting.

learn-pr/advocates/deploy-configure-internet-information-services/4-knowledge-check.yml

@@ -0,0 +1,13 @@
+### YamlMime:ModuleUnit
+uid: learn.devrel.deploy-configure-internet-information-services.summary
+title: Summary
+metadata:
+  title: Summary
+  description: Module summary and key takeaways.
+  ms.date: 03/23/2026
+  author: Orin-Thomas
+  ms.author: orthomas
+  ms.topic: unit
+durationInMinutes: 2
+content: |
+  [!include[](includes/5-summary.md)]

learn-pr/advocates/deploy-configure-internet-information-services/5-summary.yml

@@ -0,0 +1,17 @@
+Windows Server includes IIS (Internet Information Services) version 10.0 as the built-in web server role. IIS isn't installed by default in a fresh Windows Server 2025 installation. You can add it via Server Manager or PowerShell. IIS 10 is available in all supported versions of Windows Server and Windows Client.
+
+IIS uses a modular hierarchical architecture. The main architectural components are:
+
+- **Web Sites**. Top-level containers that represent individual websites hosted on the server. Each site is identified by a unique combination of host name, port, and IP address and has its own folder path for content. By default, when IIS is installed, it creates a "Default Web Site", which listens on HTTP port 80 and serves content the %SystemDrive%\inetpub\wwwroot folder.
+- **Applications**. An application in IIS is a subset of a site that runs as a distinct unit. Applications are configured starting at a virtual directory and have their own settings or even a separate application pool. For example, under one site you might have a "/Blog" application that has its own configuration or credentials. 
+- **Virtual Directories**. A virtual directory is a logical directory name within a site or application that maps to a physical folder on disk. This folder can be outside the site's root folder. Virtual directories let you publish content or files in IIS from different file system locations under a single site structure. They appear as normal subfolders to users. 
+- **Application Pools**. An application pool is the worker process environment in which one or more sites/applications run. Application pools provide isolation—each pool runs in its own sandboxed worker process named w3wp.exe. This means that problems in one site won't impact other sites hosted on the same server. By default, IIS puts the "Default Web Site" into a default application pool (DefaultAppPool). You should create additional application pools to isolate different applications or sites. Key settings of app pools include the .NET CLR version for ASP.NET apps, pipeline mode, and various recycling settings for stability. Each website in IIS can be assigned to a different application pool.
+- **Modules**. Modules are components that handle specific request-processing tasks including authentication, compression, and URL rewriting. IIS's modular architecture means you can add or remove modules depending on the features you need.
+
+These components function as follows:
+
+1. When a request arrives, IIS determines which site it's for by matching the host header, port, and IP to a site binding. 
+1. Within that site, it looks at the URL path to see if it corresponds to an application or virtual directory with distinct settings, then maps the request to a physical folder. 
+1. The request is executed using the application pool associated with that site/application, which loads the necessary modules to handle things like authentication, authorization, serving content or executing application code, and sending the response.
+
+[![A diagram showing IIS architecture functions with incoming requests.](../media/internet-information-services-architecture.png)](../media/internet-information-services-architecture.png#lightbox)

learn-pr/advocates/deploy-configure-internet-information-services/includes/1-introduction-internet-information-windows-server.md

@@ -0,0 +1,61 @@
+On a computer configured as Windows Server 2025 with Desktop Experience, you can install IIS using the Add Roles and Features Wizard:
+
+1. In Server Manager's dashboard, select "Add Roles and Features." This opens the Add Roles and Features Wizard.
+1. In the wizard's Before you begin page, select Next. Choose "Role-based or feature-based installation," then select your server. Continue to the Server Roles step.
+1. In the list of roles, find and check "Web Server (IIS)". If this is the first time installing IIS, a pop-up appears to add associated features. Select "Add Features" when prompted to include IIS Management Console and other required components. After that, the "Web Server (IIS)" role should be checked.
+[![A screenshot showing selection of the Web Server role.](../media/server-manager-install.png)](../media/server-manager-install.png#lightbox)
+1. Select Next to go through features until you reach the Role Services page. This list displays subcomponents like Common HTTP Features, Security, and Performance. By default, essential services are preselected. You can optionally select additional services or add them later as required. [![A screenshot showing selection Web Server role services.](../media/server-manager-roles.png)](../media/server-manager-roles.png#lightbox)
+1. Complete the wizard and then select Install on the confirmation page. The installation proceeds and when it completes, you'll see an "Installation succeeded" message.
+
+> [!NOTE]
+> By default, installing IIS through the wizard enables the Default Web Site on port 80. If you want to quickly verify that IIS works, you can open a web browser on the server and navigate to http://localhost. You should be greeted by the IIS welcome page, indicating the web server is running.
+
+## PowerShell installation
+
+To install IIS via PowerShell in Windows Server, use the Install-WindowsFeature cmdlet from an elevated command prompt:
+
+```powershell
+Install-WindowsFeature Web-Server -IncludeManagementTools
+```
+
+You can install specific IIS subcomponents by name using PowerShell. For example, to install IIS with some common features, you might specify component names like Web-WebSockets or Web-Dyn-Compression. You can see the available web server features by running the command:
+
+```powershell
+Get-WindowsFeature -Name Web*
+```
+
+You can determine which IIS features are installed by running the command: 
+
+```powershell
+Get-WindowsFeature -Name Web* | Where Installed
+```
+
+## IIS on Server Core
+
+Server Core is the minimal, GUI-less installation option for Windows Server. The Server Core installation option is appropriate for workloads like IIS as the minimal number of components reduces the server's attack surface. You can deploy IIS on Server Core, but you can't use the local IIS Manager application. You can install IIS on Server Core using PowerShell using Install-WindowsFeature or remotely using Server Manager.
+
+To enable remote management, you need to install the Web Management Service (WMSVC). You can do this by running the following command:
+
+```powershell
+Install-WindowsFeature -Name Web-Mgmt-Service 
+```
+
+You enable remote management by configuring the registry. You can do this with the following command:
+
+```powershell
+Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\WebManagement\Server  -Name EnableRemoteManagement -Value 1
+```
+
+You can then configure the service to start automatically by running the command:
+
+```powershell
+Set-Service -Name WMSVC -StartupType Automatic
+```
+
+You have to allow inbound management traffic to the service. You can do this using the following command, restricting incoming management traffic to a designated management subnet (here it's 192.168.15.0/24):
+
+```powershell
+New-NetFirewallRule -DisplayName "IIS Remote Management" -Direction Inbound -Action Allow -Service WMSVC -RemoteAddress 192.168.15.0/24
+```
+
+Once WMSVC is running and listening, you can open IIS Manager on a different Windows machine and use the "Connect to a Server" option and enter the hostname (or IP) of your Server Core machine. You'll typically authenticate with an account that has local administrator privileges on the server hosting IIS.