How to migrate a domain network to the Azure cloud?

Question

Microsoft Azure

There is a network with 2 physical and 2 virtual servers under WinServer 2012R2 and 5+ clients. The two servers are domain controllers (primary and RODC), Hyper-V server and terminal application server (RemoteApp). Because of some moments, I began to consider moving to the melkosoft cloud. From what I tried to google on this topic, even more questions came out:

• Is there something special for a domain network to work in Azure, or will it be necessary to raise 2 VMs?
  
• How to be with a terminal server? It runs SQL Server and 3 applications that must be accessed "from anywhere in the world" via RemoteApp
  
• How will all this kitchen be licensed? There are OS licenses and RemoteApp client licenses obtained through the Open License. Will they no longer be needed?
  
• Should one of the domain controllers be left "at home"? There are ideas to transfer clients to shopping malls, as a fairly productive server will eventually be idle. I want to hit him with something useful.
  

Answer 1

1) Azure is just a cloud platform. Think of it as a virtualization tool. That is, you simply create virtual machines there and deploy your services there, and that's it.
2) And what about the terminal server? Want to transfer to the cloud - transfer. If you don't want it, keep it. What is the question?
3) Licenses are a dark subject... :-)
4) The domain controller should be left at home anyway. You never know - communication problems, all that. To avoid problems with user login. On this productive server, deploy Hyper-V, in it - a virtual domain controller, well, and something else, to taste.

Answer 2

For replication, there must be a physical domain controller.
ps it can be made "at home" and
there will be no problems with virtual settings to transfer it from physical virtual to physical media.
If I were you, I would not post the domain, reliability, what's stopping you from doing it "at home" in the "public" network.
access from anywhere in the world, you can not protect?
read my friend about ssl certificates and authorization on them.
this will not make your task easier, they will not give you normal throughput speeds, as far as resources are concerned, they will be limited.
I can advise the following:
the first thing you need is protection
from a simple, not expensive, get dirty, take it to a new level
you raise it to unix - the access filtering server - it will act as a firewall,
then you zanet the entire network - so that it is not physical, but virtual.
I'll give you a hint, the mask should be 255.255.0.0 - access will only be to a public network, i.e. from the outside you will not pick up, you will think how to connect. I don't want to be more specific, and I've said quite a lot.
What I say lastly Azure is a bonal network of virtual machines and that's it.