However, when I try to actually log in to the computer using my email address, I get an error message saying that there are network problems, and I should try again. So clearly I do not really understand what I am doing.
I thought it might be a good idea to have the DNS server somehow more tightly coupled to Office 365, so Office 365 could do secure dynamic updates to the DNS server. Hopefully, then, the DNS server would have better information about how to log on and everything would flow better.
So I started following this guide. The first task is to provision a domain-joined virtual machine to remotely administer DNS for the managed domain. That is another guide. At step 6 of this guide, I need to decide which virtual network my virtual machine will be in. I am told to select the virtual network in which my Azure AD DS-managed domain is deployed.
My question is "where is this"? I have two virtual networks in my Azure portal, both of which I created myself. Where is the virtual network for Office 365? Thanks in advance.
Never mind, I figured this out myself. It turns out that Azure AD Domain Services had not been enabled for my Office 365 domain. I enabled it, and at that point chose a region and a virtual network. So now I know the virtual network and can continue.
However, it appears that Azure AD DS costs at least $109.50 per month, which is a showstopper for our little company. So I guess we will have to live with local accounts on our computer and none of the identity management features of AD.