Hybrid Configuration Wizard and licensing of your on-premises server used for hybrid

Greg Taylor - EXCHANGE The_Exchange_Team Is a walk-through available for installing the Exchange 2016 on-premise server meant ONLY to manage mail properties for users being synced to Azure AD in a greenfield (never had exchange) Windows Server AD environment?  Some of the questions that come up while I'm putting together my plan:

• Autodiscover SCP - should this be configured to https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml ?
• Client Access Namespace - should these be changed to anything outside of what the default install configures since Autodiscover will be pointing clients outlook.com?  If so, should they just be using https://www.outlook.com/<virtual service> ?
• If you use the HCW only to license the server, exiting after receiving the license, can mail properties still be managed?
• Should AADC have the optional feature checked for "Exchange Hybrid Deployment" during configuration?
• Do I need an external MPKI SSL cert for deployment of this management server?  Will a self-signed, or internal PKI cert be sufficient?

I'd imagine most of these won't apply to an environment that had Exchange previously as that would have been handled by a hybrid configuration.

In my particular deployment, I already have several Exchange Online users that will be matched and synced from Windows Server AD (using UPNs) after I've extended the schema to include the mail properties and users assigned the corresponding SMTP address from exchange online.  I'll be deploying AADC before Exchange 2016, and I don't want users connecting to internal DNS to suddenly try connecting to the 2016 Management server.