Just a follow up to this thread. I've been working with Microsoft Support and after some troubleshooting it was determined that TLS 1.2 was not enabled on the server. The agent found some internal documentation he followed which consisted of adding some new registry entries. Once TLS 1.2 communication was established vCenter and MABS.
Problem connecting MABS to vCenter
I am trying to deploy Microsoft Azure Backup Server for the first time in our environment. Stood up a new Windows 2019 Datacenter server and installed the software. When I try to connect to our vCenter environment I receive an error of "Data Protection Manager ID: 33623"
The MABS server is on the same network at vCenter. The server can ping vCenter by host name and IP. I disabled the Windows firewall thinking that might have been an issue. I created a new AD service account just for this process and I can successfully sign into vCenter with the account. But I have also tried my personal admin account and admin@vsphere.local credentials to setup the vCenter connection in MABS.
I'm drawing a blank of what else to try or what could be causing the problem.