locked
Azure Domain Verification RRS feed

  • Question

  • hi all, i have a trial azure active directory, i made my txt records but cant verify my domain bdo.ge, please help until my trial period expires, i want to bye azure active directory for users and can't test it fully
    Wednesday, December 28, 2016 3:59 PM

Answers

  • Hi Misha, 

    I had a look for this domain and I can see that it is currently e-mail verified against a Azure AD that was created as part of someone signing up to one of the self-service services. 

    You can find more information here: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-self-service-signup

    In order for you to be able to verify this domain on the Azure AD you are managing you will need to perform an internal admin takeover by signing up to one of the services using an email address in the bdo.ge namespace. OR alternatively you can use PowerShell to verify the domain in it's current state; and you can also use the -ForceTakeover Parameter using the Force Value if you do not want to retain access to any of the data for the services the individual employees signed up for.

    I hope this helps; If you have any questions please do let me know.

    Thanks,
    James. 


    Senior Escalation Engineer EEE-Dev | Azure AD Serviceability | Identity Engineering Team | Azure AD Identity and Access Management | blog: http://aka.ms/edutech

    Monday, January 2, 2017 8:30 PM

All replies

  • Hi,

    Add a custom domain name to Azure Active Directory, here are the steps:

    1.Add the custom domain name to your directory

    2. Add a DNS entry for the domain name at the domain name registrar

    3. Verify the custom domain name in Azure AD

    The important is that your organization owns the custom domain name, and add the DNS entry at the domain name registrar for the domain. Update the DNS zone file for the domain by adding the DNS entry provided to you by Azure AD. This DNS entry enables Azure AD to verify your ownership of the domain.

    Once you have added the DNS entry, you are ready to verify the domain name with Azure AD. Azure AD can verify the domain name only after the DNS records have propagated. This propagation often takes only seconds, but it can sometimes take an hour or more.

    Troubleshooting:

    If you can't verify a custom domain name, try the following:

    1.wait an hour.

    2.Ensure the DNS record was entered, and that it is correct.

    3.Delete the domain name from another directory in Azure AD.

    More information about verify the domain name with Azure AD, please refer to the link below:

    https://docs.microsoft.com/en-us/azure/active-directory/active-directory-add-domain

    If you still have questions, welcome to post back here.

    Best Regards,

    Jason


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, December 29, 2016 1:23 AM
  • Hi Misha, 

    I had a look for this domain and I can see that it is currently e-mail verified against a Azure AD that was created as part of someone signing up to one of the self-service services. 

    You can find more information here: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-self-service-signup

    In order for you to be able to verify this domain on the Azure AD you are managing you will need to perform an internal admin takeover by signing up to one of the services using an email address in the bdo.ge namespace. OR alternatively you can use PowerShell to verify the domain in it's current state; and you can also use the -ForceTakeover Parameter using the Force Value if you do not want to retain access to any of the data for the services the individual employees signed up for.

    I hope this helps; If you have any questions please do let me know.

    Thanks,
    James. 


    Senior Escalation Engineer EEE-Dev | Azure AD Serviceability | Identity Engineering Team | Azure AD Identity and Access Management | blog: http://aka.ms/edutech

    Monday, January 2, 2017 8:30 PM