Update links

craigshoemaker · craigshoemaker · commit 1c9b6a4ea429 · 2020-02-13T06:23:01.000-05:00
diff --git a/articles/azure-functions/durable/durable-functions-dotnet-entities.md b/articles/azure-functions/durable/durable-functions-dotnet-entities.md
@@ -367,7 +367,7 @@ public static Task Run([EntityTrigger] IDurableEntityContext ctx)
 
 Unlike regular functions, entity class methods don't have direct access to input and output bindings. Instead, binding data must be captured in the entry-point function declaration and then passed to the `DispatchAsync<T>` method. Any objects passed to `DispatchAsync<T>` will be automatically passed into the entity class constructor as an argument.
 
-The following example shows how a `CloudBlobContainer` reference from the [blob input binding](../functions-bindings-storage-blob.md#input) can be made available to a class-based entity.
+The following example shows how a `CloudBlobContainer` reference from the [blob input binding](../functions-bindings-storage-blob-input.md) can be made available to a class-based entity.
 
 ```csharp
 public class BlobBackedEntity
diff --git a/articles/azure-functions/functions-add-output-binding-storage-queue-java.md b/articles/azure-functions/functions-add-output-binding-storage-queue-java.md
@@ -113,7 +113,7 @@ mvn azure-functions:run
 ```
 
 > [!NOTE]  
-> Because you enabled extension bundles in the host.json, the [Storage binding extension](functions-bindings-storage-blob.md#packages---functions-2x-and-higher) was downloaded and installed for you during startup, along with the other Microsoft binding extensions.
+> Because you enabled extension bundles in the host.json, the [Storage binding extension](functions-bindings-storage-blob.md#add-to-your-functions-app) was downloaded and installed for you during startup, along with the other Microsoft binding extensions.
 
 As before, trigger the function from the command line using cURL in a new terminal window:
 
diff --git a/articles/azure-functions/functions-add-output-binding-storage-queue-python.md b/articles/azure-functions/functions-add-output-binding-storage-queue-python.md
@@ -151,7 +151,7 @@ Observe that you *don't* need to write any code for authentication, getting a qu
 1. When you're done, stop the host with **Ctrl**+**C**.
 
 > [!TIP]
-> During startup, the host downloads and installs the [Storage binding extension](functions-bindings-storage-blob.md#packages---functions-2x-and-higher) and other Microsoft binding extensions. This installation happens because binding extensions are enabled by default in the *host.json* file with the following properties:
+> During startup, the host downloads and installs the [Storage binding extension](functions-bindings-storage-blob.md#add-to-your-functions-app) and other Microsoft binding extensions. This installation happens because binding extensions are enabled by default in the *host.json* file with the following properties:
 >
 > ```json
 > {
diff --git a/articles/azure-functions/functions-bindings-error-pages.md b/articles/azure-functions/functions-bindings-error-pages.md
@@ -24,7 +24,7 @@ When integrating with Azure services, errors may originate from the APIs of the
 
 + [Azure Cosmos DB](functions-bindings-cosmosdb.md#exceptions-and-return-codes)
 
-+ [Blob storage](functions-bindings-storage-blob.md#exceptions-and-return-codes)
++ [Blob storage](functions-bindings-storage-blob-output.md#exceptions-and-return-codes)
 
 + [Event Hubs](functions-bindings-event-hubs.md#exceptions-and-return-codes)
 
diff --git a/articles/azure-functions/functions-dotnet-class-library.md b/articles/azure-functions/functions-dotnet-class-library.md
@@ -200,7 +200,7 @@ If you install the Core Tools by using npm, that doesn't affect the Core Tools v
 
 ## Supported types for bindings
 
-Each binding has its own supported types; for instance, a blob trigger attribute can be applied to a string parameter, a POCO parameter, a `CloudBlockBlob` parameter, or any of several other supported types. The [binding reference article for blob bindings](functions-bindings-storage-blob.md#trigger---usage) lists all supported parameter types. For more information, see [Triggers and bindings](functions-triggers-bindings.md) and the [binding reference docs for each binding type](functions-triggers-bindings.md#next-steps).
+Each binding has its own supported types; for instance, a blob trigger attribute can be applied to a string parameter, a POCO parameter, a `CloudBlockBlob` parameter, or any of several other supported types. The [binding reference article for blob bindings](functions-bindings-storage-blob-trigger.md#usage) lists all supported parameter types. For more information, see [Triggers and bindings](functions-triggers-bindings.md) and the [binding reference docs for each binding type](functions-triggers-bindings.md#next-steps).
 
 [!INCLUDE [HTTP client best practices](../../includes/functions-http-client-best-practices.md)]
 
diff --git a/articles/azure-functions/functions-reference-csharp.md b/articles/azure-functions/functions-reference-csharp.md
@@ -84,7 +84,7 @@ The `#r` statement is explained [later in this article](#referencing-external-as
 
 ## Supported types for bindings
 
-Each binding has its own supported types; for instance, a blob trigger can be used with a string parameter, a POCO parameter, a `CloudBlockBlob` parameter, or any of several other supported types. The [binding reference article for blob bindings](functions-bindings-storage-blob.md#trigger---usage) lists all supported parameter types for blob triggers. For more information, see [Triggers and bindings](functions-triggers-bindings.md) and the [binding reference docs for each binding type](functions-triggers-bindings.md#next-steps).
+Each binding has its own supported types; for instance, a blob trigger can be used with a string parameter, a POCO parameter, a `CloudBlockBlob` parameter, or any of several other supported types. The [binding reference article for blob bindings](functions-bindings-storage-blob-trigger.md#usage) lists all supported parameter types for blob triggers. For more information, see [Triggers and bindings](functions-triggers-bindings.md) and the [binding reference docs for each binding type](functions-triggers-bindings.md#next-steps).
 
 [!INCLUDE [HTTP client best practices](../../includes/functions-http-client-best-practices.md)]
 
@@ -464,7 +464,7 @@ or [`IAsyncCollector<T>`](https://github.com/Azure/azure-webjobs-sdk/blob/master
 
 ### Single attribute example
 
-The following example code creates a [Storage blob output binding](functions-bindings-storage-blob.md#output)
+The following example code creates a [Storage blob output binding](functions-bindings-storage-blob-output.md)
 with blob path that's defined at run time, then writes a string to the blob.
 
 ```cs
diff --git a/includes/functions-bindings-blob-storage-input-usage.md b/includes/functions-bindings-blob-storage-input-usage.md
@@ -26,6 +26,6 @@ You can use the following parameter types for the blob input binding:
 
 <sup>1</sup> Requires "inout" binding `direction` in *function.json* or `FileAccess.ReadWrite` in a C# class library.
 
-If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](#azure-storage-sdk-version-in-functions-1x).
+If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](../articles/azure-functions/functions-bindings-storage-blob.md#azure-storage-sdk-version-in-functions-1x).
 
-Binding to `string` or `Byte[]` is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](#trigger---concurrency-and-memory-usage) earlier in this article.
+Binding to `string` or `Byte[]` is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](../articles/azure-functions/functions-bindings-storage-blob-trigger.md#concurrency-and-memory-usage) earlier in this article.
diff --git a/includes/functions-bindings-blob-storage-output-usage.md b/includes/functions-bindings-blob-storage-output-usage.md
@@ -29,8 +29,8 @@ You can bind to the following types to write blobs:
 
 <sup>2</sup> Requires "inout" binding `direction` in *function.json* or `FileAccess.ReadWrite` in a C# class library.
 
-If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](#azure-storage-sdk-version-in-functions-1x).
+If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](../articles/azure-functions/functions-bindings-storage-blob.md#azure-storage-sdk-version-in-functions-1x).
 
 In async functions, use the return value or `IAsyncCollector` instead of an `out` parameter.
 
-Binding to `string` or `Byte[]` is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](#trigger---concurrency-and-memory-usage) earlier in this article.
+Binding to `string` or `Byte[]` is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](../articles/azure-functions/functions-bindings-storage-blob-trigger.md#concurrency-and-memory-usage) earlier in this article.
diff --git a/includes/functions-bindings-blob-storage-trigger.md b/includes/functions-bindings-blob-storage-trigger.md
@@ -25,6 +25,6 @@ You can use the following parameter types for the triggering blob:
 
 <sup>1</sup> Requires "inout" binding `direction` in *function.json* or `FileAccess.ReadWrite` in a C# class library.
 
-If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](#azure-storage-sdk-version-in-functions-1x).
+If you try to bind to one of the Storage SDK types and get an error message, make sure that you have a reference to [the correct Storage SDK version](../articles/azure-functions/functions-bindings-storage-blob.md#azure-storage-sdk-version-in-functions-1x).
 
-Binding to `string`, `Byte[]`, or POCO is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](#trigger---concurrency-and-memory-usage) later in this article.
+Binding to `string`, `Byte[]`, or POCO is only recommended if the blob size is small, as the entire blob contents are loaded into memory. Generally, it is preferable to use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](../articles/azure-functions/functions-bindings-storage-blob-trigger.md#concurrency-and-memory-usage) later in this article.
diff --git a/includes/functions-bindings-errors-intro.md b/includes/functions-bindings-errors-intro.md
@@ -34,4 +34,4 @@ The following triggers have built-in retry support:
 
 By default, these triggers retry requests up to five times. After the fifth retry, both the Azure Queue storage and Azure Service Bus triggers write a message to a [poison queue](..\articles\azure-functions\functions-bindings-storage-queue.md#trigger---poison-messages).
 
-You need to manually implement retry policies for any other triggers or bindings types. Manual implementations may include writing error information to a [poison message queue](..\articles\azure-functions\functions-bindings-storage-blob.md#trigger---poison-blobs). By writing to a poison queue, you have the opportunity to retry operations at a later time. This approach is the same one used by the Blob storage trigger.
+You need to manually implement retry policies for any other triggers or bindings types. Manual implementations may include writing error information to a [poison message queue](..\articles\azure-functions\functions-bindings-storage-blob-trigger.md#poison-blobs). By writing to a poison queue, you have the opportunity to retry operations at a later time. This approach is the same one used by the Blob storage trigger.
diff --git a/includes/functions-local-settings-file.md b/includes/functions-local-settings-file.md
@@ -34,7 +34,7 @@ These settings are supported when you run projects locally:
 | Setting      | Description                            |
 | ------------ | -------------------------------------- |
 | **`IsEncrypted`** | When this setting is set to `true`, all values are encrypted with a local machine key. Used with `func settings` commands. Default value is `false`. |
-| **`Values`** | Array of application settings and connection strings used when a project is running locally. These key-value (string-string) pairs correspond to application settings in your function app in Azure, like [`AzureWebJobsStorage`]. Many triggers and bindings have a property that refers to a connection string app setting, like `Connection` for the [Blob storage trigger](../articles/azure-functions/functions-bindings-storage-blob.md#trigger---configuration). For these properties, you need an application setting defined in the `Values` array. <br/>[`AzureWebJobsStorage`] is a required app setting for triggers other than HTTP. <br/>Version 2.x and higher of the Functions runtime requires the [`FUNCTIONS_WORKER_RUNTIME`] setting, which is generated for your project by Core Tools. <br/> When you have the [Azure storage emulator](../articles/storage/common/storage-use-emulator.md) installed locally and you set [`AzureWebJobsStorage`] to `UseDevelopmentStorage=true`, Core Tools uses the emulator. The emulator is useful during development, but you should test with an actual storage connection before deployment.<br/> Values must be strings and not JSON objects or arrays. Setting names can't include a colon (`:`) or a double underline (`__`). These characters are reserved by the runtime.  |
+| **`Values`** | Array of application settings and connection strings used when a project is running locally. These key-value (string-string) pairs correspond to application settings in your function app in Azure, like [`AzureWebJobsStorage`]. Many triggers and bindings have a property that refers to a connection string app setting, like `Connection` for the [Blob storage trigger](../articles/azure-functions/functions-bindings-storage-blob-trigger.md#configuration). For these properties, you need an application setting defined in the `Values` array. <br/>[`AzureWebJobsStorage`] is a required app setting for triggers other than HTTP. <br/>Version 2.x and higher of the Functions runtime requires the [`FUNCTIONS_WORKER_RUNTIME`] setting, which is generated for your project by Core Tools. <br/> When you have the [Azure storage emulator](../articles/storage/common/storage-use-emulator.md) installed locally and you set [`AzureWebJobsStorage`] to `UseDevelopmentStorage=true`, Core Tools uses the emulator. The emulator is useful during development, but you should test with an actual storage connection before deployment.<br/> Values must be strings and not JSON objects or arrays. Setting names can't include a colon (`:`) or a double underline (`__`). These characters are reserved by the runtime.  |
 | **`Host`** | Settings in this section customize the Functions host process when you run projects locally. These settings are separate from the host.json settings, which also apply when you run projects in Azure. |
 | **`LocalHttpPort`** | Sets the default port used when running the local Functions host (`func host start` and `func run`). The `--port` command-line option takes precedence over this setting. |
 | **`CORS`** | Defines the origins allowed for [cross-origin resource sharing (CORS)](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing). Origins are supplied as a comma-separated list with no spaces. The wildcard value (\*) is supported, which allows requests from any origin. |
diff --git a/includes/functions-package-v2.md b/includes/functions-package-v2.md
@@ -2,21 +2,20 @@
 title: include file
 description: include file
 services: functions
-author: ggailey777
+author: craigshoemaker
 manager: gwallace
 ms.service: azure-functions
 ms.topic: include
-ms.date: 09/04/2018
-ms.author: glenga
+ms.date: 01/28/2020
+ms.author: cshoe
 ms.custom: include file
 ---
 
-The following table tells how to add support for this binding in each development environment.
+Add support in you preferred development environment using the following methods.
 
-| Development environment               | To add support  |
-|----------------------|----------------|
-|Local development - C# class library       | [Install the package](../articles/azure-functions/functions-bindings-register.md#vs) |
-|Local development - C# script, JavaScript, F#, Java and Python |[Register the extension](../articles/azure-functions/functions-bindings-register.md#extension-bundles)         |
-|Portal development| Install when adding output binding    |
-
-To learn how to update existing binding extensions in the portal without having to republish your function app project, see [Update your extensions](../articles/azure-functions/install-update-binding-extensions-manual.md).
+| Development environment  | Application type      | To add support |
+|--------------------------|-----------------------|----------------|
+| Visual Studio            | C# class library      | [Install the NuGet package](../articles/azure-functions/functions-bindings-register.md#vs) |
+| Visual Studio Code       | Based on [core tools](../articles/azure-functions/functions-run-local.md) | [Register the extension bundle](../articles/azure-functions/functions-bindings-register.md#extension-bundles)<br><br>Installing the [Azure Tools extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack) is recommended. |
+| Any other editor/IDE     | Based on [core tools](../articles/azure-functions/functions-run-local.md) | [Register the extension bundle](../articles/azure-functions/functions-bindings-register.md#extension-bundles) |
+| Azure Portal             | Online only in portal | Installs when adding a binding<br /><br /> See [Update your extensions](../articles/azure-functions/install-update-binding-extensions-manual.md) to update existing binding extensions without having to republish your function app. |
diff --git a/includes/functions-storage-sdk-version.md b/includes/functions-storage-sdk-version.md
@@ -2,15 +2,15 @@
 title: include file
 description: include file
 services: functions
-author: ggailey777
-manager: cfowler
+author: craigshoemaker
+manager: gwallace
 ms.service: azure-functions
 ms.topic: include
-ms.date: 05/17/2018
-ms.author: tdykstra
+ms.date: 01/28/2020
+ms.author: cshoe
 ms.custom: include file
 ---
 
-### Azure Storage SDK version in Functions 1.x
+#### Azure Storage SDK version in Functions 1.x
 
 In Functions 1.x, the Storage triggers and bindings use version 7.2.1 of the Azure Storage SDK ([WindowsAzure.Storage](https://www.nuget.org/packages/WindowsAzure.Storage/7.2.1) NuGet package). If you reference a different version of the Storage SDK, and you bind to a Storage SDK type in your function signature, the Functions runtime may report that it can't bind to that type. The solution is to make sure your project references [WindowsAzure.Storage 7.2.1](https://www.nuget.org/packages/WindowsAzure.Storage/7.2.1).

Original file line number	Diff line number	Diff line change
`@@ -151,7 +151,7 @@ Observe that you don't need to write any code for authentication, getting a qu`
`151`	`151`	`1. When you're done, stop the host with Ctrl+C.`
`152`	`152`
`153`	`153`	`> [!TIP]`
`154`		`-> During startup, the host downloads and installs the [Storage binding extension](functions-bindings-storage-blob.md#packages---functions-2x-and-higher) and other Microsoft binding extensions. This installation happens because binding extensions are enabled by default in the host.json file with the following properties:`
	`154`	`+> During startup, the host downloads and installs the [Storage binding extension](functions-bindings-storage-blob.md#add-to-your-functions-app) and other Microsoft binding extensions. This installation happens because binding extensions are enabled by default in the host.json file with the following properties:`
`155`	`155`	`>`
`156`	`156`	> ```json
`157`	`157`	`> {`
Original file line number	Diff line number	Diff line change
`@@ -34,4 +34,4 @@ The following triggers have built-in retry support:`
`34`	`34`
`35`	`35`	`By default, these triggers retry requests up to five times. After the fifth retry, both the Azure Queue storage and Azure Service Bus triggers write a message to a [poison queue](..\articles\azure-functions\functions-bindings-storage-queue.md#trigger---poison-messages).`
`36`	`36`
`37`		`-You need to manually implement retry policies for any other triggers or bindings types. Manual implementations may include writing error information to a [poison message queue](..\articles\azure-functions\functions-bindings-storage-blob.md#trigger---poison-blobs). By writing to a poison queue, you have the opportunity to retry operations at a later time. This approach is the same one used by the Blob storage trigger.`
	`37`	`+You need to manually implement retry policies for any other triggers or bindings types. Manual implementations may include writing error information to a [poison message queue](..\articles\azure-functions\functions-bindings-storage-blob-trigger.md#poison-blobs). By writing to a poison queue, you have the opportunity to retry operations at a later time. This approach is the same one used by the Blob storage trigger.`