Add back missing info, fix links

Author: andystaples

articles/azure-functions/durable/durable-functions-powershell-v2-sdk-migration-guide.md

@@ -84,7 +84,7 @@ Update-AzFunctionAppSetting -Name <FUNCTION_APP_NAME> -ResourceGroupName <RESOUR
 
 ### Install and import the SDK
 
-You have two options for installing the SDK package: it can be installed as a [managed dependency](./../functions-reference-powershell.md#dependency-management), or as a [custom module](./../functions-reference-powershell.md#custom-modules).
+You have two options for installing the SDK package: it can be installed using [Managed Dependencies](./../functions-reference-powershell.md#managed-dependencies-feature), or [bundled with your app content](./../functions-reference-powershell.md#including-modules-in-app-content).
 In this section, we describe both options, but only one of them is needed.
 
 #### Installation option 1: Use managed dependencies

articles/azure-functions/flex-consumption-plan.md

@@ -138,7 +138,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
 + **Regions**: Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
 + **Deployments**: Deployment slots are not currently supported.
 + **Scale**: The lowest maximum scale is currently `40`. The highest currently supported value is `1000`. 
-+ **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#dependency-management) aren't supported by Flex Consumption. You must instead [define your own custom modules](functions-reference-powershell.md#custom-modules).
++ **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#managed-dependencies-feature) aren't supported by Flex Consumption. You must instead [upload modules with app content](functions-reference-powershell.md#including-modules-in-app-content).
 + **Diagnostic settings**: Diagnostic settings are not currently supported.
 + **Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting is currently not supported.
 + **Key Vault References**: Key Vault references in app settings don't work when Key Vault is network access restricted, even if the function app has Virtual Network integration. The current workaround is to directly reference the Key Vault in code and read the required secrets.

articles/azure-functions/functions-reference-powershell.md

@@ -588,6 +588,23 @@ You can configure how Managed Dependencies are downloaded and installed using th
 - **Internet Access**: Managed Dependencies require access to `https://www.powershellgallery.com` to download modules. Ensure that your environment allows this access, including modifying firewall/VNet rules as needed.
 - **License Acceptance**: Managed Dependencies doesn't support modules that require license acceptance.
 - **Flex Consumption Plan**: The Managed Dependencies feature isn't supported in the Flex Consumption plan. Use custom modules instead.
+- **Module Locations**: On your local computer, modules are typically installed in one of the globally available folders in your `$env:PSModulePath`. When running in Azure, the `$env:PSModulePath` for a PowerShell function app differs from `$env:PSModulePath` in a regular PowerShell script and will contain both the `Modules` folder uploaded with your app contents and a separate location managed by Managed Dependencies.
+
+## Environment variables
+
+In Functions, [app settings](functions-app-settings.md), such as service connection strings, are exposed as environment variables during execution. You can access these settings using `$env:NAME_OF_ENV_VAR`, as shown in the following example:
+
+```powershell
+param($myTimer)
+
+Write-Host "PowerShell timer trigger function ran! $(Get-Date)"
+Write-Host $env:AzureWebJobsStorage
+Write-Host $env:WEBSITE_SITE_NAME
+```
+
+[!INCLUDE [Function app settings](../../includes/functions-app-settings.md)]
+
+When running locally, app settings are read from the [local.settings.json](functions-develop-local.md#local-settings-file) project file.
 
 ## Concurrency
 
@@ -699,7 +716,7 @@ When developing Azure Functions in the [serverless hosting model](consumption-pl
 
 Running `Install-Module` in your function script on each invocation can cause performance issues. Instead, use `Save-Module` or `Save-PSResource` before publishing your function app to bundle the necessary modules.
 
-For more information, see the [Module Management](#module-management) section.
+For more information, see the [Dependency Management](#dependency-management) section.
 
 ## Next steps
 

articles/azure-functions/opentelemetry-howto.md

@@ -207,7 +207,7 @@ These instructions only apply for an OTLP exporter:
 
 1. Add an application setting named `OTEL_FUNCTIONS_WORKER_ENABLED` with value of `True`.
 
-1. Create an [app-level `Modules` folder](functions-reference-powershell.md#function-app-level-modules-folder) in the root of your app and run the following command:
+1. Create an [app-level `Modules` folder](functions-reference-powershell.md#including-modules-in-app-content) in the root of your app and run the following command:
 
     ```powershell
     Save-Module -Name AzureFunctions.PowerShell.OpenTelemetry.SDK