Azure IAAS SharePoint Farm – Custom domain

I have been tasked with figuring out how to setup a SharePoint 2016 farm in AZURE IAAS with VMs. I have a dev farm setup with a virtual network with DC, SQL, Single Farm VM. I have an internal domain name that’s demo.mydomain.com that works for the intranet but making it accessible from the internet is the problem. I have public DNS names for each server at servername.eastus.cloudapp.azure.com and I can access my team site from the internet with the “Public DNS Name” of the Single Farm VM.

However, I want to access the SP website from the internet with the internal domain name (that would be the easiest) or with another custom domain name, if that’s not possible. The only article I can find is https://support.microsoft.com/en-us/help/10065/associating-a-custom-domain-name-and-securing-communication-with-azure but I don’t think this is the right article because it’s talking about a cloudapp.net, not cloudapp.azure.com. Also, it just talks about setting up a CNAME or an A RECORD on your domain name providers website to point to the “Public DNS Name” and I need to build this farm out to include Workflow Manager and Office Online server using SSL which is a far more complicated domain scenario.

Does anybody have any idea on how to get information to do this? I’m sure Azure must support it. . .

Related:

SharePoint – The service did not start due to a logon failure

Sometimes a minor detail can lead into severe side-effects, as is the case in this posting. Our client installed a new piece of software, and one of the installation steps generated a rather seemingly harmless question. The installation software asked if it can be allowed to update a GPO (Group Policy object) in Active Directory (AD). The unsuspecting IT staff member assumed this was fine and proceeded to make the changes required to make the software work. However, soon after, we started receiving error messages indicating that numerous service accounts and SharePoint service accounts could not login anymore.

If a service account cannot login as a service anymore, the application pretty much stops working. And in this particular case, the SharePoint powered public web site, as well as all intranet sites, simply stopped working. Fortunately, with Intelligent Monitoring the issue was identified as soon as the Group Policy was applied and the IT staff could update the GPO in question without any major outages. Without monitoring, it may have taken the IT staff a long time and a lot of effort to get to the bottom of this issue. Under further investigation it turned out that the new software installed, as advertised, updated an existing GPO. However, instead of adding a new account under Windows User Rights Assignment and Log on as a service, the software replaced all existing associations, which led the issue.

Related:

Moving WSS sites to a new SharePoint 2010 Foundation server

This existing question helps but it doesn’t answer all my questions.

I have WSS 3 running on Server1 (Server 2003) and its database is DBServer1 (SQL 2008). I have installed SharePoint 2010 Foundation on Server2 (Server 2008) with databases on DBServer2 (SQL 2008 R2).

SP 2010 Foundation is up and running ok and it already has one newly created Web Application. Now my goal is to copy all sites from Server1/DBServer1 to Server2/DBServer2 (and eventually retire Server1/DBServer1).

Could you please help me with a step-by-step list on how to accomplish this?

Thank you!

Related: