Merge pull request #204911 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/active-directory/cloud-infrastructure-entitlement-management/faqs.md

@@ -107,7 +107,7 @@ For information about permissions usage reports, see [Generate and download the
 
 ## Does Permissions Management integrate with third-party ITSM (Information Technology Service Management) tools?
 
-Permissions Management integrates with ServiceNow.
+Integration with ITMS tools, such as ServiceNow, is in the future roadmap.
 
 ## How is Permissions Management being deployed?
 

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-enable-tenant.md

@@ -27,6 +27,12 @@ To enable Permissions Management in your organization:
 
 > [!NOTE]
 > During public preview, Permissions Management doesn't perform a license check.
+> The public preview environment will only be available until October 7th, 2022. You will be no longer be able view or access your configuration and data in the public preview environment after that date.
+> Once you complete all the steps and confirm to use Microsoft Entra Permissions Management, access to the public preview environment will be lost. You can take a note of your configuration before you start. 
+> To start using generally available Microsoft Entra Permissions Management, you must purchase a license or begin a trial. From the public preview console, initiate the workflow by selecting Start.
+
+
+
 
 ## How to enable Permissions Management on your Azure AD tenant
 

articles/active-directory/fundamentals/active-directory-how-to-find-tenant.md

@@ -28,13 +28,13 @@ Azure subscriptions have a trust relationship with Azure Active Directory (Azure
 
 1. Select **Properties**.
 
-1. Then, scroll down to the **Tenant ID** field. Your tenant ID will be in the box.
+1. Scroll down to the **Tenant ID** field. Your tenant ID will be in the box.
 
 :::image type="content" source="media/active-directory-how-to-find-tenant/portal-tenant-id.png" alt-text="Azure Active Directory - Properties - Tenant ID - Tenant ID field":::
 
 ## Find tenant ID with PowerShell
 
-You can also find the tenant programmatically. To find the tenant ID with Azure PowerShell, use the cmdlet `Get-AzTenant`.
+To find the tenant ID with Azure PowerShell, use the cmdlet `Get-AzTenant`.
 
 ```azurepowershell-interactive
 Connect-AzAccount
@@ -45,7 +45,7 @@ For more information, see this Azure PowerShell cmdlet reference for [Get-AzTena
 
 
 ## Find tenant ID with CLI
-If you want to use a command-line interface to find the tenant ID, you can do so with [Azure CLI](/cli/azure/install-azure-cli) or [Microsoft 365 CLI](https://pnp.github.io/cli-microsoft365/). 
+The [Azure CLI](/cli/azure/install-azure-cli) or [Microsoft 365 CLI](https://pnp.github.io/cli-microsoft365/) can be used to find the tenant ID.
 
 For Azure CLI, use one of the commands **az login**, **az account list**, or **az account tenant list** as shown in the following example. Notice the **tenantId** property for each of your subscriptions in the output from each command.
 

articles/active-directory/fundamentals/active-directory-troubleshooting-support-howto.md

@@ -34,8 +34,7 @@ If you are unable to find answers by using self-help resources, you can open an
 ### How to open a support ticket for Azure AD in the Azure portal
 
 > [!NOTE]
-> * For billing or subscription issues, you must use the [Microsoft 365 admin center](https://admin.microsoft.com).  
-> * If you're using Azure AD B2C, open a support ticket by first switching to an Azure AD tenant that has an Azure subscription associated with it. Typically, this is your employee tenant or the default tenant created for you when you signed up for an Azure subscription. To learn more, see [how an Azure subscription is related to Azure AD](active-directory-how-subscriptions-associated-directory.md).
+> If you're using Azure AD B2C, open a support ticket by first switching to an Azure AD tenant that has an Azure subscription associated with it. Typically, this is your employee tenant or the default tenant created for you when you signed up for an Azure subscription. To learn more, see [how an Azure subscription is related to Azure AD](active-directory-how-subscriptions-associated-directory.md).
 
 1. Sign in to [the Azure portal](https://portal.azure.com) and open **Azure Active Directory**.
 

articles/active-directory/fundamentals/active-directory-users-profile-azure-portal.md

@@ -54,6 +54,8 @@ As you'll see, there's more information available in a user's profile than what
 
     >[!Note]
     >You must use Windows Server Active Directory to update the identity, contact info, or job info for users whose source of authority is Windows Server Active Directory. After you complete your update, you must wait for the next synchronization cycle to complete before you'll see the changes.
+    >
+    > If you're having issues updating a user's Profile picture, please ensure that your Office 365 Exchange Online Enterprise App is Enabled for users to sign-in.
 
 ## Next steps
 After you've updated your users' profiles, you can perform the following basic processes:

articles/active-directory/governance/entitlement-management-organization.md

@@ -158,6 +158,9 @@ Only users from configured connected organizations can request access packages t
 
 > [!NOTE]
 > As part of rolling out this new feature, all connected organizations created before 09/09/20 were considered **configured**. If you had an access package that allowed users from any organization to sign up, you should review your list of connected organizations that were created before that date to ensure none are miscategorized as **configured**.  An admin can update the **State** property as appropriate. For guidance, see [Update a connected organization](#update-a-connected-organization).
+> [!NOTE]
+>  In some cases, a user might request an access package using their personal account having the same domain as the connected organization resulting in a new suggested connected organization. In this case, make sure the user is using their organization account instead and the portal will identify this user coming from the configured connected organization Azure AD tenant.
+
 
 ## Next steps
 

articles/automation/update-management/remove-vms.md

@@ -18,17 +18,23 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
 ## To remove your machines
 
-1. In the Azure portal, launch **Cloud Shell** from the top navigation of the Azure portal. If you are unfamiliar with Azure Cloud Shell, see [Overview of Azure Cloud Shell](../../cloud-shell/overview.md).
+### To identify Azure VM
 
-2. Use the following method to identify the UUID of an Azure virtual machine or non-Azure machine that you want to remove from management.
+1. In the Azure portal, launch **Cloud Shell** from the top navigation of the Azure portal. If you are unfamiliar with Azure Cloud Shell, see [Overview of Azure Cloud Shell](../../cloud-shell/overview.md).
 
-   # [Azure VM](#tab/azure-vm)
+2. Use the following method to identify the UUID of an Azure virtual machine that you want to remove from management.
 
    ```azurecli
    az vm show -g MyResourceGroup -n MyVm -d
    ```
 
-   # [Non-Azure machine](#tab/non-azure-machine)
+### To identify Non-Azure machine
+
+1. In the Azure portal, navigate to **Log Analytics workspaces**. Select your workspace from the list.
+
+2. In your Log Analytics workspace, select **Logs** from the left-hand menu.
+
+3. Use the following query to identify the UUID of a non-Azure machine that you want to remove from management.
 
    ```kusto
    Heartbeat
@@ -37,17 +43,17 @@ Sign in to the [Azure portal](https://portal.azure.com).
    | summarize by Computer, VMUUID
    ```
 
-   ---
+### To remove the identified Azure or Non-Azure machine
 
-3. In the Azure portal, navigate to **Log Analytics workspaces**. Select your workspace from the list.
+1. In the Azure portal, navigate to **Log Analytics workspaces**. Select your workspace from the list.
 
-4. In your Log Analytics workspace, select **Computer Groups** from the left-hand menu.
+2. In your Log Analytics workspace, select **Computer Groups** from the left-hand menu.
 
-5. From **Computer Groups** in the right-hand pane, the **Saved groups** tab is shown by default.
+3. From **Computer Groups** in the right-hand pane, the **Saved groups** tab is shown by default.
 
-6. From the table, click the icon **Run query** to the right of the item **MicrosoftDefaultComputerGroup** with the **Legacy category** value **Updates**.
+4. From the table, click the icon **Run query** to the right of the item **MicrosoftDefaultComputerGroup** with the **Legacy category** value **Updates**.
 
-7. In the query editor, review the query and find the UUID for the machine. Remove the UUID for the machine and repeat the steps for any other machines you want to remove.
+5. In the query editor, review the query and find the UUID for the machine. Remove the UUID for the machine and repeat the steps for any other machines you want to remove.
 
    > [!NOTE]
    > For added protection, before making edits be sure to make a copy of the query. Then you can restore it if a problem occurs.
@@ -60,15 +66,15 @@ Sign in to the [Azure portal](https://portal.azure.com).
    | distinct Computer
    ```
 
-8. Save the saved search when you're finished editing it by selecting **Save > Save as function** from the top bar. When prompted, specify the following:
+6. Save the saved search when you're finished editing it by selecting **Save > Save as function** from the top bar. When prompted, specify the following:
 
     * **Name**: Updates__MicrosoftDefaultComputerGroup
     * **Save as computer Group** is selected
     * **Legacy category**: Updates
 
->[!NOTE]
->Machines are still shown after you have unenrolled them because we report on all machines assessed in the last 24 hours. After removing the machine, you need to wait 24 hours before they are no longer listed.
+> [!NOTE]
+> Machines are still shown after you have unenrolled them because we report on all machines assessed in the last 24 hours. After removing the machine, you need to wait 24 hours before they are no longer listed.
 
 ## Next steps
 
-To re-enable managing your Azure or non-Azure machine, see [Enable Update Management by browsing the Azure portal](enable-from-portal.md) or [Enable Update Management from an Azure VM](enable-from-vm.md).
+To re-enable managing your Azure or non-Azure machine, see [Enable Update Management by browsing the Azure portal](enable-from-portal.md) or [Enable Update Management from an Azure VM](enable-from-vm.md).

articles/devops-project/overview.md

@@ -23,7 +23,7 @@ ms.author: gwallace
 
 ## Advantages of using DevOps Starter
 
-  DevOps starter the following supports two CI/CD providers, to automate your deployments
+  DevOps starter supports the following two CI/CD providers, to automate your deployments
   * [GitHub Actions](https://github.com/features/actions)
   * [Azure DevOps](https://azure.microsoft.com/services/devops)
 

articles/search/cognitive-search-working-with-skillsets.md

@@ -7,7 +7,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 07/13/2022
+ms.date: 07/14/2022
 ---
 
 # Skillset concepts in Azure Cognitive Search