This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 30%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
Hi
We have deployed Azure ADDS in our environment and the AADDS Vnet was joined (peered) to an ExpressRoute Vnet for on-premises connectivity to Azure but unfortunately received the following alert.
All NSG rules are correct, as depicted in the follwoing picture:
Does anyone have an idea? Thanks in advance for helping
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 20%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hi @George Anobah ,
Just checking in to see if any of the below answer helped. If any of these answers your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
Thanks,
Shweta
Hi,
It seems you are missing some rules on the NSG Inbound and Outbound, also check this article and listed ports here.
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
It could be a DNS configuration issue in the VNET. Check the AzureP2S-VNET and see the DNS Servers settings. Type the name and the IP of the on-premises domain controllers that runs the DC/DNS server roles.
----------
--please don't forget to upvote and Accept as answer if the reply is helpful--
Can you please be specific? What DNS configuration issue could lead to this problem? As i mentioned, we are using AADDS and there is no on-premise DC.
The solution I was trying to convey is applicable when you wanted to extend an on-premises Active Directory domain to Azure. Your post indicates that you are connecting to on-premises. If that's not the case, check if your vnet has assigned with correct DNS entry
This issue has been resolved. I added a user-defined route of internet to the Domain services subnet and this resolved the issue