Azure AD – Domain Name Verification

Hello all,

As domain name is crucial part of the identifier for most of the directory resources(user-group-app ID) , you will probably add your own domain in to Azure Active Directory. During the addition process the domain is needed to be verified. Although the TXT record has been configured and the process is so straightforward , you may not be able to verify your domain :)

At this point you have to figure out what lies behind. What lurks in shadows :) ?

When you create Power BI free trial account by using your domain name, a shadow tenant is created without an admin and a subscription! What’s more, your domain name is verified and allocated by the shadow tenant. That’s the reason why you can’t verify it. Because, it has already been verified by another “shadow” tenant :)

At first, you need to release it. As there is no admin associated with the shadows tenant, you need to take over the admin rights, then you can release your domain.

Here are the documentations to perform these steps.

Wish you the best.

Azure Web App Day/Time issue

Hello all,

We have been through an issue pertaining to the time zone setting of our web application which run on Azure App Service. After a couple of trial, we set the time zone to the value shown below.

It worked for our web application which is supposed use GMT+3, Turkish Standard Daytime :) It seems there are several values to get the result(GMT +3) that you may give it a try.

Wish you all the best, regards.

Azure – Web App DNS issue

Hello there!

I have been driving a project which most of the components are run on Azure as PaaS and others as IaaS. Due to a service dependency, we built a point to site vpn to connect our Apps to our Azure VNet, and a site to site vpn to connect our VM‘s to to our on-premise. So our Apps are able to communicate to our on-premise through the tunnels. Lastly, we defined a custom DNS server ip address which points to one of our dns servers that run  on our on-premise.


The custom dns setting inherits  the VM’s inside the VNet. But not for the App.

At this point, we ran into a problem.Although the custom dns server ip address was set and displayed in VNet integration blade, it didn’t effect our App!  After a short dialog with Azure Support we were provided a solution :)


As you can see above , we added a variable settings  under the Application Settings of our web app. The value, of course, points to our on-premise dns server. The support guy that helped us gave us a promise to update the documentation :)


Wish you great week:)