Merge pull request #54027 from MicrosoftDocs/NEW-lp4m3-guided

New lp4m3 guided

Author: AnnaMHuff

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/1-introduction.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.introduction
+title: Introduction
+metadata:
+  title: Introduction
+  description: "Introduction"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 2
+content: |
+  [!include[](includes/1-introduction.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/2-exercise-create-function-app.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.exercise-create-function-app
+title: Exercise - Create the function app
+metadata:
+  title: Exercise - Create the Function App
+  description: "Exercise - Create the Function App"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 7
+content: |
+  [!include[](includes/2-exercise-create-function-app.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/3-exercise-create-http-trigger-function.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.exercise-create-http-trigger-function
+title: Exercise - Create an HTTP-trigger function
+metadata:
+  title: Exercise - Create an HTTP-trigger function
+  description: "Exercise - Create an HTTP-trigger function"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 7
+content: |
+  [!include[](includes/3-exercise-create-http-trigger-function.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/4-exercise-test-endpoint-logs.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.exercise-test-endpoint-logs
+title: Exercise - Test endpoint and review logs
+metadata:
+  title: Exercise - Test endpoint and review logs
+  description: "Exercise - Test endpoint and review logs"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 6
+content: |
+  [!include[](includes/4-exercise-test-endpoint-logs.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/5-validate-success.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.validate-success
+title: Validate success
+metadata:
+  title: Validate success
+  description: "Validate success"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 2
+content: |
+  [!include[](includes/5-validate-success.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/6-clean-up-resources.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.clean-up-resources
+title: Clean up resources
+metadata:
+  title: Clean up resources
+  description: "Clean up resources"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 5
+content: |
+  [!include[](includes/6-clean-up-resources.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/7-knowledge-check.yml

@@ -0,0 +1,51 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.knowledge-check
+title: Knowledge check
+metadata:
+  title: Knowledge check
+  description: "Knowledge check"
+  ms.date: 03/29/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 5
+content: |
+  [!include[](includes/7-knowledge-check.md)]
+quiz:
+  title: "Check your knowledge"
+  questions:
+  - content: "What type of trigger allows an Azure Function to respond to web requests?"
+    choices:
+    - content: "Timer trigger"
+      isCorrect: false
+      explanation: "A timer trigger runs on a schedule, not in response to web requests."
+    - content: "HTTP trigger"
+      isCorrect: true
+      explanation: "An HTTP trigger runs the function when it receives an HTTP request, making it suitable for web endpoints."
+    - content: "Blob trigger"
+      isCorrect: false
+      explanation: "A blob trigger fires when a file is added or updated in Blob Storage, not when a web request arrives."
+  - content: "What is the main advantage of using Azure Functions for a simple website endpoint?"
+    choices:
+    - content: "It provides a dedicated virtual machine for the endpoint."
+      isCorrect: false
+      explanation: "Azure Functions is a serverless service. You do not manage or provision virtual machines."
+    - content: "You do not need to manage any infrastructure."
+      isCorrect: true
+      explanation: "Azure Functions is serverless, meaning Azure handles all infrastructure. You focus only on the code."
+    - content: "It automatically creates a custom domain name."
+      isCorrect: false
+      explanation: "Azure Functions provides a default endpoint URL. Custom domains require separate configuration."
+  - content: "What Azure service lets you monitor function invocations and view execution logs?"
+    choices:
+    - content: "Azure Monitor metrics"
+      isCorrect: false
+      explanation: "Azure Monitor metrics can show high-level data, but detailed invocation logs for Functions come from Application Insights."
+    - content: "Azure Activity Log"
+      isCorrect: false
+      explanation: "The Activity Log tracks management operations on resources, not individual function invocations."
+    - content: "Application Insights"
+      isCorrect: true
+      explanation: "Application Insights provides detailed telemetry including invocation logs, response codes, and execution times for Azure Functions."

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/8-summary.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-build-basic-website-endpoint-with-functions.summary
+title: Summary
+metadata:
+  title: Summary
+  description: "Summary"
+  ms.date: 03/16/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 2
+content: |
+  [!include[](includes/8-summary.md)]

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/1-introduction.md

@@ -0,0 +1,41 @@
+This guided project focuses on building a simple HTTP endpoint using Azure Functions.
+
+Azure Functions is a serverless compute service that lets you run code in response to events without managing infrastructure. You write a function, deploy it, and Azure handles the scaling and hosting. With an HTTP trigger, your function gets its own URL that anyone can call from a browser.
+
+## Scenario
+
+Your team needs a lightweight endpoint for a contact page without maintaining servers. You create a Function App, deploy an HTTP-triggered function using Cloud Shell, and then test, secure, and monitor the endpoint—all in one session.
+
+- Exercise 1 - Create a Function App with the serverless Flex Consumption plan.
+- Exercise 2 - Deploy an HTTP-trigger function from Cloud Shell.
+- Exercise 3 - Test the endpoint, add security, and review logs.
+
+:::image type="content" source="../media/overview-architecture.png" alt-text="Diagram of a serverless HTTP endpoint using Azure Functions with an HTTP trigger, function key, and Application Insights." border="false":::
+
+By the end of this project, you have a live HTTP endpoint that responds to requests, requires an access key for security, and logs every invocation to Application Insights.
+
+> [!NOTE]
+> This is a guided project module where you complete a project by following step-by-step instructions.
+
+## Skilling areas
+
+In this project, you practice skills in the following areas:
+
+**Create and configure a Function App**
++ Create a resource group and a Function App.
++ Select the Flex Consumption hosting plan.
++ Verify deployment status in the portal.
+
+**Deploy a function using Cloud Shell**
++ Open Cloud Shell and initialize a function project.
++ Create an HTTP-triggered function.
++ Deploy the function to Azure from the command line.
+
+**Test, secure, and monitor a function**
++ Call the HTTP endpoint from a browser.
++ Enable Application Insights for monitoring.
++ Change the authorization level to require a function key.
++ Review invocation logs and execution details.
+
+> [!IMPORTANT]
+> This project uses the Azure portal for every step. No prior Azure experience is required.

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/2-exercise-create-function-app.md

@@ -0,0 +1,61 @@
+This guided project consists of the following exercises:
+
+ - **Create the Function App**
+ - Deploy an HTTP-trigger function
+ - Test endpoint and review logs
+
+In this exercise, you create a resource group and deploy a Function App using the serverless Flex Consumption plan. When you're done, you have a running Function App ready to host your first function.
+
+This exercise includes the following tasks:
+
+ - Prepare the environment
+ - Configure the Function App
+ - Verify the deployment
+
+**Outcome:** A running Function App that uses the serverless consumption plan.
+
+> [!TIP]
+> Pause after each major action and confirm the page status before moving on. This habit prevents compounding mistakes.
+
+## Task 1: Prepare the environment
+
+Set up your Azure environment before you begin. You create a resource group to organize all the resources for this project together.
+
+> [!WARNING]
+> This project creates Azure resources that may incur charges. Complete the clean-up unit when you're done to avoid unintended expenses.
+
+1.  Sign in to the [Azure portal](https://portal.azure.com) with an account that has permissions to create Function App resources.
+2.  In the portal search bar, search for **Resource groups** and select **Resource groups**.
+3.  Select **+ Create**. Name the resource group **rg-gp-functions-endpoint**, choose your preferred region, and select **Review + create** then **Create**.
+
+## Task 2: Configure the Function App
+
+Set up the Function App with serverless hosting. The Flex Consumption plan ensures you pay only for the execution time of your functions, making it cost-effective for occasional workloads.
+
+1.  In the portal search bar, search for **Function App** and select **Function App**.
+2.  Select **Create**.
+3.  Select **Flex Consumption** as the hosting option and select **Select**.
+4.  On the Basics tab, select **rg-gp-functions-endpoint** as the resource group.
+5.  For **Function App name**, enter a globally unique name (for example, **func-gp-endpoint-** followed by your initials and a number).
+6.  For **Secure unique default host name**, leave the default (**On**).
+7.  For **Region**, keep the default or choose your preferred region.
+8.  For **Runtime stack**, select **Node.js**.
+9.  For **Version**, keep the latest available LTS option.
+10. For **Instance size**, leave the default (**2048 MB**).
+11. Select **Review + create** and then select **Create**.
+
+> [!NOTE]
+> **Validation step:** Verify you selected all required settings before deployment: resource group, runtime stack (Node.js), region, and Flex Consumption hosting plan.
+
+> [!NOTE]
+> Each exercise includes validation steps like this one. Track your results as you go—you'll review them all in the validation unit at the end of this module.
+
+## Task 3: Verify the deployment
+
+Confirm that your Function App deployed successfully and is running.
+
+1.  When deployment completes, select **Go to resource**.
+2.  Confirm the Function App Overview page shows a **Running** status.
+
+> [!NOTE]
+> **Validation step:** Confirm the Function App Overview page shows **Running** status and note the resource URL.