Merge pull request #159317 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

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

@@ -28,11 +28,11 @@ To learn more about SaaS app integration with Azure AD, see [What is application
 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/).
-* Displayr single sign-on (SSO) enabled subscription.
+* Displayr single sign-on (SSO) enabled company.
 
 ## Scenario description
 
-In this tutorial, you configure and test Azure AD SSO in a test environment. Displayr supports **SP** initiated SSO.
+In this tutorial, you will learn to configure Azure AD SSO in your Displayr company. Displayr supports **SP** initiated SSO.
 
 ## Adding Displayr from the gallery
 
@@ -45,17 +45,13 @@ To configure the integration of Displayr into Azure AD, you need to add Displayr
 1. In the **Add from the gallery** section, type **Displayr** in the search box.
 1. Select **Displayr** 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
+## Configure Azure AD single sign-on
 
-Configure and test Azure AD SSO with Displayr using a test user called **Britta Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Displayr.
-
-To configure and test Azure AD SSO with Displayr, complete the following building blocks:
+To configure Azure AD SSO with Displayr, complete the following building blocks:
 
 1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** to enable your users to use this feature.
 2. **[Configure Displayr](#configure-displayr)** to configure the SSO settings on application side.
-3. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** to test Azure AD single sign-on with Britta Simon.
-4. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** to enable Britta Simon to use Azure AD single sign-on.
-5. **[Create Displayr test user](#create-displayr-test-user)** to have a counterpart of Britta Simon in Displayr that is linked to the Azure AD representation of user.
+4. **[Restrict access to specific users](#restrict-access-to-specific-users)** to restrict which of your Azure AD users can sign in to Displayr.
 6. **[Test SSO](#test-sso)** to verify whether the configuration works.
 
 ### Configure Azure AD SSO
@@ -100,10 +96,6 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
    c. Select **Source Attribute** of **Group ID**.
 
-   d. Check **Customize the name of the group claim**.
-
-   e. Check **Emit groups as role claims**.
-
    f. Click **Save**.
 
 1. On the **Set-up Displayr** section, copy the appropriate URL(s) based on your requirement.
@@ -122,11 +114,11 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 3. If you want to set up Displayr manually, open a new web browser window and sign into your Displayr company site as an administrator and perform the following steps:
 
-4. Click on **Settings** then navigate to **Account**.
+4. Click on the **User** icon, then navigate to **Account settings**.
 
 	![Screenshot that shows the "Settings" icon and "Account" selected.](./media/displayr-tutorial/config01.png)
 
-5. Switch to **Settings** from the top menu and scroll down the page for clicking **Configure Single Sign On (SAML)**.
+5. Switch to **Settings** from the top menu and scroll down the page to click on **Configure Single Sign On (SAML)**.
 
 	![Screenshot that shows the "Settings" tab selected and the "Configure Single Sign On (S A M L)" action selected.](./media/displayr-tutorial/config02.png)
 
@@ -148,67 +140,13 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 	g. Click **Save**.	
 
-### Create an Azure AD test user
-
-In this section, you'll create a test user in the Azure portal called Britta 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 `Britta 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 Britta Simon to use Azure single sign-on by granting access to Displayr.
-
-1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
-1. In the applications list, select **Displayr**.
-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 **Britta 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.
-
-### Create Displayr test user
+### Restrict access to specific users
 
-To enable Azure AD users, sign in to Displayr, they must be provisioned into Displayr. In Displayr, provisioning is a manual task.
-
-**To provision a user account, perform the following steps:**
-
-1. Sign in to Displayr as an Administrator.
-
-2. Click on **Settings** then navigate to **Account**.
-
-	![Screenshot that shows the "Settings (cog)" icon with "Account" selected.](./media/displayr-tutorial/config01.png)
-
-3. Switch to **Settings** from the top menu and scroll down the page, until **Users** section then click on **New User**.
-
-	![Screenshot that shows the "Settings" tab with "Users" highlighted and the "New User" button selected.](./media/displayr-tutorial/config07.png)
-
-4. On the **New User** page, perform the following steps:
-
-	![Displayr Configuration](./media/displayr-tutorial/config06.png)
-
-	a. In **Name** text box, enter the name of user like **Brittasimon**.
-
-	b. In **Email** text box, enter the email of user like `[email protected]`.
-
-	c. Select your appropriate **Group membership**.
-
-	d. Click **Save**.
+By default, all users in the tenant where you added the Displayr application can log in to Displayr by using SSO. If you want to restrict access to specific users or groups, see [Restrict your Azure AD app to a set of users in an Azure AD tenant](../develop/howto-restrict-your-app-to-a-set-of-users.md).
 
 ### Test SSO
 
-When you select the Displayr tile in the Access Panel, you should be automatically signed in to the Displayr for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](../user-help/my-apps-portal-end-user-access.md).
+When you select the Displayr tile in the Access Panel, you should be automatically signed in to the Displayr company for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](../user-help/my-apps-portal-end-user-access.md).
 
 ## Additional Resources
 

articles/active-directory/saas-apps/media/displayr-tutorial/config01.png

@@ -40,16 +40,14 @@ To ensure you apply the correct update package to your dev kit, you must first d
 Using the **model** and **swVersion** identified in the previous section, check the table below to determine which update package to download.
 
 
-|model  |swVersion  |Update method  |Download links  |
-|---------|---------|---------|---------|
-|PE-101     |2020.108.101.105, <br>2020.108.114.120, <br>2020.109.101.122, <br>2020.109.116.120, <br>2021.101.106.118        |**USB only**         |[USB update package](https://go.microsoft.com/fwlink/?linkid=2155734)         |
-|PE-101     |2021.102.108.112, <br>         |OTA or USB        |[OTA manifest](https://go.microsoft.com/fwlink/?linkid=2155625)<br>[OTA update package](https://go.microsoft.com/fwlink/?linkid=2161538)<br>[USB update package](https://go.microsoft.com/fwlink/?linkid=2155734)          |
-|APDK-101     |All swVersions        |OTA or USB       | [OTA manifest](https://go.microsoft.com/fwlink/?linkid=2162292)<br>[OTA update package](https://go.microsoft.com/fwlink/?linkid=2161538)<br>[USB update package](https://go.microsoft.com/fwlink/?linkid=2155734)        |
-
+|model  |swVersion  |Update method  |Download links  |Note  |
+|---------|---------|---------|---------|---------|
+|PE-101     |2020.108.101.105, <br>2020.108.114.120, <br>2020.109.101.122, <br>2020.109.116.120, <br>2021.101.106.118        |**USB only**         |[2021.104.110.103 USB update package](https://go.microsoft.com/fwlink/?linkid=2155734)         |Public Preview major release         |
+|PE-101     |2021.102.108.112, <br>         |OTA or USB        |[2021.104.110.103 OTA manifest](https://go.microsoft.com/fwlink/?linkid=2155625)<br>[2021.104.110.103 OTA update package](https://go.microsoft.com/fwlink/?linkid=2161538)<br>[2021.104.110.103 USB update package](https://go.microsoft.com/fwlink/?linkid=2155734)          |Public Preview major release         |
+|APDK-101     |All swVersions        |OTA or USB       | [2021.105.111.112 OTA manifest](https://go.microsoft.com/fwlink/?linkid=2163554)<br>[2021.105.111.112 OTA update package](https://go.microsoft.com/fwlink/?linkid=2163456)<br>[2021.105.111.112 USB update package](https://go.microsoft.com/fwlink/?linkid=2163555)        |Latest monthly release (May)         |
 
 
 ## Next steps
 Update your dev kits via the methods and update packages determined in the previous section.
 - [Update your Azure Percept DK over-the-air](https://docs.microsoft.com/azure/azure-percept/how-to-update-over-the-air)
 - [Update your Azure Percept DK via USB](https://docs.microsoft.com/azure/azure-percept/how-to-update-via-usb)
-

articles/active-directory/saas-apps/media/displayr-tutorial/config04.png

@@ -361,6 +361,8 @@ The latest values for Azure Purview quotas can be found in the [Azure Purview qu
 
 For SQL Database limits, see [SQL Database resource limits for single databases](../../azure-sql/database/resource-limits-vcore-single-databases.md), [SQL Database resource limits for elastic pools and pooled databases](../../azure-sql/database/resource-limits-vcore-elastic-pools.md), and [SQL Database resource limits for SQL Managed Instance](../../azure-sql/managed-instance/resource-limits.md).
 
+The maximum number of private endpoints per Azure SQL Database logical server is 250.
+
 ## Azure Synapse Analytics limits
 
 [!INCLUDE [synapse-analytics-limits](../../../includes/synapse-analytics-limits.md)]

articles/active-directory/saas-apps/media/displayr-tutorial/config05.png

@@ -18,6 +18,6 @@ Go to the Azure portal and <a href="https://ms.portal.azure.com/#create/Microsof
 | **Pricing tier** | The cost of your resource depends on the pricing tier you choose and your usage. For more information, see the API [pricing details](https://azure.microsoft.com/pricing/details/cognitive-services/).
 
 > [!NOTE]
-> When you create a Cognitive Service resource in the Azure portal, you have the option to create a multi-service subscription key (used across multiple cognitive services) or a single-service subscription key (used only with a specific cognitive service). Currently, Form Recognizer is not included in the multi-service subscription.
+> When you create a Cognitive Service resource in the Azure portal, you have the option to create a multi-service subscription key (used across multiple Cognitive Services) or a single-service subscription key (used only with a specific Cognitive Service). Currently, Form Recognizer is not included in the multi-service subscription.
 
 When your Form Recognizer resource finishes deploying, find and select it from the **All resources** list in the portal. Your key and endpoint will be located on the resource's key and endpoint page, under resource management. Save both of these to a temporary location before going forward.

articles/active-directory/saas-apps/media/displayr-tutorial/config06.png

@@ -150,7 +150,7 @@ To configure environment variables, such as `JEKYLL_ENV`, add an `env` section t
       # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig
       app_location: "/" # App source code path
       api_location: "" # Api source code path - optional
-      output_location: "_site_" # Built app content directory - optional
+      output_location: "_site" # Built app content directory - optional
       ###### End of Repository/Build Configurations ######
    env:
       JEKYLL_ENV: production