Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into asc-melvyn-20200129

Author: memildin

articles/active-directory/saas-apps/media/wdesk-tutorial/wdesk-username.png

@@ -1186,8 +1186,6 @@
         href: qmarkets-idea-innovation-management-tutorial.md
       - name: QPrism
         href: qprism-tutorial.md
-      - name: Qualtrics
-        href: qualtrics-tutorial.md
       - name: Quantum Workplace
         href: quantum-workplace-tutorial.md
       - name: Questetra BPM Suite
@@ -1286,6 +1284,8 @@
         href: saphana-tutorial.md
       - name: SAP NetWeaver
         href: sap-netweaver-tutorial.md
+      - name: SAP Qualtrics
+        href: qualtrics-tutorial.md
       - name: Sauce Labs - Mobile and Web Testing
         href: saucelabs-mobileandwebtesting-tutorial.md
       - name: ScaleX Enterprise

articles/active-directory/saas-apps/qualtrics-tutorial.md

@@ -13,7 +13,7 @@ ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.tgt_pltfrm: na
 ms.topic: tutorial
-ms.date: 01/31/2020
+ms.date: 04/02/2020
 ms.author: jeedes
 
 ---
@@ -180,6 +180,10 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
     ![Configure Single Sign-On](./media/wdesk-tutorial/tutorial_wdesk_ssoconfig2.png)
 
+1. Under **SAML User ID Settings**, check **SAML User ID is Wdesk Username**.
+
+    ![Configure Single Sign-On](./media/wdesk-tutorial/wdesk-username.png)
+
 4. Under **General Settings**, check the **Enable SAML Single Sign On**:
 
     ![Configure Single Sign-On](./media/wdesk-tutorial/tutorial_wdesk_ssoconfig3.png)
@@ -222,17 +226,17 @@ To enable Azure AD users to sign in to Wdesk, they must be provisioned into Wdes
 
     ![Creating an Azure AD test user](./media/wdesk-tutorial/createuser1.png)  
 
-5. In **User** text box, enter the username of user like brittasimon@contoso.com and click **Continue** button.
+5. In **User** text box, enter the username of user like b.simon@contoso.com and click **Continue** button.
 
     ![Creating an Azure AD test user](./media/wdesk-tutorial/createuser3.png)
 
 6.  Enter the details as shown below:
 
     ![Creating an Azure AD test user](./media/wdesk-tutorial/createuser4.png)
 
-    a. In **E-mail** text box, enter the email of user like brittasimon@contoso.com.
+    a. In **E-mail** text box, enter the email of user like b.simon@contoso.com.
 
-    b. In **First Name** text box, enter the first name of user like **Britta**.
+    b. In **First Name** text box, enter the first name of user like **B**.
 
     c. In **Last Name** text box, enter the last name of user like **Simon**.
 

articles/active-directory/saas-apps/toc.yml

@@ -3,7 +3,7 @@ title: Create your first function in the Azure portal
 description: Learn how to create your first Azure Function for serverless execution using the Azure portal.
 ms.assetid: 96cf87b9-8db6-41a8-863a-abb828e3d06d
 ms.topic: quickstart
-ms.date: 03/26/2020
+ms.date: 03/06/2020
 ms.custom: mvc, devcenter, cc996988-fb4f-47
 ---
 
@@ -29,37 +29,35 @@ Next, create a function in the new function app.
 
 ## <a name="create-function"></a>Create an HTTP triggered function
 
-1. From the left menu of the **Functions** window, select **Functions**, then select **Add** from the top menu. 
- 
-1. From the **New Function** window, select **Http trigger**.
+1. Expand your new function app, select the **+** button next to **Functions**, choose **In-portal**, and then select **Continue**.
 
-    ![Choose HTTP trigger function](./media/functions-create-first-azure-function/function-app-select-http-trigger.png)
+    ![Functions quickstart for choosing a platform.](./media/functions-create-first-azure-function/function-app-quickstart-choose-portal.png)
 
-1. In the **New Function** window, accept the default name for **New Function**, or enter a new name. 
+1. Choose **WebHook + API**, and then select **Create**.
 
-1. Choose **Anonymous** from the **Authorization level** drop-down list, and then select **Create Function**.
+    ![Functions quickstart in the Azure portal.](./media/functions-create-first-azure-function/function-app-quickstart-node-webhook.png)
 
-    Azure creates the HTTP trigger function. Now, you can run the new function by sending an HTTP request.
+   A function is created using a language-specific template for an HTTP triggered function.
 
-## Test the function
+Now, you can run the new function by sending an HTTP request.
 
-1. In your new HTTP trigger function, select **Code + Test** from the left menu, then select **Get function URL** from the top menu.
+## Test the function
 
-    ![Select Get function URL](./media/functions-create-first-azure-function/function-app-select-get-function-url.png)
+1. In your new function, select **</> Get function URL** at the top right. 
 
-1. In the **Get function URL** dialog box, select **default** from the drop-down list, and then select the **Copy to clipboard** icon. 
+1. In the **Get function URL** dialog box, select **default (Function key)** from the drop-down list, and then select **Copy**. 
 
     ![Copy the function URL from the Azure portal](./media/functions-create-first-azure-function/function-app-develop-tab-testing.png)
 
-1. Paste the function URL into your browser's address bar. Add the query string value `?name=<your_name>` to the end of this URL and press Enter to run the request. 
+1. Paste the function URL into your browser's address bar. Add the query string value `&name=<your_name>` to the end of this URL and press Enter to run the request. 
 
     The following example shows the response in the browser:
 
     ![Function response in the browser.](./media/functions-create-first-azure-function/function-app-browser-testing.png)
 
     The request URL includes a key that is required, by default, to access your function over HTTP.
 
-1. When your function runs, trace information is written to the logs. To see the trace output, return to the **Code + Test** page in the portal and expand the **Logs** arrow at the bottom of the page.
+1. When your function runs, trace information is written to the logs. To see the trace output from the previous execution, return to your function in the portal and select the arrow at the bottom of the screen to expand the **Logs**.
 
    ![Functions log viewer in the Azure portal.](./media/functions-create-first-azure-function/function-view-logs.png)
 

articles/active-directory/saas-apps/wdesk-tutorial.md

@@ -1,6 +1,6 @@
 ---
 title: "Quickstart: Create your first function in Azure using Visual Studio"
-description: In this quickstart, you learn how to create and publish an HTTP trigger Azure Function by using Visual Studio.
+description: In this quickstart, you learn how to create and publish an HTTP-triggered Azure Function by using Visual Studio.
 ms.assetid: 82db1177-2295-4e39-bd42-763f6082e796
 ms.topic: quickstart
 ms.date: 03/06/2020
@@ -10,7 +10,7 @@ ms.custom: mvc, devcenter, vs-azure, 23113853-34f2-4f
 
 Azure Functions lets you run your code in a serverless environment without having to first create a VM or publish a web application.
 
-In this quickstart, you learn how to use Visual Studio 2019 to locally create and test a "hello world" HTTP trigger C# function app, which you then publish to Azure. 
+In this quickstart, you learn how to use Visual Studio 2019 to locally create and test a "hello world" HTTP-triggered C# function app, which you then publish to Azure. 
 
 ![Function localhost response in the browser](./media/functions-create-your-first-function-visual-studio/functions-create-your-first-function-visual-studio-browser-local-final.png)
 
@@ -32,7 +32,7 @@ Visual Studio creates a project and class that contains boilerplate code for the
 
 Expand the capabilities of your function with input and output bindings by applying the appropriate attributes to the method. For more information, see the [Triggers and bindings](functions-dotnet-class-library.md#triggers-and-bindings) section of the [Azure Functions C# developer reference](functions-dotnet-class-library.md).
 
-Now that you've created your function project and an HTTP trigger function, you can test it on your local computer.
+Now that you've created your function project and an HTTP-triggered function, you can test it on your local computer.
 
 ## Run the function locally
 
@@ -52,7 +52,7 @@ Before you can publish your project, you must have a function app in your Azure
 
 1. Copy the base URL of the function app from the **Publish** profile page. Replace the `localhost:port` portion of the URL you used to test the function locally with the new base URL. Append the query string `?name=<YOUR_NAME>` to this URL and run the request.
 
-    The URL that calls your HTTP trigger function is in the following format:
+    The URL that calls your HTTP triggered function is in the following format:
 
     `http://<APP_NAME>.azurewebsites.net/api/<FUNCTION_NAME>?name=<YOUR_NAME>`
 
@@ -66,7 +66,7 @@ Before you can publish your project, you must have a function app in your Azure
 
 ## Next steps
 
-In this quickstart, you used Visual Studio to create and publish a C# function app in Azure with a simple HTTP trigger function. 
+In this quickstart, you used Visual Studio to create and publish a C# function app in Azure with a simple HTTP triggered function. 
 
 Advance to the next article to learn how to add an Azure Storage queue binding to your function:
 > [!div class="nextstepaction"]

articles/azure-functions/functions-create-first-azure-function.md

@@ -105,7 +105,7 @@ Even with Always On enabled, the execution timeout for individual functions is c
 
 ## Determine the hosting plan of an existing application
 
-To determine the hosting plan used by your function app, see **App Service plan** in the **Overview** tab for the function app in the [Azure portal](https://portal.azure.com). To see the pricing tier, select the name of the **App Service Plan**, and then select **Properties** from the left pane.
+To determine the hosting plan used by your function app, see **App Service plan / pricing tier** in the **Overview** tab for the function app in the [Azure portal](https://portal.azure.com). For App Service plans, the pricing tier is also indicated.
 
 ![View scaling plan in the portal](./media/functions-scale/function-app-overview-portal.png)
 
@@ -120,7 +120,7 @@ When the output from this command is `dynamic`, your function app is in the Cons
 
 ## Storage account requirements
 
-On any plan, a function app requires a general Azure Storage account, which supports Azure Blob, Queue, Files, and Table storage. This is because Azure Functions relies on Azure Storage for operations such as managing triggers and logging function executions, but some storage accounts do not support queues and tables. These accounts, which include blob-only storage accounts (including premium storage) and general-purpose storage accounts with zone-redundant storage replication, are filtered-out from your existing **Storage Account** selections when you create a function app.
+On any plan, a function app requires a general Azure Storage account, which supports Azure Blob, Queue, Files, and Table storage. This is because Functions relies on Azure Storage for operations such as managing triggers and logging function executions, but some storage accounts do not support queues and tables. These accounts, which include blob-only storage accounts (including premium storage) and general-purpose storage accounts with zone-redundant storage replication, are filtered-out from your existing **Storage Account** selections when you create a function app.
 
 The same storage account used by your function app can also be used by your triggers and bindings to store your application data. However, for storage-intensive operations, you should use a separate storage account.  
 
@@ -130,7 +130,7 @@ It's certainly possible for multiple function apps to share the same storage acc
 
 To learn more about storage account types, see [Introducing the Azure Storage services](../storage/common/storage-introduction.md#azure-storage-services).
 
-## How the Consumption and Premium plans work
+## How the consumption and premium plans work
 
 In the Consumption and Premium plans, the Azure Functions infrastructure scales CPU and memory resources by adding additional instances of the Functions host, based on the number of events that its functions are triggered on. Each instance of the Functions host in the Consumption plan is limited to 1.5 GB of memory and one CPU.  An instance of the host is the entire function app, meaning all functions within a function app share resource within an instance and scale at the same time. Function apps that share the same Consumption plan are scaled independently.  In the Premium plan, your plan size will determine the available memory and CPU for all apps in that plan on that instance.  
 
@@ -158,7 +158,7 @@ Scaling can vary on a number of factors, and scale differently based on the trig
 
 There are many aspects of a function app that will impact how well it will scale, including host configuration, runtime footprint, and resource efficiency.  For more information, see the [scalability section of the performance considerations article](functions-best-practices.md#scalability-best-practices). You should also be aware of how connections behave as your function app scales. For more information, see [How to manage connections in Azure Functions](manage-connections.md).
 
-For more information on scaling in Python and Node.js, see [Azure Functions Python developer guide - Scaling and concurrency](functions-reference-python.md#scaling-and-concurrency) and [Azure Functions Node.js developer guide - Scaling and concurrency](functions-reference-node.md#scaling-and-concurrency).
+For additional information on scaling in Python and Node.js, see [Azure Functions Python developer guide - Scaling and concurrency](functions-reference-python.md#scaling-and-concurrency) and [Azure Functions Node.js developer guide - Scaling and concurrency](functions-reference-node.md#scaling-and-concurrency).
 
 ### Billing model