Azure
custom domain name verification process is little different if you are enabling
SSO using ADFS (Federated domain). If you select “I plan to configure the
domain for a single sing-on with my local Active Directory” option, you will
not get a TXT or MX record from this window for the domain verification.
The TXT
and MX records will be provided during the AADConnect configuration as shown in
the following screenshot:
However,
sometime you will get the AzureDomainNotVerifiedException error message during
the AADConnect domain verification process. The error messages and
details are provided below:
Create
AAD Trust
Add
error occurred executing CreAAD Trust task: Exception of type
‘Microsoft.Online.Deployment.Types.AzureDomainNotVerifiedException’ was thrown.
Resolution
/ Workaround
1.
Delete the custom domain from Azure.
2.
Add a new custom domain and DO NOT select “I plan to configure the domain for a
single sing-on with my local Active Directory” option.
3. Get
the TXT record and verify the domain.
4.
Perform AADConnect configuration. During this configuration, domain will be
converted from Managed to Federated.
Monday, November 9, 2015
AADConnect – An error occurred executing Create AD Trust task
3 comments:
I have learned a lot of useful information from your blog.GoMovies
Registering a domain is easy but its verification is way too difficult as it consists of so many technicalities. As I and my friends started an online MBA Essay writers website we faced numerous issues with domain verification and it cost us a lot. I wish we had found this post before so that it would have provided us with a little bit of ease.
I have two domains that are almost two years old, and now I want to use them but don't know how can I use Dissertation Writing Services for this. Can you please write something valuable on this for me?
Post a Comment