Merge pull request #236130 from MicrosoftDocs/main

4/27 AM Publish

Author: huypub

articles/active-directory/devices/troubleshoot-mac-sso-extension-plugin.md

@@ -77,7 +77,7 @@ Use the following steps to check the operating system (OS) version on the macOS
 1. From the macOS device, open Terminal from the **Applications** -> **Utilities** folder.
 1. When the Terminal opens type **sw_vers** at the prompt, look for a result like the following:
 
-   ```bash
+   ```zsh
    % sw_vers
    ProductName: macOS
    ProductVersion: 13.0.1
@@ -194,7 +194,7 @@ Once deployed the **Microsoft Enterprise SSO Extension for Apple devices** suppo
 1. When the **Spotlight Search** appears type **Terminal** and hit **return**.
 1. When the Terminal opens type **`osascript -e 'id of app "<appname>"'`** at the prompt. See some examples follow:
 
-   ```bash
+   ```zsh
    % osascript -e 'id of app "Safari"'
    com.apple.Safari
 
@@ -294,14 +294,14 @@ During troubleshooting it may be useful to reproduce a problem while tailing the
 1. When the **Spotlight Search** appears type: **Terminal** and hit **return**.
 1. When the Terminal opens type: 
 
-   ```bash
+   ```zsh
    tail -F ~/Library/Containers/com.microsoft.CompanyPortalMac.ssoextension/Data/Library/Caches/Logs/Microsoft/SSOExtension/*
    ```
 
    > [!NOTE]
    > The trailing /* indicates that multiple logs will be tailed should any exist
 
-   ```
+   ```output
    % tail -F ~/Library/Containers/com.microsoft.CompanyPortalMac.ssoextension/Data/Library/Caches/Logs/Microsoft/SSOExtension/*
    ==> /Users/<username>/Library/Containers/com.microsoft.CompanyPortalMac.ssoextension/Data/Library/Caches/Logs/Microsoft/SSOExtension/SSOExtension 2022-12-25--13-11-52-855.log <==
    2022-12-29 14:49:59:281 | I | TID=783491 MSAL 1.2.4 Mac 13.0.1 [2022-12-29 19:49:59] Handling SSO request, requested operation: 

articles/active-directory/external-identities/code-samples.md

@@ -37,14 +37,14 @@ You can bulk-invite external users to an organization from email addresses that
 
 3. Sign in to your tenancy
 
-    ```powershell
+    ```azurepowershell-interactive
     $cred = Get-Credential
     Connect-AzureAD -Credential $cred
     ```
 
 4. Run the PowerShell cmdlet
 
-   ```powershell
+   ```azurepowershell-interactive
    $invitations = import-csv C:\data\invitations.csv
    $messageInfo = New-Object Microsoft.Open.MSGraph.Model.InvitedUserMessageInfo
    $messageInfo.customizedMessageBody = "Hey there! Check this out. I created an invitation through PowerShell"

articles/active-directory/fundamentals/multi-tenant-user-management-scenarios.md

@@ -165,13 +165,13 @@ This scenario requires automatic synchronization and identity management to conf
 
 This section describes three techniques for automating account provisioning in the automated scenario.
 
-#### Technique 1: Use the [built-in cross-tenant synchronization capability in Azure AD](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/seamless-application-access-and-lifecycle-management-for-multi/ba-p/3728752)
+#### Technique 1: Use the [built-in cross-tenant synchronization capability in Azure AD](../multi-tenant-organizations/cross-tenant-synchronization-overview.md)
 
 This approach only works when all tenants that you need to synchronize are in the same cloud instance (such as Commercial to Commercial).
 
 #### Technique 2: Provision accounts with Microsoft Identity Manager
 
-Use an external Identity and Access Management (IAM) solution such as [Microsoft Identity Manager](https://microsoft.sharepoint-df.com/microsoft-identity-manager/microsoft-identity-manager-2016) (MIM) as a synchronization engine.
+Use an external Identity and Access Management (IAM) solution such as [Microsoft Identity Manager](/microsoft-identity-manager/microsoft-identity-manager-2016) (MIM) as a synchronization engine.
 
 This advanced deployment uses MIM as a synchronization engine. MIM calls the [Microsoft Graph API](https://developer.microsoft.com/graph) and [Exchange Online PowerShell](/powershell/exchange/exchange-online/exchange-online-powershell?view=exchange-ps&preserve-view=true). Alternative implementations can include the cloud-hosted [Active Directory Synchronization Service](/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview) (ADSS) managed service offering from [Microsoft Industry Solutions](https://www.microsoft.com/industrysolutions). There are non-Microsoft offerings that you can create from scratch with other IAM offerings (such as SailPoint, Omada, and OKTA).
 

articles/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md

@@ -178,21 +178,21 @@ To use Azure PowerShell locally for this article instead of using Cloud Shell:
 
 1. Sign in to Azure.
 
-    ```azurepowershell
+    ```azurepowershell-interactive
     Connect-AzAccount
     ```
 
 1. Install the [latest version of PowerShellGet](/powershell/gallery/powershellget/install-powershellget).
 
-    ```azurepowershell
+    ```azurepowershell-interactive
     Install-Module -Name PowerShellGet -AllowPrerelease
     ```
 
     You might need to `Exit` out of the current PowerShell session after you run this command for the next step.
 
 1. Install the prerelease version of the `Az.ManagedServiceIdentity` module to perform the user-assigned managed identity operations in this article.
 
-    ```azurepowershell
+    ```azurepowershell-interactive
     Install-Module -Name Az.ManagedServiceIdentity -AllowPrerelease
     ```
 
@@ -330,7 +330,7 @@ In this article, you learn how to create, list, and delete a user-assigned manag
 
 1. If you're running locally, sign in to Azure through the Azure CLI.
 
-    ```
+    ```azurecli-interactive
     az login
     ```
 

articles/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm.md

@@ -132,7 +132,7 @@ To assign a user-assigned identity to a VM during its creation, your account nee
 3. Create a VM using [az vm create](/cli/azure/vm/#az-vm-create). The following example creates a VM associated with the new user-assigned identity, as specified by the `--assign-identity` parameter, with the specified `--role` and `--scope`. Be sure to replace the `<RESOURCE GROUP>`, `<VM NAME>`, `<USER NAME>`, `<PASSWORD>`, `<USER ASSIGNED IDENTITY NAME>`, `<ROLE>`, and `<SUBSCRIPTION>` parameter values with your own values. 
 
    ```azurecli-interactive 
-   az vm create --resource-group <RESOURCE GROUP> --name <VM NAME> --image UbuntuLTS --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY NAME> --role <ROLE> --scope <SUBSCRIPTION> 
+   az vm create --resource-group <RESOURCE GROUP> --name <VM NAME> --image <SKU linux image>  --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY NAME> --role <ROLE> --scope <SUBSCRIPTION> 
    ```
 
 ### Assign a user-assigned managed identity to an existing Azure VM

articles/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vmss.md

@@ -133,7 +133,7 @@ This section walks you through creation of a virtual machine scale set and assig
 3. [Create](/cli/azure/vmss/#az-vmss-create) a virtual machine scale set. The following example creates a virtual machine scale set associated with the new user-assigned managed identity, as specified by the `--assign-identity` parameter, with the specified `--role` and `--scope`. Be sure to replace the `<RESOURCE GROUP>`, `<VMSS NAME>`, `<USER NAME>`, `<PASSWORD>`, `<USER ASSIGNED IDENTITY>`, `<ROLE>`, and `<SUBSCRIPTION>` parameter values with your own values.
 
    ```azurecli-interactive
-   az vmss create --resource-group <RESOURCE GROUP> --name <VMSS NAME> --image UbuntuLTS --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY> --role <ROLE> --scope <SUBSCRIPTION>
+   az vmss create --resource-group <RESOURCE GROUP> --name <VMSS NAME> --image <SKU Linux Image> --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY> --role <ROLE> --scope <SUBSCRIPTION>
    ```
 
 ### Assign a user-assigned managed identity to an existing virtual machine scale set

articles/active-directory/managed-identities-azure-resources/tutorial-vm-managed-identities-cosmos.md

@@ -170,7 +170,7 @@ The user assigned managed identity should be specified using its [resourceID](./
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
-az vm create --resource-group <MyResourceGroup> --name <myVM> --image UbuntuLTS --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY NAME>
+az vm create --resource-group <MyResourceGroup> --name <myVM> --image <SKU Linux Image> --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY NAME>
 ```
 
 [Configure managed identities for Azure resources on a VM using the Azure CLI](qs-configure-cli-windows-vm.md#user-assigned-managed-identity)

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

@@ -2617,6 +2617,8 @@
         href: userecho-tutorial.md  
       - name: UserVoice
         href: uservoice-tutorial.md
+      - name: UserTesting
+        href: usertesting-saml-tutorial.md
       - name: UserZoom
         href: userzoom-tutorial.md
       - name: Valence Security Platform

articles/active-directory/saas-apps/usertesting-saml-tutorial.md

@@ -0,0 +1,118 @@
+---
+title: Azure Active Directory SSO integration with UserTesting
+description: Learn how to configure single sign-on between Azure Active Directory and UserTesting.
+services: active-directory
+author: jeevansd
+manager: CelesteDG
+ms.reviewer: CelesteDG
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: how-to
+ms.date: 04/26/2023
+ms.author: jeedes
+
+---
+
+# Azure Active Directory SSO integration with UserTesting
+
+In this article, you learn how to integrate UserTesting with Azure Active Directory (Azure AD). UserTesting is a platform for getting rapid customer feedback on almost any customer experience you can imagine, including websites, mobile apps, prototypes, and real world experiences. When you integrate UserTesting with Azure AD, you can:
+
+* Control in Azure AD who has access to UserTesting.
+* Enable your users to be automatically signed-in to UserTesting with their Azure AD accounts.
+* Manage your accounts in one central location - the Azure portal.
+
+You configure and test Azure AD single sign-on for UserTesting in a test environment. UserTesting supports **SP** and **IDP** initiated single sign-on.
+
+## Prerequisites
+
+To integrate Azure Active Directory with UserTesting, you need:
+
+* An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
+* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* UserTesting single sign-on (SSO) enabled subscription.
+
+## Add application and assign a test user
+
+Before you begin the process of configuring single sign-on, you need to add the UserTesting application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration.
+
+### Add UserTesting from the Azure AD gallery
+
+Add UserTesting from the Azure AD application gallery to configure single sign-on with UserTesting. For more information on how to add application from the gallery, see the [Quickstart: Add application from the gallery](../manage-apps/add-application-portal.md).
+
+### Create and assign Azure AD test user
+
+Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon.
+
+Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides). 
+
+## Configure Azure AD SSO
+
+Complete the following steps to enable Azure AD single sign-on in the Azure portal.
+
+1. In the Azure portal, on the **UserTesting** 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, select the pencil icon for **Basic SAML Configuration** to edit the settings.
+
+   ![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
+
+1. On the **Basic SAML Configuration** section, perform the following steps:
+
+    a. In the **Identifier** textbox, type a URL using the following pattern:
+    `https://www.okta.com/saml2/service-provider/<Account_Name>`
+
+    b. In the **Reply URL** textbox, type a URL using the following pattern:
+    ` https://auth.usertesting.com/sso/saml2/<ID>`
+
+1. If you wish to configure the application in **SP** initiated mode, then perform the following step:
+
+    a. In the **Sign on URL** textbox, type the URL:
+    `https://app.usertesting.com/users/sso_sign_in`
+
+    b.In the **Relay State** textbox, type the URL:
+    `https://app.usertesting.com/sessions/from_idp`
+
+     > [!NOTE]
+    > These values are not real. Update these values with the actual Identifier and Reply URL. Contact [UserTesting 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, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
+
+    ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
+
+1. On the **Set up UserTesting** section, copy the appropriate URL(s) based on your requirement.
+
+	![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
+
+## Configure UserTesting SSO
+
+To configure single sign-on on **UserTesting** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [UserTesting support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create UserTesting test user
+
+In this section, you create a user called Britta Simon at UserTesting. Work with [UserTesting support team](mailto:[email protected]) to add the users in the UserTesting 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 with following options. 
+
+#### SP initiated:
+
+* Click on **Test this application** in Azure portal. This will redirect to UserTesting Sign-on URL where you can initiate the login flow.  
+
+* Go to UserTesting Sign-on URL directly and initiate the login flow from there.
+
+#### IDP initiated:
+
+* Click on **Test this application** in Azure portal and you should be automatically signed in to the UserTesting for which you set up the SSO. 
+
+You can also use Microsoft My Apps to test the application in any mode. When you click the UserTesting tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the UserTesting for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
+
+## Additional resources
+
+* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
+
+## Next steps
+
+Once you configure UserTesting 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](/cloud-app-security/proxy-deployment-aad).

articles/active-directory/standards/index.yml

@@ -24,12 +24,12 @@ landingContent:
     linkLists:
       - linkListType: overview
         links:
-          - text: Configure to identity standards
-            url: standards-overview.md
           - text: NIST AAL overview
             url: nist-overview.md
           - text: FedRAMP High impact overview
             url: configure-azure-active-directory-for-fedramp-high-impact.md
+          - text: Configure Azure Active Directory for Memorandum 22-09 requirements
+            url: memo-22-09-meet-identity-requirements.md
           - text: Configure Azure Active Directory for CMMC compliance
             url: configure-azure-active-directory-for-cmmc-compliance.md
           - text: Configure Azure Active Directory for HIPAA compliance