Merge pull request #127638 from MicrosoftDocs/master

8/28 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -40043,6 +40043,26 @@
       "redirect_url": "/azure/cognitive-services/speech-service/custom-keyword-overview",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/cognitive-services/Speech-Service/speech-translation-basics.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/get-started-speech-translation",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/cognitive-services/Speech-Service/translate-speech-to-speech.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/get-started-speech-translation",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cognitive-services/Speech-Service/translate-speech-to-text.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/get-started-speech-translation",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cognitive-services/Speech-Service/translate-speech-to-text-multiple-languages.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/get-started-speech-translation",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cognitive-services/LUIS/luis-get-started-ruby-get-intent.md",
       "redirect_url": "/azure/cognitive-services/LUIS/",
@@ -56329,6 +56349,11 @@
       "redirect_url": "how-to-upload-media?tabs=rest",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/cognitive-services/personalizer/sdk-learning-loop.md",
+      "redirect_url": "/azure/cognitive-services/personalizer/quickstart-personalizer-sdk",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/service-fabric/service-fabric-scale-up-node-type.md",
       "redirect_url": "/azure/service-fabric/service-fabric-scale-up-primary-node-type",

articles/active-directory/authentication/howto-mfa-getstarted.md

@@ -107,7 +107,7 @@ We recommend that organizations use Conditional Access to define their network u
 Administrators can choose the [authentication methods](../authentication/concept-authentication-methods.md) that they want to make available for users. It is important to allow more than a single authentication method so that users have a backup method available in case their primary method is unavailable. The following methods are available for administrators to enable:
 
 > [!TIP]
-> Microsoft recommends using the mobile app as the primary method for Azure Multi-Factor Authentication for the best security and user experience.
+> Microsoft recommends using the Microsoft Authenticator (mobile app) as the primary method for Azure Multi-Factor Authentication for a more secure and improved user experience. The Microsoft Authenticator app also [meets](https://azure.microsoft.com/resources/microsoft-nist/) the National Institute of Standards and Technology Authenticator Assurance Levels. 
 
 ### Notification through mobile app
 
@@ -367,4 +367,4 @@ Find solutions for common issues with Azure MFA at the [Troubleshooting Azure Mu
 To see Azure Multi-Factor Authentication in action, complete the following tutorial:
 
 > [!div class="nextstepaction"]
-> [Enable Azure Multi-Factor Authentication](tutorial-enable-azure-mfa.md)
+> [Enable Azure Multi-Factor Authentication](tutorial-enable-azure-mfa.md)

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

@@ -0,0 +1,148 @@
+---
+title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Eventfinity | Microsoft Docs'
+description: Learn how to configure single sign-on between Azure Active Directory and Eventfinity.
+services: active-directory
+author: jeevansd
+manager: CelesteDG
+ms.reviewer: celested
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: tutorial
+ms.date: 08/28/2020
+ms.author: jeedes
+---
+
+# Tutorial: Azure Active Directory single sign-on (SSO) integration with Eventfinity
+
+In this tutorial, you'll learn how to integrate Eventfinity with Azure Active Directory (Azure AD). When you integrate Eventfinity with Azure AD, you can:
+
+* Control in Azure AD who has access to Eventfinity.
+* Enable your users to be automatically signed-in to Eventfinity with their Azure AD accounts.
+* Manage your accounts in one central location - the Azure portal.
+
+To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on).
+
+## Prerequisites
+
+To get started, you need the following items:
+
+* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* Eventfinity single sign-on (SSO) enabled subscription.
+
+## Scenario description
+
+In this tutorial, you configure and test Azure AD SSO in a test environment.
+
+* Eventfinity supports **SP and IDP** initiated SSO
+* Once you configure Eventfinity you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app).
+
+> [!NOTE]
+> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
+
+## Adding Eventfinity from the gallery
+
+To configure the integration of Eventfinity into Azure AD, you need to add Eventfinity from the gallery to your list of managed SaaS apps.
+
+1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
+1. On the left navigation pane, select the **Azure Active Directory** service.
+1. Navigate to **Enterprise Applications** and then select **All Applications**.
+1. To add new application, select **New application**.
+1. In the **Add from the gallery** section, type **Eventfinity** in the search box.
+1. Select **Eventfinity** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
+
+
+## Configure and test Azure AD single sign-on for Eventfinity
+
+Configure and test Azure AD SSO with Eventfinity using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Eventfinity.
+
+To configure and test Azure AD SSO with Eventfinity, complete the following building blocks:
+
+1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
+    1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
+    1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
+1. **[Configure Eventfinity SSO](#configure-eventfinity-sso)** - to configure the single sign-on settings on application side.
+    1. **[Create Eventfinity test user](#create-eventfinity-test-user)** - to have a counterpart of B.Simon in Eventfinity that is linked to the Azure AD representation of user.
+1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
+
+## Configure Azure AD SSO
+
+Follow these steps to enable Azure AD SSO in the Azure portal.
+
+1. In the [Azure portal](https://portal.azure.com/), on the **Eventfinity** application integration page, find the **Manage** section and select **single sign-on**.
+1. On the **Select a single sign-on method** page, select **SAML**.
+1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
+
+   ![Edit Basic SAML Configuration](common/edit-urls.png)
+
+1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, enter the values for the following fields:
+
+    In the **Reply URL** text box, type a URL using the following pattern:
+    `https://auth.eventfinity.co/saml/<ID>/acs`
+
+1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
+
+    In the **Sign-on URL** text box, type a URL using the following pattern:
+    `https://auth.eventfinity.co/saml/<ID>/sso`
+
+	> [!NOTE]
+	> These values are not real. Update these values with the actual Reply URL and Sign-On URL. Contact [Eventfinity Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+
+1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
+
+	![The Certificate download link](common/copy-metadataurl.png)
+### Create an Azure AD test user
+
+In this section, you'll create a test user in the Azure portal called B.Simon.
+
+1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
+1. Select **New user** at the top of the screen.
+1. In the **User** properties, follow these steps:
+   1. In the **Name** field, enter `B.Simon`.  
+   1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
+   1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
+   1. Click **Create**.
+
+### Assign the Azure AD test user
+
+In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Eventfinity.
+
+1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
+1. In the applications list, select **Eventfinity**.
+1. In the app's overview page, find the **Manage** section and select **Users and groups**.
+
+   ![The "Users and groups" link](common/users-groups-blade.png)
+
+1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
+
+	![The Add User link](common/add-assign-user.png)
+
+1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
+1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
+1. In the **Add Assignment** dialog, click the **Assign** button.
+
+## Configure Eventfinity SSO
+
+To configure single sign-on on **Eventfinity** side, you need to send the **App Federation Metadata Url** to [Eventfinity support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create Eventfinity test user
+
+In this section, you create a user called B.Simon in Eventfinity. Work with [Eventfinity support team](mailto:[email protected]) to add the users in the Eventfinity platform. Users must be created and activated before you use single sign-on.
+
+## Test SSO 
+
+In this section, you test your Azure AD single sign-on configuration using the Access Panel.
+
+When you click the Eventfinity tile in the Access Panel, you should be automatically signed in to the Eventfinity for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
+
+## Additional resources
+
+- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
+
+- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
+
+- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
+
+- [Try Eventfinity with Azure AD](https://aad.portal.azure.com/)
+
+- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)

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

@@ -555,6 +555,8 @@
         href: ethicspoint-incident-management-tutorial.md
       - name: Euromonitor Passport
         href: euromonitor-passport-tutorial.md
+      - name: Eventfinity
+        href: eventfinity-tutorial.md
       - name: EverBridge
         href: everbridge-tutorial.md
       - name: Evernote

articles/aks/node-image-upgrade.md

@@ -16,6 +16,10 @@ If you're interested in learning about the latest images provided by AKS, see th
 
 For information on upgrading the Kubernetes version for your cluster, see [Upgrade an AKS cluster][upgrade-cluster].
 
+## Limitations
+
+* The AKS cluster must use virtual machine scale sets for the nodes.
+
 ## Install the AKS CLI Extension
 
 Before the next core CLI version is released, you need the *aks-preview* CLI extension to use node image upgrade. Use the [az extension add][az-extension-add] command, and then check for any available updates using the [az extension update][az-extension-update] command:

articles/automation/quickstart-create-automation-account-template.md

@@ -56,7 +56,7 @@ The following table lists the API version for the resources used in this example
 |:---|:---|:---|
 | [Workspace](/azure/templates/microsoft.operationalinsights/workspaces) | workspaces | 2020-03-01-preview |
 | [Automation account](/azure/templates/microsoft.automation/automationaccounts) | automation | 2020-01-13-preview |
-| [Workspace Linked services](/azure/templates/microsoft.operationalinsights/workspaces/linkedservices) | worksapces | 2020-03-01-preview |
+| [Workspace Linked services](/azure/templates/microsoft.operationalinsights/workspaces/linkedservices) | workspaces | 2020-03-01-preview |
 
 ### Before you use the template
 
@@ -123,4 +123,4 @@ In this quickstart, you created an Automation account, a Log Analytics workspace
 To learn more, continue to the tutorials for Azure Automation.
 
 > [!div class="nextstepaction"]
-> [Azure Automation tutorials](learn/automation-tutorial-runbook-graphical.md)
+> [Azure Automation tutorials](learn/automation-tutorial-runbook-graphical.md)

articles/azure-arc/data/breadcrumb/toc.yml

@@ -3,9 +3,9 @@
   topicHref: /azure/index
   items:
   - name: Azure Arc
-    tocHref: /azure-arc/
-    topicHref: /azure-arc/index
+    tocHref: /azure/azure-arc/
+    topicHref: /azure/azure-arc/index
     items:
     - name: Data
       tocHref: /sql/azdata/
-      topicHref: /azure-arc/data/index
+      topicHref: /azure/azure-arc/data/index

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

@@ -178,15 +178,38 @@ To define the data type for an input binding, use the `dataType` property in the
 Options for `dataType` are: `binary`, `stream`, and `string`.
 
 ## context object
-The runtime uses a `context` object to pass data to and from your function and to let you communicate with the runtime. The context object can be used for reading and setting data from bindings, writing logs, and using the `context.done` callback when your exported function is synchronous.
 
-The `context` object is always the first parameter to a function. It should be included because it has important methods such as `context.done` and `context.log`. You can name the object whatever you would like (for example, `ctx` or `c`).
+The runtime uses a `context` object to pass data to and from your function and the runtime. Used to read and set data from bindings and for writing to logs, the `context` object is always the first parameter passed to a function.
+
+For functions featuring synchronous code, the context object includes the `done` callback which you call when the function is done processing. Explicitly calling `done` is unnecessary when writing asynchronous code; the `done` callback is called implicitly.
 
 ```javascript
-// You must include a context, but other arguments are optional
-module.exports = function(ctx) {
-    // function logic goes here :)
-    ctx.done();
+module.exports = (context) => {
+
+    // function logic goes here
+
+    context.log("The function has executed.");
+
+    context.done();
+};
+```
+
+The context passed into your function exposes an `executionContext` property, which is an object with the following properties:
+
+| Property name  | Type  | Description |
+|---------|---------|---------|
+| `invocationId` | String | Provides a unique identifier for the specific function invocation. |
+| `functionName` | String | Provides the name of the running function |
+| `functionDirectory` | String | Provides the functions app directory. |
+
+The following example shows how to return the `invocationId`.
+
+```javascript
+module.exports = (context, req) => {
+    context.res = {
+        body: context.executionContext.invocationId
+    };
+    context.done();
 };
 ```
 

articles/azure-monitor/learn/dotnetcore-quick-start.md

@@ -100,7 +100,7 @@ Application Insights can gather telemetry data from any internet-connected appli
 When you are done testing, you can delete the resource group and all related resources. To do so follow the steps below.
 
 > [!NOTE]
-> If you used an existing resource group the instructions below will not work and you will need to just delete the individual Application Insights resource. Keep in mind anytime you delete a resource group all underyling resources that are members of that group will be deleted.
+> If you used an existing resource group the instructions below will not work and you will need to just delete the individual Application Insights resource. Keep in mind anytime you delete a resource group all underlying resources that are members of that group will be deleted.
 
 1. From the left-hand menu in the Azure portal, click **Resource groups** and then click **myResourceGroup**.
 2. On your resource group page, click **Delete**, type **myResourceGroup** in the text box, and then click **Delete**.

articles/azure-sql/database/auto-failover-group-overview.md

@@ -11,7 +11,7 @@ ms.topic: conceptual
 author: anosov1960
 ms.author: sashan
 ms.reviewer: mathoma, carlrab
-ms.date: 07/09/2020
+ms.date: 08/28/2020
 ---
 
 # Use auto-failover groups to enable transparent and coordinated failover of multiple databases
@@ -252,7 +252,7 @@ When performing OLTP operations, use `<fog-name>.zone_id.database.windows.net` a
 
 ### Using read-only listener to connect to the secondary instance
 
-If you have a logically isolated read-only workload that is tolerant to certain staleness of data, you can use the secondary database in the application. To connect directly to the geo-replicated secondary, use `server.secondary.zone_id.database.windows.net` as the server URL and the connection is made directly to the geo-replicated secondary.
+If you have a logically isolated read-only workload that is tolerant to certain staleness of data, you can use the secondary database in the application. To connect directly to the geo-replicated secondary, use `<fog-name>.zone_id.secondary.database.windows.net` as the server URL and the connection is made directly to the geo-replicated secondary.
 
 > [!NOTE]
 > In certain service tiers, SQL Database supports the use of [read-only replicas](read-scale-out.md) to load balance read-only query workloads using the capacity of one read-only replica and using the `ApplicationIntent=ReadOnly` parameter in the connection string. When you have configured a geo-replicated secondary, you can use this capability to connect to either a read-only replica in the primary location or in the geo-replicated location.