Merge pull request #183472 from MicrosoftDocs/master

12/21 PM Publishing

Author: v-alje

articles/active-directory/develop/active-directory-saml-claims-customization.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
 ms.topic: how-to
-ms.date: 07/20/2021
+ms.date: 12/21/2021
 ms.author: kenwith
 ms.reviewer: luleon, paulgarn, jeedes
 ms.custom: aaddev
@@ -111,7 +111,8 @@ To apply a transformation to a user attribute:
 
 1. In **Manage claim**, select *Transformation* as the claim source to open the **Manage transformation** page.
 2. Select the function from the transformation dropdown. Depending on the function selected, you will have to provide parameters and a constant value to evaluate in the transformation. Refer to the table below for more information about the available functions.
-3. To apply multiple transformation, click on **Add transformation**.You can apply a maximum of two transformation to a claim. For example, you could first extract the email prefix of the `user.mail`. Then, make the string upper case.
+3. (preview ) `Treat source as multivalued` is a checkbox indicating if the transform should be applied to all values or just the first. By default, transformations will only be applied to the first element in a multi value claim, by checking this box it ensures it is applied to all. This checkbox will only be enabled for multi valued attributes, for example `user.proxyaddresses`.
+4. To apply multiple transformation, click on **Add transformation**. You can apply a maximum of two transformation to a claim. For example, you could first extract the email prefix of the `user.mail`. Then, make the string upper case.
 
    ![Multiple claims transformation](./media/active-directory-saml-claims-customization/sso-saml-multiple-claims-transformation.png)
 

articles/active-directory/governance/entitlement-management-logic-apps-integration.md

@@ -27,7 +27,7 @@ ms.collection: M365-identity-device-management
 
 These Logic Apps can then be triggered to run in accordance with entitlement management use cases such as when an access package is granted or requested. For example, an admin could create and link a custom Logic App to entitlement management so that when a user requests an access package, a Logic App is triggered that ensures the user is also assigned certain characteristics in a 3rd party SAAS app (like Salesforce) or is sent a custom email.
 
-entitlement management use cases that can be integrated with Logic Apps include:  
+Entitlement management use cases that can be integrated with Logic Apps include:  
 
 - when an access package is requested  
 
@@ -129,4 +129,4 @@ To verify that your custom extension has correctly triggered the associated Logi
 
 The overview page for a specific Logic App will show timestamps of when the Logic App was last executed. Also, the Resource Group overview for a resource group with a linked custom extension will show the name of that custom extension in the overview if it has been configured correctly.  
 
-## Next steps
+## Next steps

articles/active-directory/hybrid/reference-connect-version-history.md

@@ -58,6 +58,14 @@ Required permissions | For permissions required to apply an update, see [account
 >
 > Please follow this link to read more about [auto upgrade](how-to-connect-install-automatic-upgrade.md).
 
+## 2.0.89.0
+
+### Release status
+12/21/2021: Released for download only, not available for auto upgrade.
+
+### Bug fixes
+- We fixed a bug in version 2.0.88.0 where, under certain conditions, linked mailboxes of disabled users were getting deleted.
+
 ## 2.0.88.0
 > [!NOTE] 
 > This release requires Windows Server 2016 or newer. It fixes a vulnerability that is present in version 2.0 of Azure AD Connect, as well as some other bug fixes and minor feature updates.
@@ -68,7 +76,7 @@ Required permissions | For permissions required to apply an update, see [account
 ### Bug fixes
 
  - We upgraded the version of Microsoft.Data.OData from 5.8.1 to 5.8.4 to fix a vulnerability
- - Accesibility: We made the Azure AD Connect wizard resizable to account for different zoom levels and screen resolutions.
+ - Accesibility: We made the Azure AD Connect wizard resizable to account for different zoom levels and screen resolutions
  - Accesibility: Named elements to satisfy accessibility requirements
  - We fixed a bug where miisserver was crashing due to a null reference
  - We fixed a bug to ensure the desktop SSO value persists after upgrading Azure AD Connect to a newer version

articles/active-directory/manage-apps/f5-big-ip-forms-advanced.md

@@ -116,7 +116,7 @@ Setting up a SAML federation trust between BIG-IP APM and Azure AD is one of the
       >[!NOTE]
       >In this configuration, the SAML flow would operate in IdP-initiated mode, where Azure AD issues users a SAML assertion before they're redirected to the BIG-IP service endpoint for the application. The BIG-IP APM supports both IdP-initiated and service provider-initiated modes.
 
-   c. For the `Logout URI`, enter the BIG-IP APM single logout (SLO) endpoint, prepended by the host header of the service that's being published. Providing an SLO URI ensures that users' BIG-IP APM session is also terminated after they're signed out of Azure AD. An example URI might be *https://myvacation.contoso.com/saml/sp/profile/redirect/slr*.
+   c. For the `Logout URI`, enter the BIG-IP APM single logout (SLO) endpoint, prepended by the host header of the service that's being published. Providing an SLO URI ensures that users' BIG-IP APM session is also terminated after they're signed out of Azure AD. An example URI might be `https://myvacation.contoso.com/saml/sp/profile/redirect/slr`.
 
      ![Screenshot showing a basic SAML configuration.](./media/f5-big-ip-forms-advanced/basic-saml-configuration.png)
 

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

@@ -144,7 +144,12 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ### Create Documo test user
 
-In this section, a user called Britta Simon is created in Documo. Documo supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Documo, a new one is created after authentication.
+In this section, a user called B.Simon is created in Documo. 
+
+1. Navigate to the [Users page](https://app.documo.com?redirectTo=/users) on the Documo app.
+1. Click the **New user** button.
+1. Fill out the user form with name, email, phone number, user role, and password information. Make sure the **email** field matches the email for B.Simon in **Azure AD**.
+1. Click **Create**.
 
 ## Test SSO 
 

articles/azure-arc/servers/manage-vm-extensions.md

@@ -1,7 +1,7 @@
 ---
 title: VM extension management with Azure Arc-enabled servers
 description: Azure Arc-enabled servers can manage deployment of virtual machine extensions that provide post-deployment configuration and automation tasks with non-Azure VMs.
-ms.date: 10/28/2021
+ms.date: 12/21/2021
 ms.topic: conceptual
 ---
 
@@ -45,7 +45,7 @@ In this release, we support the following VM extensions on Windows and Linux mac
 To learn about the Azure Connected Machine agent package and details about the Extension agent component, see [Agent overview](agent-overview.md#agent-component-details).
 
 > [!NOTE]
-> Recently support for the DSC VM extension was removed for Azure Arc-enabled servers. Alternatively, we recommend using the Custom Script Extension to manage the post-deployment configuration of your server or machine.
+> The Desired State Configuration VM extension is no longer available for Azure Arc-enabled servers. Alternatively, we recommend [migrating to guest configuration](../../governance/policy/how-to/guest-configuration-azure-automation-migration.md) or using the Custom Script Extension to manage the post-deployment configuration of your server.
 
 Arc-enabled servers support moving machines with one or more VM extensions installed between resource groups or another Azure subscription without experiencing any impact to their configuration. The source and destination subscriptions must exist within the same [Azure Active Directory tenant](../../active-directory/develop/quickstart-create-new-tenant.md). This support is enabled starting with the Connected Machine agent version **1.8.21197.005**. For more information about moving resources and considerations before proceeding, see [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
 

articles/azure-maps/quick-android-map.md

@@ -1,9 +1,10 @@
 ---
-title: 'Quickstart: Create an Android app with Azure Maps | Microsoft Azure '
+title: 'Quickstart: Create an Android app with Azure Maps'
+titleSuffix:  Microsoft Azure Maps
 description: 'Quickstart: Learn how to create an Android app using the Azure Maps Android SDK.'
 author: stevemunk
 ms.author: v-munksteve
-ms.date: 04/26/2021
+ms.date: 12/21/2021
 ms.topic: quickstart
 ms.service: azure-maps
 services: azure-maps
@@ -32,18 +33,18 @@ This article shows you how to add the Azure Maps to an Android app. It walks you
 
 Create a new Azure Maps account with the following steps:
 
-1. In the upper left-hand corner of the [Azure portal](https://portal.azure.com), click **Create a resource**.
-2. In the *Search the Marketplace* box, type **Azure Maps**.
-3. From the *Results*, select **Azure Maps**. Click **Create** button that appears below the map.
+1. In the upper left-hand corner of the [Azure portal](https://portal.azure.com), select **Create a resource**.
+2. In the *Search the Marketplace* box, type **Azure Maps**, then select **Azure Maps** from the search results.
+3. Select the **Create** button that appears below the map.
 4. On the **Create Maps Account** page, enter the following values:
     * The *Subscription* that you want to use for this account.
     * The *Resource group* name for this account. You may choose to *Create new* or *Use existing* resource group.
     * The *Name* of your new account.
     * The *Pricing tier* for this account.
     * Read the *License* and *Privacy Statement*, and check the checkbox to accept the terms.
-    * Click the **Create** button.
+    * Select the **Create** button.
 
-    :::image type="content" source="./media/quick-demo-map-app/create-account.png" alt-text="Create Maps account in portal":::
+    :::image type="content" source="./media/quick-demo-map-app/create-account.png" alt-text="A screen shot that shows the Create Maps account pane in the Azure portal":::
 
 ## Get the primary key for your account
 
@@ -56,28 +57,28 @@ Once your Maps account is successfully created, retrieve the primary key that en
 >[!NOTE]
 > If you use the Azure subscription key instead of the Azure Maps primary key, your map won't render properly. Also, for security purposes, it is recommended that you rotate between your primary and secondary keys. To rotate keys, update your app to use the secondary key, deploy, then press the cycle/refresh button beside the primary key to generate a new primary key. The old primary key will be disabled. For more information on key rotation, see [Set up Azure Key Vault with key rotation and auditing](../key-vault/secrets/tutorial-rotation-dual.md)
 
-![Get Primary Key Azure Maps key in Azure portal](media/quick-android-map/get-key.png)
+![A screen shot showing the Azure Maps Primary key in the Azure portal](media/quick-android-map/get-key.png)
 
 ## Create a project in Android Studio
 
 First, create a new project with an empty activity. Complete these steps to create an Android Studio project:
 
 1. Under **Choose your project**, select **Phone and Tablet**. Your application will run on this form factor.
-2. On the **Phone and Tablet** tab, select **Empty  Activity**, and then select **Next**.
+2. On the **Phone and Tablet** tab, select **Empty Activity**, and then select **Next**.
 3. Under **Configure your project**, select `API 21: Android 5.0.0 (Lollipop)` as the minimum SDK. This is the earliest version supported by the Azure Maps Android SDK.
 4. Accept the default `Activity Name` and `Layout Name` and select **Finish**.
 
 See the [Android Studio documentation](https://developer.android.com/studio/intro/) for more help with installing Android Studio and creating a new project.
 
-![Create a project in Android studio](media/quick-android-map/form-factor-android.png)
+![A Create new project screen shot in Android studio](media/quick-android-map/form-factor-android.png)
 
 ## Set up a virtual device
 
 Android Studio lets you set up a virtual Android device on your computer. Doing so can help you test your application during development. To set up a virtual device, select the Android Virtual Device (AVD) Manager icon in the upper-right corner of your project screen, and then select **Create Virtual Device**. You can also get to the AVD Manager by selecting **Tools** > **Android** > **AVD Manager** from the toolbar. In the **Phones** category, select **Nexus 5X**, and then select **Next**.
 
 You can learn more about setting up an AVD in the [Android Studio documentation](https://developer.android.com/studio/run/managing-avds).
 
-![Android Emulator](media/quick-android-map/android-emulator.png)
+![A screen shot of the Android Emulator in Android Studio](media/quick-android-map/android-emulator.png)
 
 ## Install the Azure Maps Android SDK
 
@@ -113,7 +114,7 @@ The next step in building your application is to install the Azure Maps Android
         > [!Note]
         > You can set the version number to "0+" to have your code always point to the latest version.
 
-    4. Go to **File** in the toolbar and then click on **Sync Project with Gradle Files**.
+    4. Go to **File** in the toolbar and then select **Sync Project with Gradle Files**.
 3. Add a map fragment to the main activity (res \> layout \> activity\_main.xml):
 
     ```xml
@@ -336,11 +337,11 @@ The next step in building your application is to install the Azure Maps Android
 
 5. Select the run button, as shown in the following graphic (or press `Control` + `R` on a Mac), to build your application.
 
-    ![Click Run](media/quick-android-map/run-app.png)
+    ![A screen shot showing the run button in Android Studio.](media/quick-android-map/run-app.png)
 
 Android Studio will take a few seconds to build the application. After the build is complete, you can test your application in the emulated Android device. You should see a map like this one:
 
-![Azure Maps in Android application](media/quick-android-map/quickstart-android-map.png)
+![A screen shot showing Azure Maps in an Android application](media/quick-android-map/quickstart-android-map.png)
 
 ## Clean up resources
 
@@ -354,8 +355,8 @@ If you don't plan to continue to the tutorials, take these steps to clean up the
 
 If you don't plan on continuing to develop with the Azure Maps Android SDK:
 
-1. Navigate to the Azure portal page. Select **All resources** from the main portal page. Or, click on the menu icon in the upper left-hand corner. Select **All resources**.
-2. Click on your Azure Maps account. At the top of the page, click **Delete**.
+1. Navigate to the Azure portal page. Select **All resources** from the main portal page.
+2. Select your Azure Maps account. At the top of the page, select **Delete**.
 3. Optionally, if you don't plan to continue developing Android apps, uninstall Android Studio.
 
 For more code examples, see these guides:

articles/azure-percept/azure-percept-devkit-container-release-notes.md

@@ -14,6 +14,11 @@ This page provides information of changes and fixes for Azure Percept DK Contain
 
 To download the container updates, go to [Azure Percept Studio](https://ms.portal.azure.com/#blade/AzureEdgeDevices/main/overview), select Devices from the left navigation pane, choose the specific device, and then select Vision and Speech tabs to initiate container downloads. 
 
+## December (2112) Release
+
+- Removed lines in the image frames using automatic image capture in Azure Percept Studio. This issue was introduced in the 2108 module release.  
+- Security fixes for docker services running as root in azureeyemodule, azureearspeechclientmodule, and webstreammodule. 
+
 ## August (2108) Release
 
 - Azureyemodule (mcr.microsoft.com/azureedgedevices/azureeyemodule:2108-1)

articles/azure-resource-manager/bicep/toc.yml

@@ -128,6 +128,13 @@
         href: patterns-name-generation.md
       - name: Shared variable file
         href: patterns-shared-variable-file.md
+  - name: Provide parameters
+    items:
+    - name: Create parameter file
+      href: parameter-files.md
+    - name: Pass sensitive values
+      displayName: key vault
+      href: key-vault-parameter.md
   - name: Scenarios
     items:
     - name: Access control
@@ -151,13 +158,6 @@
         href: deploy-powershell.md
       - name: Deploy - Cloud Shell
         href: deploy-cloud-shell.md
-    - name: Parameters
-      items:
-      - name: Create parameter file
-        href: parameter-files.md
-      - name: Pass sensitive values
-        displayName: key vault
-        href: key-vault-parameter.md
   - name: Configure settings
     items:
     - name: Bicep config file