changed files by pdets auto publish service, publishid[6350cdda-24d0-4e90-ba65-a475fc66fff7] and do [publish].

Author: wwlpublish

learn-pr/wwl-azure/develop-azure-functions/1-introduction.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]

learn-pr/wwl-azure/develop-azure-functions/2-azure-function-development-overview.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore Azure Functions development
   description: "Explore Azure Functions development"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/2-azure-function-development-overview.md)]
+  [!include[](includes/2-azure-function-development-overview.md)]

learn-pr/wwl-azure/develop-azure-functions/3-create-triggers-bindings.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Create triggers and bindings
   description: "Create triggers and bindings"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 3
+durationInMinutes: 8
 content: |
-  [!include[](includes/3-create-triggers-bindings.md)]
+  [!include[](includes/3-create-triggers-bindings.md)]

learn-pr/wwl-azure/develop-azure-functions/4-connect-azure-services.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Connect functions to Azure services
   description: "Connect functions to Azure services"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/4-connect-azure-services.md)]
+  [!include[](includes/4-connect-azure-services.md)]

learn-pr/wwl-azure/develop-azure-functions/5-create-function-visual-studio-code.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: Create an Azure Function by using Visual Studio Code'
   description: "Exercise: Create an Azure Function by using Visual Studio Code"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 15
 content: |
-  [!include[](includes/5-create-function-visual-studio-code.md)]
+  [!include[](includes/5-create-function-visual-studio-code.md)]

learn-pr/wwl-azure/develop-azure-functions/6-knowledge-check.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -37,4 +37,4 @@ quiz:
       explanation: "Incorrect. Triggers only support the `in` direction."
     - content: "Connection value"
       isCorrect: false
-      explanation: "Incorrect. A connection value is used to connect your function to other Azure services."
+      explanation: "Incorrect. A connection value is used to connect your function to other Azure services."

learn-pr/wwl-azure/develop-azure-functions/7-summary.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 07/09/2024
+  ms.date: 02/14/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/7-summary.md)]
+  [!include[](includes/7-summary.md)]

learn-pr/wwl-azure/develop-azure-functions/includes/2-azure-function-development-overview.md

@@ -1,7 +1,7 @@
 A function app provides an execution context in Azure in which your functions run. As such, it's the unit of deployment and management for your functions. A function app is composed of one or more individual functions that are managed, deployed, and scaled together. All of the functions in a function app share the same pricing plan, deployment method, and runtime version. Think of a function app as a way to organize and collectively manage your functions.
 
 > [!NOTE]
-> In Functions 2.x all functions in a function app must be authored in the same language. In previous versions of the Azure Functions runtime, this wasn't required.
+> In Functions 2.x, all functions in a function app must be authored in the same language. In previous versions of the Azure Functions runtime, this wasn't required.
 
 ## Develop and test Azure Functions locally
 
@@ -23,7 +23,7 @@ A Functions project directory contains the following files in the project root f
 The `host.json` metadata file contains configuration options that affect all functions in a function app instance. Other function app configuration options are managed depending on where the function app runs:
 
 * **Deployed to Azure:** in your application settings
-* **On your local computer:** in the local.settings.json file.
+* **On your local computer:** in the `local.settings.json` file.
 
 Configurations in `host.json` related to bindings are applied equally to each function in the function app. You can also override or apply settings per environment using application settings. To learn more, see the [host.json reference](/azure/azure-functions/functions-host-json). 
 

learn-pr/wwl-azure/develop-azure-functions/includes/3-create-triggers-bindings.md

@@ -6,6 +6,12 @@ You can mix and match different bindings to suit your needs. Bindings are option
 
 Triggers and bindings let you avoid hardcoding access to other services. Your function receives data (for example, the content of a queue message) in function parameters. You send data (for example, to create a queue message) by using the return value of the function.
 
+When you develop your functions locally, you need to take trigger and binding behaviors into consideration. For HTTP triggers, you can call the HTTP endpoint on the local computer, using `http://localhost/`. For non-HTTP triggered functions, there are several options to run locally:
+
+* The easiest way to test bindings during local development is to use connection strings that target live Azure services. You can target live services by adding the appropriate connection string settings in the `Values` array in the local.settings.json file. When you do this, local executions during testing use live service data. Because of this, consider setting-up separate services to use during development and testing, and then switch to different services during production.
+* For storage-based triggers, you can use the local [Azurite emulator](/azure/storage/common/storage-use-azurite) when testing functions with Azure Storage bindings (Queue Storage, Blob Storage, and Table Storage), without having to connect to remote storage services.
+* You can manually run non-HTTP trigger functions by using special administrator endpoints. For more information, see [Manually run a non HTTP-triggered function](/azure/azure-functions/functions-manually-run-non-http).
+
 ## Trigger and binding definitions
 
 Triggers and bindings are defined differently depending on the development language.

learn-pr/wwl-azure/develop-azure-functions/includes/4-connect-azure-services.md

@@ -1,19 +1,19 @@
-As a security best practice, Azure Functions takes advantage of the application settings functionality of Azure App Service to help you more securely store strings, keys, and other tokens required to connect to other services. Application settings in Azure are stored encrypted and can be accessed at runtime by your app as environment variable `name` `value` pairs. For triggers and bindings that require a connection property, you set the application setting name instead of the actual connection string. You can't configure a binding directly with a connection string or key.
+As a security best practice, Azure Functions takes advantage of the application settings functionality of Azure App Service to help you more securely store strings, keys, and other tokens required to connect to other services. Application settings in Azure are stored encrypted and accessed at runtime by your app as environment variable `name` `value` pairs. For triggers and bindings that require a connection property, you set the application setting name instead of the actual connection string. You can't configure a binding directly with a connection string or key.
 
 The default configuration provider uses environment variables. These variables are defined in application settings when running in the Azure and in the local settings file when developing locally.
 
 ## Configure an identity-based connection
 
-Some connections in Azure Functions are configured to use an identity instead of a secret. Support depends on the extension using the connection. In some cases, a connection string may still be required in Functions even though the service to which you're connecting supports identity-based connections.
+Some connections in Azure Functions are configured to use an identity instead of a secret. Support depends on the extension using the connection. In some cases, a connection string might still be required in Functions even though the service to which you're connecting supports identity-based connections.
 
 > [!NOTE]
-> When running in a Consumption or Elastic Premium plan, your app uses the `WEBSITE_AZUREFILESCONNECTIONSTRING` and `WEBSITE_CONTENTSHARE` settings when connecting to Azure Files on the storage account used by your function app. Azure Files doesn't support using managed identity when accessing the file share.
+> An app running in a Consumption or Elastic Premium plan, uses the `WEBSITE_AZUREFILESCONNECTIONSTRING` and `WEBSITE_CONTENTSHARE` settings when connecting to Azure Files on the storage account used by your function app. Azure Files doesn't support using managed identity when accessing the file share.
 
 When hosted in the Azure Functions service, identity-based connections use a managed identity. The system-assigned identity is used by default, although a user-assigned identity can be specified with the `credential` and `clientID` properties. Configuring a user-assigned identity with a resource ID is **not** supported. When run in other contexts, such as local development, your developer identity is used instead, although this can be customized.
 
 ## Grant permission to the identity
 
-Identities must have permissions to perform the intended actions. This is typically done by assigning a role in Azure RBAC or specifying the identity in an access policy, depending on the service to which you're connecting. 
+Identities must have permissions to perform the intended actions. This is typically done by assigning a role in Azure role-based access control or specifying the identity in an access policy, depending on the service to which you're connecting. 
 
 > [!IMPORTANT]
-> Some permissions might be exposed by the target service that are not necessary for all contexts. Where possible, adhere to the **principle of least privilege**, granting the identity only required privileges.
+> Some permissions might be exposed by the target service that aren't necessary for all contexts. Where possible, adhere to the **principle of least privilege**, granting the identity only required privileges.