The dns server is waiting for active directory domain services to signal that the initial sync

#The dns server is waiting for active directory domain services to signal that the initial sync update

If your users have activated Power BI through self-service sign-up and created an unmanaged tenant for your organization, you must take over management as an internal or external admin using PowerShell This is the process we will implement in the current article, which is just as easy and simple as the previous one. Make sure you donвЂ™t have any unmanaged Power BI tenants. After your first Domain Controller is already in use, itвЂ™s time to add another Windows Server 2016 DC to your Active Directory environment.Either for redundancy, load balancing or just because another DC feels the right way to go.Subsequent synchronizations with 100 modifications on the AD server took a couple of seconds to complete. For more information about deleting domain names, see Manage custom domain names. When we performed internal testing of synchronization with an Active Directory server on our local network with 10 000 users, 1000 groups and 200 000 memberships, we found that the initial synchronization took about 5 minutes. To fix this duplication problem, you must delete the domain name from the old directory. If your domain name is currently verified in another directory, it canвЂ™t also be verified in the new directory. A domain name can only be verified in one directory.

Make sure the domain name isnвЂ™t already in use in another directory.

#The dns server is waiting for active directory domain services to signal that the initial sync update

If you canвЂ™t update the record on the registrar site, share the entry with someone who has permission to add the entry and verify itвЂ™s correct.

Make sure the entry is there, and that it matches the DNS entry information provided by Azure AD. Go back to the domain name registrar site. DNS records must propagate before Azure AD can verify the domain.