I am moving a small SharePoint Farm, one web server and one database server, from a co-located solution up into Microsoft Azure. As part of this move I am using Azure Site Recovery to fail my my virtual machines from my co-located provider up into Azure.
My co-located SharePoint Farm is connected to my office and part of my primary domain.
My Azure tenant is connected to my office, via VPN, and I have a number of existing Windows VMs in Azure that are joined to my domain.
Using Azure Site Recovery I have created exact replica VMs of my SharePoint Farm in my Azure Tenant. Since these VMs are essentially images of my existing SharePoint Farm, SIDs, Server Names, and all, I have walled them off in Azure within their own subnet
that can't reach my office network and hit my Primary DC.
But I want to test these VMs in Azure before I cut over....so....prior to doing the Azure Site Recovery Failover, from my co-location into Azure, I setup a NEW Domain Controller, in Azure, that's part of my primary domain. This DC is not a backup/read-only. It is a full DC with DNS and our GC.
Once I knew that my SharePoint Farm at my co-location could see the new DC, I did test fail-over of my farm into Azure and brought up my parallel SharePoint Farm, in Azure, in my walled off subnet. I then brought down my new DC, redid its networking, and brought it back up in my walled off subnet in Azure.
I now have my test SharePoint Farm VMs and my DC, walled off, can't connect to the primary domain controller, and all within Azure.
I want my test SharePoint Farm to logon against the DC within this walled off subnet. The test SharePoint web server seems to be hitting it. A test of $env:logonserver comes back with the DC within the walled off subnet. But the test SharePoint database server
simply won't logon against this walled off DC. It keeps trying to reach my PDC.
I have tried everything. DNS entries within their network interfaces, LMHosts files, GPO settings to try and force the server to look for the next closest DC. Nothing seems to work, for the test SharePoint database server.
Not sure what else I can do here...except reach out to the community. Any help would be appreciated.