Azure Migration and Modernization topics

Azure Migrate Physical Server Discovery - ServerDiscoveryService.exe Crash Bug

cbrnit — Thu, 29 Jan 2026 02:24:12 GMT

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.

Can anyone attest to the accuracy of an Azure Migrate Business Case?

Richard_Hartman — Mon, 24 Nov 2025 14:59:14 GMT

Hello! I've only created a business case in a simple lab environment using 5 on-prem Hyper-V servers. (SmartHotelHost lab from Github) The business case export explains that I'll be saving over $100K annually once fully migrated into Azure after multiple years. (It's only 5 servers!) That said, I've been reluctant to suggest the Business Case tool and steer clients toward the Azure Migrate Assessment and Azure Pricing Calculator which have proven to be reliable tools.

Anyone have any experience with the business case? Was it accurate?

Thanks a bunch!

Rich

TLS 1.0 and 1.1 Support on Azure Web App

dxxx0001 — Tue, 22 Apr 2025 11:40:11 GMT

I know Azure is winding up support for TLS 1.0 and 1.1 by August 2025.

Does anyone can help me to access our existing IoT devices to connect to Azure Web App using this TLS 1.0 and 1.1?

Our device were connecting to azure server fine until Mid March 2025. At end of March 2025 we lost access to this IoT devices which uses TLS 1.0, 1.1.

Any thoughts or any one have any idea why it stopped before the deadline of August 2025?

And what can be done to get back this devices online?

#IoTHub #WebApp #Azure #TLS #TLS1.0 #TLS1.1 #SNI

Azure Migrate Appliance

Skhatri — Sun, 06 Apr 2025 22:13:21 GMT

Hi,

We are planning to migrate 100 servers to Azure and are looking for guidance on deploying the Azure Migrate appliance. Due to space limitations on-premises, we do not have room to deploy the appliance locally.

Is it possible to deploy the Azure Migrate appliance in an Azure virtual machine (VM) within our existing Azure subscription? if so we would like to deploy the VM, install the Azure Migrate appliance, and then use it to assess, discover, and perform dependency analysis for our on-premises virtual and physical servers. Additionally, we are considering using the "Physical Server" option by downloading the installer script from the Azure Migrate appliance.

Can you please confirm if this approach is viable, are there any additional steps or considerations we should be aware of by deploying the appliance in Azure on a VM.

Thanks

MS SQL in Azure VM to SQL PaaS Migration

babuvt — Sun, 06 Apr 2025 17:46:17 GMT

What are the current best practices for migrating a SQL Server hosted in an Azure VM to Azure SQL Database?
I’m looking to approach this in two phases: Assessment followed by Migration.

There are several tools available for this process, including Database Migration Assistant (DMA), Azure Data Studio, Azure Migrate, and Azure Database Migration Service (DMS).
The source VMs are running across various OS versions—Windows Server 2008, 2012, 2016, and newer.

However, I’ve noticed that DMA appears to be deprecated, and Azure Data Studio is scheduled for retirement by February 2026.

How to build a lab

RabihSemaan — Tue, 25 Mar 2025 23:00:04 GMT

Dears,

i need to build a lab but i have lack of memories on my laptop, i tried to install vmware workstation or esxi on azure vm did not work. Is there ant method to practice vmware migrations via azure migrate.

even i am trying physical migration if you could help.

thank you

LAB: Set up DR for SQL in Azure VM by using Always on feature

Aaida_Aboobakkar — Tue, 25 Feb 2025 05:00:10 GMT

Why create DR for SQL in azure VMs?

Creating a disaster recovery (DR) plan for SQL Server in Azure Virtual Machines (VMs) is crucial to ensure business continuity and data protection. Azure VMs offer flexible and scalable solutions for high availability and disaster recovery, such as Always On availability groups, failover clustering, and geo-replication.

These features help minimize downtime and data loss during unexpected events, ensuring that your SQL Server databases remain accessible and resilient. By leveraging Azure's built-in DR capabilities, organizations can meet their recovery time objectives (RTO) and recovery point objectives (RPO), safeguarding critical business operations.

Architectural diagram

Steps

Create two SQL Server VM, one for on-premises and another for azure (for sake of lab I am creating both in azure vm. The experience is same for both scenario)

Follow the below steps in both SQL VMs to prep for DR.
Set domain for sql servers

Restart VM (Very Important to make changes effective)
Make sure the sql servers are joined to same domain
system--> Advanced setting--> computer name-->Change domain

Restart VM
Create Secondary VM using SQL supported image ( I am selecting standard SQL edition option)

Add roles and features

In Features select Failover clustering

Complete installation
Enable Always on feature

Repeat step for both VMs

Create a primary db in SQL1

In primary create test database and add data

-- Create the database
CREATE DATABASE userdatabase;

-- Switch to the new database
USE userdatabase;

-- Create the table
CREATE TABLE userinfo (
email VARCHAR(255) NOT NULL,
name VARCHAR(255) NOT NULL
);

-- Insert dummy data into the userinfo table
INSERT INTO userinfo (email, name) VALUES ('john.doe@example.com', 'John Doe');
INSERT INTO userinfo (email, name) VALUES ('jane.smith@example.com', 'Jane Smith');
INSERT INTO userinfo (email, name) VALUES ('alice.jones@example.com', 'Alice Jones');
INSERT INTO userinfo (email, name) VALUES ('bob.brown@example.com', 'Bob Brown');

SELECT * from userinfo

Create cluster

Create Availability group

Now you can see both servers are part of same availability group

test failover

Register now for the Migrate to Innovate Summit

MSdellis — Thu, 13 Feb 2025 21:47:33 GMT

Join the summit on March 11, presented in partnership with Intel.

Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI.

Join us to:

Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads.

Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure.

Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations.

Register now >

Migrate to Innovate Summit

Tuesday, March 11, 2025

9:00 AM–11:30 AM Pacific Time (UTC-7)

Migrating Windows Server from 'Hybrid Azure AD Join' to 'Entra ID Join (Cloud-Only)'

Nstellar — Thu, 03 Oct 2024 11:59:57 GMT

Hi everyone,

I need help with a scenario where I’m looking to move a server ( non DC ) from Microsoft Entra Hybrid Joined to cloud only (Entra ID) Joined only. The goal is to stop relying on the on-premises AD domain and make the server authenticate only through cloud-based accounts (Azure AD accounts).

I’d appreciate any guidance, documentation or best practices on how to properly handle this migration while ensuring minimal disruption.

Has anyone done this transition before?
What steps and considerations should I be aware of in terms of network configuration, Cost.... etc?

Thanks in advance for your help!

Trouble Installing Microsoft Site Recovery - Process Server Service Keeps Terminating

emad1250 — Tue, 13 Aug 2024 09:10:54 GMT

Hey everyone,

I'm in the middle of migrating our on-premise servers to the Azure cloud, and I've hit a snag that I can't seem to get past. I'm at the step where I need to install the Microsoft Site Recovery agent on our appliance, but I'm stuck on the last part—validating the server configuration.

Every time I run the installer, it fails during the validation step. At the same time, I've noticed that the "Process Server" service keeps getting terminated, and I'm unable to enable it again.

Has anyone encountered this issue before? Any tips on how to get past this, or what might be causing the Process Server service to keep failing? I'm really stuck here and could use some advice!

Thanks in advance for any help.

Sentinel migration

Victor1989 — Fri, 29 Nov 2024 07:48:51 GMT

need guidance to plan for sentinel migration

Plan your migration to Microsoft Sentinel | Microsoft Learn

Azure VMs migration from one tenant to another

Venelin Ustabashiev — Wed, 26 Jun 2024 08:59:37 GMT

Hi Community,

I have a task to move/migrate Azure VMs from subscription on one Azure tenant to subscription on another Azure tenant. Moving the subscription is not an option. I think I can treat the VMs as "Physical or other" and use Azure Migrate with an appliance. Is there any another way? Can I treat is as Hyper-V to Azure Migration? Will I need an appliance server for discovery and replication?

Regards

Venelin

Stop replication failed

cmadavis — Tue, 25 Jun 2024 19:30:50 GMT

I have a Azure Migrate: Migration and modernization | Replications where the migration has failed. I tried to stop the replication to create a new migration job but am now getting stop replication failed with the error below. I have checked the vault but cannot see any protected objects.

Error message

Protection could not be disabled for the machine 'MACHINENAME'.

Possible causes

Check the failed Disable Protection job for more information.

Recommendation

Resolve the issue, disable protection on the machine again.

Digital event: The Future of VMware Is in Azure – July 16th, 2024

MSdellis — Tue, 18 Jun 2024 17:43:51 GMT

Take a deep dive into options for migrating and optimizing your workloads in a rapidly evolving VMware landscape. Join this free digital event and learn how Azure VMware Solution can support your VMware workloads while minimizing migration disruption.

Security—with topics on securing the management plane, role-based access control, patch management, and integration with Microsoft Defender for Cloud and Azure VMware Solution.
Networking—with topics on hub-and-spoke vs. mesh network design, securing network traffic, traffic and networking monitoring, and hybrid deployments.
Disaster recovery and resiliency—with topics on replication and cold site setup, business continuity, and easier vSphere migration with Azure VMware Solution.
VMware integration with Azure services—with topics on data warehousing and data lakes, AI and machine learning analytics, DevOps solutions, and automation and lifecycle management.

Join us for talks from industry leaders, technical sessions, and live Q&A.

Register now >

The Future of VMware Is in Azure

Tuesday, July 16, 2024

9:00 AM–10:30 AM Pacific Time (UTC-7)

Azure Migration without VM Shutdown

Shepcon — Mon, 03 Jun 2024 13:33:38 GMT

We're in the process of shutting down the on-premises setup of our company environment running on VMware. We have a DC, SQL server, accounting server and a couple terminal servers used for remote access. I have created the necessary Azure migration assessment and ready to start the replication of the 1st batch of servers. Because we have a legacy custom SQL app, we must maintain standard Windows AD, so I'll be moving our DC virtual machine. Azure AD will not work thus the need to migrate our on-prem DC.

My question is replicating and copying our on-prem domain controller from VMware up to Azure but keeping it running following the replication migration up to Azure. I know the normal process of replication is to shutdown the running on-prem VMs once the final delta replication has completed. However, I need to keep my on-prem AD environment running for about another month as I build the Azure environment in parallel. I understand that the two environments will not be in-sync if new domain users are created but this likely will not need to occur with the small size of the company. Basically, does the Azure migration process allow us to keep the migrated VMs running following the final replication sync? I'll do this replication during non-production hours so network activity will be zero.

Thanks for any suggestions or input.

Ken

Looking for opinion: Unjoin Hybrid AD, or migrate to new tenant?

cia-ica — Tue, 14 May 2024 15:13:13 GMT

Hello,

So I have a bit of a conundrum, and I'm not sure which is the better option.

Situation: We currently have an Entra-Hybrid AD environment. Our local AD is a .lan domain, and has almost 30 years of historical garbage (none of it is required anymore). All of our endpoints are already setup for Intune, and all apps/policies are being pushed from Intune. We have two servers that we will migrate to Entra hosted VMs, so are not a big concern.

My question is this:

1) If we disconnect our Hybrid-AD connection, how do we make sure all users are cloud sync'd and no longer pulling from local AD.

2) Is there a way to formally disconnect our Entra tenant from our AD Sync tool (so that its no longer expecting that domain).

3) How do we remove our old domain from the Entra-ID Tenant?

3) Our current tenant was setup in a hurry, and was not setup with very good governance or any real organization. Is there a good service that can help "clean up" an existing tenant?

3) Would it be easier to simply create a new Tenant, set it up with best practices, migrate the users, email, onedrive and SP, and then re-join the Intune devices as the final setup?

Looking for recommendations/suggestions/pitfalls to look out for while doing this.

Thank you,

Will the AMS API documentation be accessible after service deprecation?

allkallka — Wed, 01 May 2024 12:30:02 GMT

I am looking for some info on whether the documentation on AMS API will be still available after the 30th of June when the service is to be deprecated.

Will it be archived? Will there be some public access?

nvme disk devices and mobility agent

Marioalessiocaruso — Tue, 30 Apr 2024 14:14:48 GMT

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.

Azure Migrate availability for Southeast Asia

LCKho3693 — Tue, 23 Apr 2024 02:59:05 GMT

Just to check whether any of you facing any issue on testing Azure Migrate in Southeast Asia region ?

I'm facing a issue where the Azure Migrate dashboard can't identify the "source appliance" that configured and discovering the VMs on source location, which causing problem on setting up "Target appliance".

TLS 1.0 for Web API Service

JamesPN — Tue, 09 Apr 2024 13:20:23 GMT

I'm trying to determine whether in October of this year all requests to my Web API on Azure that come from legacy TLS 1.0 systems will no longer work?

I understand that Azure storage will only accept TLS 1.2 going forward and thats fine as my web api talks to that using 1.2, however its incoming requests to my web API that I still need to allow 1.0.

When it says deprecated does it mean that it will not be possible to allow TLS 1 on my Web API or just that it will no longer be supported but you can still choose it?