Initial MS documentation on this topic can be found here

Initial MS documentation on this topic can be found here. You don't need a sub domain nor are they even supported. You can keep and should it all in one (flat) domain. Also, just to call it out, a domain functional level of 2012 R2 or higher is required as well as a forest functional level of 2012 R2 or greater. You can use the following as an alternative to what MS is suggesting but you may run issues with naming and/or certificates:

While the documentation from MS to Dynamics 365 For Finance and Operations set up and deploy on-premises environments is fairly good, there are a few areas in which I think some additional explanation and context for planning ahead would be nice. This guide is meant to augment the MS documentation but not replace it. Each page will have a link back to the specific section we'll be augmenting with some additional commentary. This page will serve as the nexus for all the pages / parts as they get published.

Restarting an AOS in AX 2009 and 2012 is easy. Depending on the topology in D365, that can also be easy. However, performing the same action with Dynamics 365 For Finance and Operations on-premise isn't quite as easy because the service fabric is there. You have to ask the service fabric to restart the service rather just restart a windows based service. Here is the powershell that can restart the AXService.exe services for you which is, in simple terms, restarting the AOS.

Dynamics 365 For Finance and Operations has pretty decent documentation available on how to configure and setup an environment. However, some areas need some additional detail to really help them be ready for prime time. Specifically in the area of describing your proposed environment, things are sort of high level. The official documentation can be found here.

Service Fabric Node Listing

Learn how to run a database sync via command line for an Azure based instance of Dynamics 365 for Finance and Operations as well as how to perform the same action in an on premise environment.

Learn how to import and license file into Dynamics 365 For Finance an Operations for an azure based install plus how to do it in an on premise environment.

Deployment scenarios between AX 2012 and Dynamics 365 For Finance and Operations can now be compared with the on premise version, called Local Business Data, of Dynamics 365 For Finance and Operations, or F&O for short. Below we'll compare and contrast each scenario, sizing, latency, other hidden requirements as well as when you would select Dynamics 365 F&O in Azure or the LBD flavor.

AX 2012 / 2009

The initial document and ConfigTemplate.xml from Microsoft and LCS is actually pretty good. The instructions are somewhat high level in some areas leaving a few details out and also there is very little assistance when it comes to the configTemplate.xml file. Below are some additions I made to the standard file from LCS which I hope will help others. It is also available for download if you prefer.