Merge pull request #215753 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 10/25

Author: ttorble

.openpublishing.redirection.azure-monitor.json

@@ -846,6 +846,11 @@
             "redirect_url": "/azure/azure-monitor/app/java-in-process-agent",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/export-power-bi.md",
+            "redirect_url": "/azure/azure-monitor/logs/log-powerbi",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-monitor/app/java-trace-logs.md",
             "redirect_url": "/azure/azure-monitor/app/java-in-process-agent",

articles/active-directory/external-identities/user-flow-add-custom-attributes.md

@@ -10,7 +10,7 @@ ms.subservice: B2B
 ms.topic: how-to
 ms.date: 03/02/2021
 ms.author: mimart
-ms.custom: "it-pro"
+ms.custom: engagement-fy23, "it-pro"
 ms.collection: M365-identity-device-management
 ---
 

articles/active-directory/governance/create-access-review.md

@@ -10,7 +10,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.topic: how-to
 ms.subservice: compliance
-ms.date: 09/09/2022
+ms.date: 10/24/2022
 ms.author: amsliu
 ms.reviewer: mwahl
 ms.collection: M365-identity-device-management
@@ -139,6 +139,7 @@ If you are reviewing access to an application, then before creating the review,
 
 1. In the **Enable review decision helpers** section choose whether you want your reviewer to receive recommendations during the review process:
     1. If you select **No sign-in within 30 days**, users who have signed in during the previous 30-day period are recommended for approval. Users who haven't signed in during the past 30 days are recommended for denial. This 30-day interval is irrespective of whether the sign-ins were interactive or not. The last sign-in date for the specified user will also display along with the recommendation.
+    1. If you select User-to-Group Affiliation, reviewers will get the recommendation to Approve or Deny access for the users based on user’s average distance in the organization’s reporting-structure. Users who are very distant from all the other users within the group are considered to have "low affiliation" and will get a deny recommendation in the group access reviews.
 
    > [!NOTE]
    > If you create an access review based on applications, your recommendations are based on the 30-day interval period depending on when the user last signed in to the application rather than the tenant. 

articles/active-directory/governance/media/create-access-review/helpers.png

@@ -99,17 +99,16 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 11. Review the user attributes that are synchronized from Azure AD to Atea in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Atea for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Atea API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
 
-      |Attribute|Type|Supported for filtering|
-      |---|---|---|
-      |userName|String|✓|
-      |active|Boolean|
-      |emails[type eq "work"].value|String|
-      |name.givenName|String|
-      |name.familyName|String|
-      |name.formatted|String|
-      |phoneNumbers[type eq "mobile"].value|String|
-      |locale|String|
-      |nickName|String|
+      Attribute|Type|Supported for filtering|Required by LawVu|
+      |---|---|---|---|
+      |userName|String|✓|✓|
+      |active|Boolean||✓|
+      |emails[type eq "work"].value|String||✓|
+      |name.givenName|String|||
+      |name.familyName|String|||
+      |name.formatted|String||✓|
+      |phoneNumbers[type eq "mobile"].value|String|||
+      |locale|String|||
 
 12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
@@ -134,6 +133,11 @@ Once you've configured provisioning, use the following resources to monitor your
 * Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion.
 * If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).  
 
+## Change Log
+* 10/25/2022 - Drop core user attribute **nickName**. 
+* 10/25/2022 - Changed the mapping of core user attribute **name.formatted** to **Join(" ", [givenName], [surname]) -> name.formatted**.
+* 10/25/2022 - Domain name of all OAuth config urls of Atea app changed to Atea owned domain.
+
 ## Additional resources
 
 * [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)

articles/active-directory/governance/media/create-access-review/upon-completion-settings-new.png

@@ -109,9 +109,10 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Provisioning tab automatic](common/provisioning-automatic.png)
 
-1. In the **Admin Credentials** section, click on Authorize, make sure that you enter your Taskize Connect account's Admin credentials. Click **Test Connection** to ensure Azure AD can connect to Taskize Connect. If the connection fails, ensure your Taskize Connect account has Admin permissions and try again.
+1. In the **Admin Credentials** section, click on Authorize, make sure that you enter your Gong account's Admin credentials. Click **Test Connection** to ensure Azure AD can connect to Gong. If the connection fails, ensure your Gong account has Admin permissions and try again.
 
    ![Token](media/gong-provisioning-tutorial/gong-authorize.png)
+   
 1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
 	![Notification Email](common/provisioning-notification-email.png)

articles/active-directory/saas-apps/atea-provisioning-tutorial.md

@@ -4,59 +4,38 @@ description: This article tells how to create configurations from existing serve
 keywords: dsc,powershell,configuration,setup
 services: automation
 ms.subservice: dsc
-ms.date: 08/08/2019
+ms.date: 10/25/2022
+ms.custom: engagement-fy23
 ms.topic: conceptual
 ---
 
 # Create configurations from existing servers
 
-> Applies To: Windows PowerShell 5.1
+> **Applies to:** :heavy_check_mark: Windows PowerShell 5.1
 
-Creating configurations from existing servers can be a challenging task.
-You might not want *all* settings,
-just those that you care about.
-Even then you need to know in what order the settings
-must be applied in order for the configuration to apply successfully.
+> [!IMPORTANT]
+>  The article refers to a solution that is maintained by the Open Source community. Support is only available in the form of GitHub collaboration, not from Microsoft.
 
-> [!NOTE]
-> This article refers to a solution that is maintained by the Open Source community.
-> Support is only available in the form of GitHub collaboration, not from Microsoft.
+This article explains how to create configuration from existing servers for an Azure Automation state configuration. To create configurations from an existing servers is a challenging task as you need to know the right settings and the order they must be applied to ensure that configuration is successful.  
 
-## Community project: ReverseDSC
+## Community project: ReverseDSC 
 
-A community maintained solution named
-[ReverseDSC](https://github.com/microsoft/reversedsc)
-has been created to work in this area starting SharePoint.
+ The [ReverseDSC](https://github.com/microsoft/reversedsc) is a community maintained solution created to work in this area beginning with the SharePoint. The solution builds on the [SharePointDSC resource](https://github.com/powershell/sharepointdsc) and extends it to orchestrate by [gathering information](https://github.com/Microsoft/sharepointDSC.reverse#how-to-use) from existing servers running SharePoint.
 
-The solution builds on the
-[SharePointDSC resource](https://github.com/powershell/sharepointdsc)
-and extends it to orchestrate
-[gathering information](https://github.com/Microsoft/sharepointDSC.reverse#how-to-use)
-from existing servers running SharePoint.
-The latest version has multiple
-[extraction modes](https://github.com/Microsoft/SharePointDSC.Reverse/wiki/Extraction-Modes)
-to determine what level of information to include.
+The latest version has multiple [extraction modes](https://github.com/Microsoft/SharePointDSC.Reverse/wiki/Extraction-Modes) to determine the level of information to include. The result of using the solution is generating
+[Configuration Data](https://github.com/Microsoft/sharepointDSC.reverse#configuration-data) that must be used with SharePointDSC configuration scripts.
 
-The result of using the solution is generating
-[Configuration Data](https://github.com/Microsoft/sharepointDSC.reverse#configuration-data)
-to be used with SharePointDSC configuration scripts.
 
-Once the data files have been generated,
-you can use them with
-[DSC Configuration scripts](/powershell/dsc/overview)
-to generate MOF files
-and
-[upload the MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
-Then register your servers from either
-[on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
-or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms)
-to pull configurations.
+## Create configuration from existing servers for an Azure Automation state configuration
 
-To try out ReverseDSC, visit the
-[PowerShell Gallery](https://www.powershellgallery.com/packages/ReverseDSC/)
-and download the solution or click "Project Site"
-to view the
-[documentation](https://github.com/Microsoft/sharepointDSC.reverse).
+Follow the steps to create a configuration from existing servers for an Azure Automation state configuration:
+
+1. After you generate the data files, you can use them with [DSC Configuration scripts](/powershell/dsc/overview) to generate *MOF* files.
+1. upload the [MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
+1. Register your servers from either [on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
+or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms) to pull configurations.
+
+For more information on ReverseDSC, visit the [PowerShell Gallery](https://www.powershellgallery.com/packages/ReverseDSC/) and download the solution or select **Project Site** to view the [documentation](https://github.com/Microsoft/sharepointDSC.reverse).
 
 ## Next steps
 

articles/active-directory/saas-apps/gong-provisioning-tutorial.md

@@ -4,40 +4,41 @@ description: This article describes the information to gather before opening a c
 services: automation
 ms.subservice:
 ms.topic: troubleshooting
-ms.date: 09/23/2019
+ms.custom: engagement-fy23
+ms.date: 10/21/2022
 ---
 
 # Data to collect when opening a case for Microsoft Azure Automation
 
-This article describes some of the information that you should gather before you open a case for Azure Automation with Microsoft Azure Support. This information is not required to open the case. However, it can help Microsoft resolve your problem more quickly. Also, you may be asked for this data by the support engineer after you open the case.
-
-## Basic data
+This article describes the information that you should gather before you open a case for Azure Automation with Microsoft Azure Support. Even though this information isn't required to open a case. However, it helps the support team to quickly resolve a problem.  
+ 
+> [!NOTE]
+> For more information, refer the Knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-Collect the basic data described in the Knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
 ## Data for Update Management issues on Linux
 
-1. In addition to the items that are listed in KB [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics), run the following log collection tool:
+1. Run the following log collection tool, in addition to the details in KB [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-   [OMS Linux Agent Log Collector](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/tools/LogCollector/OMS_Linux_Agent_Log_Collector.md)
+      - [OMS Linux Agent Log Collector](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/tools/LogCollector/OMS_Linux_Agent_Log_Collector.md)
 
-2. Compress the contents of the **/var/opt/microsoft/omsagent/run/automationworker/** folder, then send the compressed file to Azure Support.
+1. Compress the contents of the **/var/opt/microsoft/omsagent/run/automationworker/** folder, and send the compressed file to Azure Support.
 
-3. Verify that the ID for the workspace that the Log Analytics agent for Linux reports to is the same as the ID for the workspace being monitored for updates.
+1. Verify that the ID for the workspace that the Log Analytics agent for Linux reports to is the same as the ID for the workspace being monitored for updates.
 
 ## Data for Update Management issues on Windows
 
 1. Collect data for the items listed in [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-2. Export the following event logs into the EVTX format:
+1. Export the following event logs into the EVTX format:
 
    * System
    * Application
    * Security
    * Operations Manager
    * Microsoft-SMA/Operational
 
-3. Verify that the ID of the workspace that the agent reports to is the same as the ID for the workspace being monitored by Windows Updates.
+1. Verify that the ID of the workspace that the agent reports to is the same as the ID for the workspace being monitored by Windows Updates.
 
 ## Data for job issues
 
@@ -48,10 +49,13 @@ Collect the basic data described in the Knowledge Base article [4034605 - How to
    1. In the Azure portal, go to **Automation Accounts**.
    2. Select the Automation account that you are troubleshooting, and note the name.
    3. Select **Jobs**.
+
+      :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/select-jobs.png" alt-text="Screenshot showing to select jobs menu from automation account.":::
+
    4. Choose the job that you are troubleshooting.
-   5. In the Job Summary pane, look for the GUID value in **Job ID**.
+   5. In the Job Summary pane, check for the GUID value in **Job ID**.
 
-   ![Job ID within Job Summary Pane](media/collect-data-microsoft-azure-automation-case/job-summary-job-id.png)
+      :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/job-summary-job-id.png" alt-text="Screenshot Job ID within Job Summary Pane.":::
 
 3. Collect a sample of the script that you are running.
 
@@ -62,22 +66,20 @@ Collect the basic data described in the Knowledge Base article [4034605 - How to
    3. Select **Jobs**.
    4. Choose the job that you are troubleshooting.
    5. Select **All Logs**.
-   6. In the resulting pane, collect the data.
-
-   ![Data listed under All Logs](media/collect-data-microsoft-azure-automation-case/all-logs-data.png)
+      In the pane below, you can collect the data.
 
+       :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/all-logs-data.png" alt-text="Screenshot of Data listed under All Logs.":::
+      
 ## Data for module issues
 
-In addition to the [basic data items](#basic-data), gather the following information:
+In addition to the knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics), obtain the following information:
 
-* The steps you have followed, so that the problem can be reproduced.
+* The steps you followed, so that the problem can be reproduced.
 * Screenshots of any error messages.
 * Screenshots of the current modules and their version numbers.
 
 ## Next steps
 
-If you need more help:
-
 * Get answers from Azure experts through [Azure Forums](https://azure.microsoft.com/support/forums/).
 * Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience by connecting the Azure community to the right resources: answers, support, and experts.
 * File an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.

articles/automation/automation-dsc-config-from-server.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Automation State Configuration issues
 description: This article tells how to troubleshoot and resolve Azure Automation State Configuration issues.
 services: automation
 ms.subservice:
-ms.date: 04/16/2019
+ms.date: 10/17/2022
 ms.topic: troubleshooting
 ms.custom: devx-track-azurepowershell
 ---
@@ -101,9 +101,13 @@ VM has reported a failure when processing extension 'Microsoft.Powershell.DSC /
 
 ### Cause
 
-This issue is caused by a bad or expired certificate. See [Re-register a node](../automation-dsc-onboarding.md#re-register-a-node).
+The following are the possible causes:
 
-This issue might also be caused by a proxy configuration not allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning).
+- A bad or expired certificate. See [Re-register a node](../automation-dsc-onboarding.md#re-register-a-node).
+
+- A proxy configuration that isn't allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning). 
+
+- When you disable local authentication in Azure Automation. See [Disable local authentication](../disable-local-authentication.md). To fix it, see [re-enable local authentication](../disable-local-authentication.md#re-enable-local-authentication).
 
 ### Resolution