Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » AWS/Azure/OpenShift » Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available

Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available

Posted on 13/07/202008/04/2024 Christian By Christian No Comments on Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available
connection information

Azure Active Directory (Azure AD) has been renamed as Microsoft Entra ID. It is an identity and access management solution from Microsoft that helps organizations secure and manage identities for hybrid and multicloud environments. In this article, we shall discuss the fix “Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available”. Please see How to access shared resources from two different domains, and Active Directory: How to Setup a Domain Controller.

Why was this error “Enter connection information for your on-premise directory or forest” Prompted?

This error was prompted when I wanted to install Azure AD connect on another server for high availability, should in case one of the servers the agent is running on fails, we can as well have access to our applications. But this was not possible due to domain related errors as I will be discussing below.

Let’s simulate the error! As you can see below, if everything is working correctly with the domain, the forest should appear by default. However, all you need to do is click on Add Directory, as shown below.

on-premise directory

Also, see Azure Active Directory: Why do I need to deploy Azure AD? Here is Active Directory Forest – Trees and Domain and Sites, and how to install and configure Active Directory Domain Services on Windows Server 2022.

Fix Azure AD connect unable to connect directory

Let me manually input the domain name (forest) as shown below. Furthermore, This will fail because the root issue has not yet been fixed.

Azure AD connect

Now, you will be requested to enter your credentials.

Note: You cannot use your Enterprise or Domain administrator account for your AD Forest account. It is recommended to let Azure AD Connect or you can specify a synchronisation account with the correct permission.

Moreover, I will be using an existing account I have in AD. Click on “OK” as shown below

forest availability

This will run and try to validate the forest credentials but will fail, as shown below. This is the error!

connection information

Without this, you cannot proceed as the option to continue is greyed out. This Error is as a result of the following domain issues below.

To fix this issue, simply remove the device from the domain and have it joined to the domain again.

Note: From experience, This might not be the desired fix for your own scenrio, but further troubleshooting you might be able to resolve this issue.

See the following articles below for similar fixes on how to remove the device and have it joined to the domain on how to join a computer (PC) to the Domain. Here is the fix to error: An Active Directory could not be contacted / Cannot find domain: Non-existent domain.

Also, see Windows Server post OS installation for more details. See the fix to “We can’t sign you with this credential because your domain isn’t available. Why Can’t I Connect with a 169.254 IP Address?”

I hope you found this blog post on on the fix “Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available” helpful. Please let me know in the comment session if you have any questions.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
AWS/Azure/OpenShift Tags:AD Connect, AD Connect Error, Azure, Azure AD, Azure AD Tenant

Post navigation

Previous Post: AD Connect Error: The Synchronisation service scheduler is currently synchronization and the configuration change cannot be made at this time
Next Post: AD Connect Sync Service Not Running: Start ADSync to Continue

Related Posts

  • Create an S3 Bucket
    Backup Repository: How to Create Amazon S3 buckets AWS/Azure/OpenShift
  • Azure VM Creation With CLI 1
    Deploy a Linux virtual machine (VM) on Azure using the Azure CLI AWS/Azure/OpenShift
  • HybridCloudTrust
    WHFB Hybrid Cloud Kerberos Trust Model is now available AWS/Azure/OpenShift
  • Building VPC
    Build a Scalable VPC for Your AWS Environment [Part 1] AWS/Azure/OpenShift
  • veeam backup for aws Processing postgres rds failed
    Veeam backup for aws Processing postgres rds failed: No valid combination of the network settings was found for the worker configuration AWS/Azure/OpenShift
  • AADSTS50020  User from Identity Provider does not exist in Tenant
    AADSTS50020: User from Identity Provider does not exist in Tenant AWS/Azure/OpenShift

More Related Articles

Create an S3 Bucket Backup Repository: How to Create Amazon S3 buckets AWS/Azure/OpenShift
Azure VM Creation With CLI 1 Deploy a Linux virtual machine (VM) on Azure using the Azure CLI AWS/Azure/OpenShift
HybridCloudTrust WHFB Hybrid Cloud Kerberos Trust Model is now available AWS/Azure/OpenShift
Building VPC Build a Scalable VPC for Your AWS Environment [Part 1] AWS/Azure/OpenShift
veeam backup for aws Processing postgres rds failed Veeam backup for aws Processing postgres rds failed: No valid combination of the network settings was found for the worker configuration AWS/Azure/OpenShift
AADSTS50020  User from Identity Provider does not exist in Tenant AADSTS50020: User from Identity Provider does not exist in Tenant AWS/Azure/OpenShift

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • hero windowsadmincenter
    How to set up Windows Admin Center on a Windows Server Windows Server
  • Trellix MVISOSN
    How to install Trellix MVISON Endpoint Security | Vulnerability Scans and Assessment
  • maxresdefault 2 2
    Fix Outlook Not Responding and Outlook Crashing or freezing Network | Monitoring
  • homebrew social card
    Package Manager for macOS: How to install Homebrew on macOS Mac
  • Featured image Periodic scanning
    How to enable or disable Windows Defender Antivirus Scanning periodically on Windows via Windows Settings Security | Vulnerability Scans and Assessment
  • Featured image TeamsGif.
    How to fix Microsoft Teams GIFs or Images not working Windows
  • SUBVERSION FEATURE
    How to Install Apache Subversion on a Linux System Linux
  • Edge browser
    Enable or disable Microsoft Edge from showing Web Content Windows

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,813 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.