Merge pull request #284504 from SnehaSudhirG/13Aug-MigrationTroubleshoot

Added a new article, updated toc

Author: Stacyrch140

articles/update-manager/media/migration-troubleshoot/error-migration-prerequisite-scripts.png

@@ -4,7 +4,7 @@ description: A summary of important pointers while migrating using Azure portal
 author: snehasudhirG
 ms.service: azure-update-manager
 ms.topic: conceptual
-ms.date: 08/01/2024
+ms.date: 08/13/2024
 ms.author: sudhirsneha
 ---
 
@@ -43,7 +43,10 @@ This article lists the significant details that you must note when you're migrat
 
 - When the migration runbook is executed multiple times, say you did Migrate All automation schedules and then again tried to migrate all the schedules, then migration runbook runs the same logic. Doing it again updates the MRP schedule if any new change is present in SUC. It doesn't make duplicate config assignments. Also, operations are carried only for automation schedules having enabled schedules. If an SUC was **Migrated** earlier, it will be skipped in the next turn as its underlying schedule will be **Disabled**. 
 - In the end, you can resolve more machines from Azure Resource Graph as in Azure Update Manager. You can't check if Hybrid Runbook Worker is reporting or not, unlike in Automation Update Management where it was an intersection of Dynamic Queries and Hybrid Runbook Worker.
-- Machines that are unsupported in Azure Update Manager aren't migrated. The Schedules, which have such machines will be partially migrated and only supported machines of the software update configuration will be moved to Azure Update Manager. To prevent patching by both Automation Update Management and Azure Update Manager, remove migrated machines from deployment schedules in Automation Update Management. 
+- Machines that are unsupported in Azure Update Manager aren't migrated. The Schedules, which have such machines will be partially migrated and only supported machines of the software update configuration will be moved to Azure Update Manager. To prevent patching by both Automation Update Management and Azure Update Manager, remove migrated machines from deployment schedules in Automation Update Management.
+- **Post Deboarding**: 
+    - Remove the user managed identity created for migration that is linked with the automation account. For more information, see [Remove user-assigned managed identity for Azure Automation account](../automation/remove-user-assigned-identity.md#remove-using-the-azure-portal).
+    - [Delete the user managed identity](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#delete-a-user-assigned-managed-identity).
 
 Post-migration, a Software Update Configuration can have any one of the following four migration statuses: 
 

articles/update-manager/media/migration-troubleshoot/error-prerequisite-scripts.png

@@ -0,0 +1,87 @@
+---
+title: Troubleshoot known issues with Azure Update Manager while migrating from Automation Update Management
+description: This article provides details on known issues and how to troubleshoot any problems when migrating from Automation Update Management to Azure Update Manager
+author: snehasudhirG
+ms.service: azure-update-manager
+ms.topic: conceptual
+ms.date: 08/13/2024
+ms.author: sudhirsneha
+---
+
+# Troubleshoot issues during automated migration
+
+**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers
+
+This article describes the errors that might occur when you use migration portal experience or scripts, and how to resolve them.
+
+## Required PowerShell modules for executing prerequisite script aren't installed
+
+### Cause
+
+When the required PowerShell modules aren't installed for executing the prerequisite scripts, you may see the following errors:
+
+:::image type="content" source="./media/migration-troubleshoot/error-prerequisite-scripts.png" alt-text="Screenshot that shows the error code when PowerShell modules aren't installed. " lightbox="./media/migration-troubleshoot/error-prerequisite-scripts.png":::
+
+:::image type="content" source="./media/migration-troubleshoot/error-migration-prerequisite-scripts.png" alt-text="Screenshot that shows the error code when the required PowerShell modules aren't installed. " lightbox="./media/migration-troubleshoot/error-migration-prerequisite-scripts.png":::
+
+### Resolution
+
+Ensure you successfully execute the command `Install-Module -Name Az -Repository PSGallery -Force`
+
+## Unable to acquire token for tenant organizations 
+
+### Issue
+
+Encountering a warning as - unable to acquire token `organizations` with error `InteractiveBrowserCredential authentication failed: Method not found: 'Void Microsoft.Identity.Client.Extensions.Msal.MsalCacheHelper.RegisterCache(Microsoft.Identity.Client.ITokenCa)`
+
+### Cause
+
+This is part of one of the documented [issues](https://github.com/Azure/azure-powershell/issues/25005) with Az.Accounts 3.0.0 module. [Learn more](https://learn.microsoft.com/answers/questions/1342970/warning-unable-to-acquire-token-for-tenant-organiz)
+
+### Resolution
+
+Execute command `Update-AzConfig -EnableLoginByWam $false` in an elevated PowerShell Session.
+
+### Issue
+
+:::image type="content" source="./media/migration-troubleshoot/warning-token-organization.png" alt-text="Screenshot that shows the warning message when tokens aren't acquired for tenant organizations. " lightbox="./media/migration-troubleshoot/warning-token-organization.png":::
+
+### Cause
+
+Your organization requires to use `Connect-AzAccount`  with `DeviceCode` parameter to login to Azure.
+
+### Resolution
+
+- Modify this [line](https://github.com/azureautomation/Preqrequisite-for-Migration-from-Azure-Automation-Update-Management-to-Azure-Update-Manager/blob/1750c1758cf9be93153a24b6eb9bfccc174ce66b/MigrationPrerequisites.ps1#L1224) in the Prerequisite script where it has the Connect-AzAccount Command to use the - [UseDeviceAuthentication](https://review.learn.microsoft.com/powershell/module/az.accounts/connect-azaccount?view=azps-12.2.0&branch=main#-usedeviceauthentication) parameter.
+
+
+## Encountering Get-AzOperationInsightsWorkspace exception message
+
+### Issue
+
+:::image type="content" source="./media/migration-troubleshoot/exception-message.png" alt-text="Screenshot that shows the exception message when the operational insights module isn't installed. " lightbox="./media/migration-troubleshoot/exception-message.png":::
+
+### Cause
+
+[Operational Insights](/powershell/module/az.operationalinsights/) module isn't installed. 
+
+### Resolution
+
+Execute Command `Install-Module-Name Az.OperationalInsights`
+
+## Couldn't convert string to DateTimeOffset: 1719675651. Path 'expires_on', line 1, position 1608.
+
+### Cause
+
+This error can come up while executing the Migration/Deboarding Runbook in Azure. This can happen if you have custom Az Modules in your automation account, which are outdated.
+
+### Resolution
+
+Delete custom Az Modules and ensure that default Az Module is updated to 8.0.0 for PowerShell 5.1
+
+## Next steps
+
+- [Migration using Azure portal](migration-using-portal.md)
+- [Migration using runbook scripts](migration-using-runbook-scripts.md)
+- [Manual migration guidance](migration-manual.md)
+- [Key points during migration](migration-key-points.md)

articles/update-manager/media/migration-troubleshoot/exception-message.png

@@ -75,6 +75,8 @@ items:
         href: migration-using-runbook-scripts.md
       - name: Key points to note for automated migration
         href: migration-key-points.md
+      - name: Troubleshoot automated migration
+        href: migration-troubleshoot.md
       - name: Using manual migration
         href: migration-manual.md
     - name: Check update compliance