Quantcast
Channel: Azure Active Directory forum
Viewing all articles
Browse latest Browse all 16000

Azure AD Connect - no such host is known when configuring proxy

$
0
0

Hi,

We have an internal Exchange environment which we want to federate with O365. Initially we do not want mail flow to go to O365 - at this moment, I simply want to configure federation and will setup the MX and SPF records for Office 365 at a later date.

Our environment is as follows:

ADFS (internal server)

WAP (DMZ)

O365 subscription 

Port 443 is allowed from ADFS to Office 365 and the WAP. The WAP is allowed to communicate with the internal ADFS server using 443. I've installed AD Connect and entered my enterprise admin and O365 credentials, then chosen the option to configure ADFS using AD Connect. I hit an error with the "ADFS Farm\Proxy Servers" as I receive an error stating that "No such host is known". I have a few questions:

1. How can I get AD Connect to configure ADFS O365 federation ? Presumably I need to open management ports up between the WAP and AD Connect server?
2. Given that I don't want to configure mail flow for O365, are there any adverse results from selecting the hybrid configuration in AD Connect (I'm aware that certain Exchange attributes are written back on premise and that's fine).

Thanks

  


IT Support/Everything


Viewing all articles
Browse latest Browse all 16000

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>