Merge pull request #42575 from ggailey777/current

Freshness updates to VS quickstart

Author: ktoliver

articles/azure-functions/functions-create-your-first-function-visual-studio.md

@@ -34,7 +34,7 @@ To complete this tutorial:
 
 * Install [Visual Studio 2017](https://azure.microsoft.com/downloads/) and ensure that the **Azure development** workload is also installed.
 
-* If you installed the Azure development workload with Visual Studio 2017 version 15.4 or earlier, you will need to [update your Azure Functions tools](functions-develop-vs.md#check-your-tools-version).
+* Make sure you have the [latest Azure Functions tools](functions-develop-vs.md#check-your-tools-version).
 
 [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
 

articles/azure-functions/functions-develop-vs.md

@@ -88,13 +88,13 @@ The Functions runtime uses an Azure Storage account internally. For all trigger
 
 [!INCLUDE [Note on local storage](../../includes/functions-local-settings-note.md)]
 
- To set the storage account connection string:
+To set the storage account connection string:
 
 1. In Visual Studio, open **Cloud Explorer**, expand **Storage Account** > **Your Storage Account**, then select **Properties** and copy the **Primary Connection String** value.
 
 2. In your project, open the local.settings.json file and set the value of the **AzureWebJobsStorage** key to the connection string you copied.
 
-3. Repeat the previous step to add unique keys to the **Values** array for any other connections required by your functions.  
+3. Repeat the previous step to add unique keys to the **Values** array for any other connections required by your functions.
 
 ## Create a function
 
@@ -157,7 +157,7 @@ As with triggers, input and output bindings are added to your function as bindin
         }
     }
     ```
-The connection to Queue storage is obtained from the `AzureWebJobsStorage` setting. For more information, see the reference article for the specific binding.
+The connection to Queue storage is obtained from the `AzureWebJobsStorage` setting. For more information, see the reference article for the specific binding. 
 
 [!INCLUDE [Supported triggers and bindings](../../includes/functions-bindings.md)]
 

includes/functions-vstools-create.md

@@ -16,7 +16,7 @@ The Azure Functions project template in Visual Studio creates a project that can
 
 2. In the **New Project** dialog, select **Installed**, expand **Visual C#** > **Cloud**, select **Azure Functions**, type a **Name** for your project, and click **OK**. The function app name must be valid as a C# namespace, so don't use underscores, hyphens, or any other nonalphanumeric characters.
 
-    ![New project dialog to create a function in Visual Studio](./media/functions-vstools-create/functions-vstools-add-new-project.png) 
+    ![New project dialog to create a function in Visual Studio](./media/functions-vstools-create/functions-vstools-add-new-project.png)
 
 3. Use the settings specified in the table that follows the image.
 

includes/functions-vstools-publish.md

@@ -10,26 +10,28 @@ ms.author: glenga
 ms.custom: include file
 ---
 
-1. In **Solution Explorer**, right-click the project and select **Publish**. Choose **Create New**  and then **Publish**.
+1. In **Solution Explorer**, right-click the project and select **Publish**.
+
+2. Select **Azure Function App**, choose **Create New**, and then select **Publish**.
+
+    ![Pick a publish target](./media/functions-vstools-publish/functions-vstools-create-new-function-app.png)
 
 2. If you haven't already connected Visual Studio to your Azure account, select **Add an account...**.
 
-3. In the **Create App Service** dialog, use the **Hosting** settings as specified in the following table:
+3. In the **Create App Service** dialog, use the **Hosting** settings as specified in the table below the image:
 
-    ![Azure local runtime](./media/functions-vstools-publish/functions-vstools-publish.png)
+    ![Create App Service dialog](./media/functions-vstools-publish/functions-vstools-publish.png)
 
     | Setting      | Suggested value  | Description                                |
     | ------------ |  ------- | -------------------------------------------------- |
     | **App Name** | Globally unique name | Name that uniquely identifies your new function app. |
     | **Subscription** | Choose your subscription | The Azure subscription to use. |
     | **[Resource Group](../articles/azure-resource-manager/resource-group-overview.md)** | myResourceGroup |  Name of the resource group in which to create your function app. Choose **New** to create a new resource group.|
-    | **[App Service Plan](../articles/azure-functions/functions-scale.md)** | Consumption plan | Make sure to choose the **Consumption** under **Size** after you click **New** to create a new plan. Also, choose a **Location** in a [region](https://azure.microsoft.com/regions/) near you or near other services your functions access.  |
-
-    >[!NOTE]
-    >An Azure storage account is required by the Functions runtime. Because of this, a new Azure Storage account is created for you when you create a function app.
+    | **[App Service Plan](../articles/azure-functions/functions-scale.md)** | Consumption plan | Make sure to choose the **Consumption** under **Size** after you click **New** to create a plan. Also, choose a **Location** in a [region](https://azure.microsoft.com/regions/) near you or near other services your functions access.  |
+    | **[Storage Account](../articles/storage/common/storage-create-storage-account.md#create-a-storage-account)** | General purpose storage account | An Azure storage account is required by the Functions runtime. Click **New** to create a general purpose storage account, or use an existing one.  |
 
 4. Click **Create** to create a function app and related resources in Azure with these settings and deploy your function project code. 
 
 5. After the deployment is complete, make a note of the **Site URL** value, which is the address of your function app in Azure.
 
-    ![Azure local runtime](./media/functions-vstools-publish/functions-vstools-publish-profile.png)
+    ![Publish success message](./media/functions-vstools-publish/functions-vstools-publish-profile.png)