What is the best way to handle networking during a long-running cloud migration?
Hi everyone, I'd like to get some opinions from people who have worked on large-scale cloud migrations. Consider a migration where workloads are gradually moved from AWS to Azure over several weeks or months rather than being migrated in a single cutover. During the migration period, both environments need to remain operational. A simplified architecture could look like: AWS workloads | | Existing connectivity | AWS Network | | Inter-cloud connectivity | Azure Network | | Azure workloads The challenge is that applications may temporarily become distributed across both clouds. For example: • Application servers may still be running in AWS. • New application components may already be deployed in Azure. • Databases or shared services may remain in AWS temporarily. • DNS and routing may need to support both environments. • Migration tools may require connectivity to source and target environments. • Some workloads may be migrated much earlier than their dependent services. For a long-running migration like this, what architecture would you recommend? Some options I have been considering are: 1. Site-to-site VPN between AWS and Azure 2. Dedicated connectivity such as AWS Direct Connect + Azure ExpressRoute 3. A combination of dedicated connectivity and VPN for backup 4. A hub-and-spoke architecture in Azure with controlled connectivity back to AWS 5. Application-level connectivity rather than relying heavily on network-level connectivity Another question is how you would handle routing. Would you prefer to: • Keep AWS and Azure routing domains mostly independent? • Use a centralized hub for cross-cloud traffic? • Advertise routes dynamically using BGP? • Restrict cross-cloud communication to only the application dependencies that require it? For a migration lasting several months, what approach have you found to be the most reliable and easiest to operate? I'm particularly interested in lessons learned around: • Routing • DNS • Security • Latency • Failover • Monitoring • Avoiding unexpected cross-cloud traffic costs Would appreciate experiences from anyone who has handled a production AWS-to-Azure or Azure-to-AWS migration.Azure Migrate Physical Server Discovery - ServerDiscoveryService.exe Crash Bug
Summary The Azure Migrate appliance for physical server discovery fails to complete discovery due to a crash bug in ServerDiscoveryService.exe. The service successfully connects to target servers but crashes during WSMan transport cleanup before any discovery data is collected. Environment Appliance OS: Windows Server 2022 Standard Evaluation (Build 20348) Appliance Type: Physical server discovery (script-based installation) ServerDiscoveryService.exe Version: 2.0.3300.663 .NET Version: 8.0.22 (CoreCLR 8.0.2225.52707) Target Servers: Windows Server (various) and Linux, all on-premises Discovery Agent Version: 2.0.03300.663 Appliance Configuration Manager Version: 6.1.294.1847 Symptoms Target server validation succeeds in the appliance configuration manager CIM sessions connect successfully (logs show "TestConnection succeeded for CIM Session with HTTP protocol") Connections are immediately disposed with "Disposing all connections when the process is shutdown" No discovery data is collected Azure portal shows error 60001 with misleading "Could not load file or assembly 'Microsoft.Management.Infrastructure'" message Discovery status remains "Discovery Incomplete" for all Windows servers Root Cause The ServerDiscoveryService.exe process crashes repeatedly with an unhandled NullReferenceException in the WSMan transport finalizer. This is visible in the Windows Application Event Log: Application: ServerDiscoveryService.exe CoreCLR Version: 8.0.2225.52707 .NET Version: 8.0.22 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException: Object reference not set to an instance of an object. at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync() at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync() at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize() The crash also triggers an access violation: Faulting application name: ServerDiscoveryService.exe, version: 2.0.3300.663 Exception code: 0xc0000005 Faulting application path: C:\Program Files\Microsoft Azure Server Discovery Service\ServerDiscoveryService.exe These crashes occur approximately every 10 minutes. Troubleshooting Completed Verified manual connectivity works: PowerShell Invoke-Command and New-CimSession both succeed from the appliance to target servers using the same credentials Verified WinRM configuration: Targets have WinRM HTTP listener on port 5985, LocalAccountTokenFilterPolicy is set to 1 Verified assemblies exist: Microsoft.Management.Infrastructure.dll is present in the GAC on both the appliance and target servers Tested both FQDNs and IP addresses: Same failure occurs with both Tested both local and domain credentials: Same failure with properly formatted credentials (domain\user) Verified time synchronization: Appliance clock is accurate Verified appliance is up to date: All components show current versions Tested with fresh appliance: Previously tried OVA-based appliance with similar results; rebuilt using Microsoft's PowerShell script installer on clean Server 2022—same issue Relevant Log Locations C:\ProgramData\Microsoft Azure\Logs\ConfigManager\ClientOperations_*.log - Shows successful CIM connections followed by immediate disposal C:\ProgramData\Microsoft Azure\Logs\ConfigManager\ApplianceOnboarding-Portal-*.log - Shows error 60000 "UnhandledException" with message "Internal error occured." (note: typo is in original) Windows Event Log (Application) - Contains the actual crash stack traces Conclusion This is a code defect in ServerDiscoveryService.exe—a null reference exception in a finalizer is a programming error that cannot be caused by configuration or environmental factors. The service connects successfully but crashes before completing its work. Request Please escalate to the Azure Migrate engineering team for a bug fix in ServerDiscoveryService.exe version 2.0.3300.663.
nvme disk devices and mobility agent
Hi everyone, I'm doing some tests regarding the migration of Linux ec2 instances from AWS to Azure, I have followed the docs for the modernized experience described here but the installation on the ec2 vms fails because the instalelr cannot find a scsi disk the error is for example : "AddDiskDiscoveryInfo failed: Error: no attribute found for key scsi_bus" My undestanding is that the installer expect to find some scsi reference under the linux userspace and since it cannot find it exit with errors. The vm I'm trying to migrate is based on suse linux 12, the disks of that vm are mapped like this : lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 10G 0 disk ├─nvme0n1p1 259:1 0 2M 0 part ├─nvme0n1p2 259:2 0 20M 0 part /boot/efi └─nvme0n1p3 259:3 0 10G 0 part / nvme1n1 259:4 0 1G 0 disk and lsscsi does not return any output, so for modern linux kernels nvme devices and scsi devices are different things, I think that the mobility agent should consider this and have an alternate way to identify disks/partitions when nvme is found.
Migrate on-prem AD to azure AD having ADDS
I have to move legacy apps from on-prem to azure. What I read is to use ADDS for legacy apps authentication is the only option since some of my legacy apps are using SSO and some has service accounts at on-prem AD. the goals are below: Migrate on-prem active directory to azure active directory and have azure active directory domain services. Migrate local group policies to azure active directory domain services migrate all services accounts from azure managed identities so those can be used on legacy applications. Migrate all user profiles seamlessly. Completely demote on-prem active directory. The environment is having 956 users and 20+ applications. currently have on-prem AD and azure AD and users are hybrid joined. Please guide through the process and best practice for above scenario.SUGGESTION: AzureMigrateInstaller.ps1 (Version: 10.3.0.0) - IE removal and Edge dependency
AzureMigrateInstaller.ps1 (Version: 10.3.0.0) function UninstallInternetExplorer { if ((Get-WindowsOptionalFeature -Online -FeatureName "Internet-Explorer-Optional-amd64").State -eq "Disabled") { Log-Info "Internet Explorer has already been uninstalled. Skipping uninstallation and continuing..." Log-Success "[OK]`n" return } do { Log-InfoHighLight "The latest Azure Migrate appliance configuration manager is not supported on Internet Explorer 11 or lower." Log-InfoHighLight "You can either uninstall Internet Explorer using this script and open the appliance URL https://$machineHostName`:44368 on any other browser except Internet Explorer." Log-Input "Do you want to remove Internet Explorer browser from this machine now? This will force a machine reboot immediately. Press [Y] to continue with the uninstallation or [N] to manually uninstall Internet Explorer..." $userChoice = Read-Host }while ("y", "n" -NotContains $userChoice.Trim()) if ($userChoice.Trim() -eq "n") { $global:WarningCount++ Log-Error "Skipping IE uninstallation..." Log-Warning "Warning #$global:WarningCount User Action Required - Remove Internet Explorer as the default browser and then launch Azure Migrate appliance configuration manager using the shortcut placed on the desktop.`n" } else { dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64 /NoRestart # Restart the machine shutdown -r -t 60 -f Log-Success "[OK]" Log-InfoHighLight 'Restarting machine $machineHostName in 60 seconds. To abort this restart execute "shutdown /a" - Not Recommended.' # Exit the script as restart is pending. exit 0 } } The script will call this function and remove IE from Windows Server. If the user chooses to do so, it causes an expected restart to finalize the removal. The function is being called AFTER the cleanup and after all components have been installed. It will not the script resume where it left off before the restart. Suggestion: - make the cleanup of components (at every run of the script) optional using WMIprovider is very slow, too and causes high CPU load. - rehome the IE removal in the front of the script OR alternatively include a message that this is the last operation of the script and it does not need to be run again after the potential restart. Please also include a clear warning that disabling IE, will break IE mode for Edge. It is prominently used for WSUS Update Import etc., not necessarily on a Hyper-V host though. I do not see the reason why you remove IE, the package will also install MS Edge, if it does not already exist. Which is good enough.Digital event: Extend to the Cloud with Azure VMware Solution
Transform your VMware investments in the cloud Learn how to easily run your VMware workloads natively on Azure at this free digital event. Join industry experts for an inside look at the latest capabilities of Azure VMware Solution and: Hear from customers who’ve used Azure VMware Solution to optimize their workloads. Learn how to cost-effectively migrate your VMware workloads, skills, and tools to the cloud. Get modernization tips and best practices direct from Microsoft and VMware insiders. See demos and be among the first to learn about new and upcoming product features. Join technical sessions on simple deployment, migration, disaster recovery, and connecting to other Azure services. Plus, ask the experts your questions in the live chat Q&A. Delivered in partnership with VMware. Register now > Extend to the Cloud with Azure VMware Solution Wednesday, March 23, 2022 9:00 AM–11:30 AM Pacific Time https://info.microsoft.com/www-extend-to-the-cloud-with-azure-vmware-solution.html?ocid=AID3045911_QSG_579520Digital event: Modernize and Migrate with Hybrid Flexibility
Boost your skills with guidance from Azure customers and experts Grow your skills and get insights from real Azure customers to navigate your cloud journey with confidence at this free digital event. Discover best practices and resources to accelerate every stage of your modernization and migration with Azure. Register now to: Learn best practices in technical sessions on modernizing and migrating specific workloads—including .NET, Java and web apps, relational data, and servers. Get insights from real-life modernization examples with enterprise customers who successfully modernized and migrated with Azure. Learn to manage and govern assets consistently across hybrid environments. Register now > Get a chance to win Surface headphones, Surface earbuds, or a Bose SoundLink micro speaker by registering now for this free digital event. 15 winners will be selected following the event. Boost your chances by earning entry points through activities like knowledge checks and an event survey. No purchase necessary. Open only to registered event attendees 18+. Game ends April 13, 2022. For official rules, see https://aka.ms/AzureModernizationDigitalEventSweepstakes. Modernize and Migrate with Hybrid Cloud Flexibility Wednesday, April 13, 2022 9:00 AM to 11:00 AM Pacific Time
Announcements and cows at Azure Open Source Day - Feb 15
https://info.microsoft.com/ww-azure-open-source-day.html?ocid=AID3043963_QSG_567533is a free digital event featuring Linux and open-source speakers from Microsoft, AMD, Red Hat, SUSE, GitHub and SitePro who come together to share tips and best practices on how to turbocharge apps and data with open-source and hybrid cloud technologies. Attendees will learn how Microsoft is committed to open source and works with the open-source community to develop new technologies. They’ll hear about the latest trends and capabilities of using Linux and Azure together—direct from Microsoft insiders. Why attend? Get the inside scoop on CBL-Mariner, the Linux distribution built by Microsoft to host Azure open-source services. A rapidly increasing number of Azure services are built using open source, leading Microsoft to create CBL-Mariner, Azure’s own internal Linux distribution. Learn why Azure decided to build Mariner, how it is being developed in the open, and what benefits it brings to customers using open-source services on Azure. Find out how to better automate and manage Linux investments on Azure using Azure Hybrid Benefit and Project Bicep (next generation ARM Templates). Get a quick overview of the new Bicep language for native, declarative resource deployments to Azure. Discover tools for every developer, including Visual Studio Code, GitHub Codespaces, and Azure managed database and AI services. Discover how developers are modernizing applications with Azure managed open-source data and AI services. This session will feature real-world examples of developers who have re-platformed or re-architected applications, and the design and technology decisions they made to create more scalable and performant applications. Learn about application modernization best practices using containers and Azure Kubernetes Service (AKS). Get an overview on Microsoft’s full spectrum of cloud native applications and open source on Azure. Join us to learn about our latest innovations for containers and serverless including Azure Kubernetes Service, Azure Red Hat OpenShift, and Azure Container Apps. Hear from Microsoft insiders and Linux industry leaders like Red Hat and SUSE. Red Hat Ansible Automation Platform is a robust, open source automation solution that allows users to build and operate automation across the different parts of an organization. Red Hat has been working to bring the power of the Ansible Automation Platform to the Microsoft Azure Marketplace, including native integrations to numerous Azure services. These integrations provide a differentiated experience unique for Azure users to quickly and easily get started with automation for your Azure resources. Learn how to deploy and manage Kubernetes everywhere with Rancher by SUSE running on Microsoft Azure. Rancher addresses the operational and security challenges of managing multiple Kubernetes clusters across any infrastructure, while providing DevOps teams with integrated tools for running containerized workloads. Transform your business operations without negative impact during the journey to hybrid cloud providing reliability and scalability. The key topics that will be covered include: • SUSE and Microsoft partnership • Rancher container management platform • Deployment of Kubernetes cluster demo Ask the experts your questions during the live chat Q&A. During the event—9:00AM to 10:30AM Pacific Time—is your opportunity to connect to these industry experts and ask your questions. Don’t miss out! https://info.microsoft.com/ww-azure-open-source-day.html?ocid=AID3043963_QSG_567533 on February 15, 2022 and hear Microsoft CEO, Satya Nadella, share a special announcement on the 30th anniversary of Linux. Or https://twitter.com/Azure/status/1481053337000763392 Azure Open Source Day Tuesday, February 15, 2022 9:00 AM–10:30 AM Pacific Time https://info.microsoft.com/ww-azure-open-source-day.html?ocid=AID3043963_QSG_567533 Delivered in partnership with AMD.
