![]() It also outlines an introduction to planning a single sign-on deployment when using Azure Active Directory (Azure AD). To fix this issue, please ensure that the outbound TCP port 9090 is allowed on the on-premises firewall, or the URL *. is allowed on the on-premises proxy server.This article provides you with information about the single sign-on (SSO) options that are available to you. GetDesktopSsoStatus One or more errors occurred. The URL of Service Endpoint is usually like If the outbound TCP port 9090 is blocked on the on-premises firewall, or the URL is blocked on the on-premises proxy server, then you may get the following error in the screenshot below during Azure AD Connect configuration.Īlso, by checking the log file named trace-date-number, which is located at: C:\Users\currentaccountname\AppData\Local\AADConnect, you can find the following error messages. ![]() What could be causes for receiving that message? In the docs that I found it simply assumes that 'it works'.ĭuring configuration, Azure AD Connect needs to communicate with Service Endpoint on TCP port 9090. I have the latest version (1.1.380.0) and for testing purposes I simply disabled the firewall on the machine I am trying to install Azure AD Connect on so there won't be a problem with port 9090. However, when I manage to fill everything in and end up in the tab 'Single sign on' I get an error with "Cannot retrieve single sign on status."Īfter research it seems that there was a 'bug' in some version of Azure AD Connect. ![]() I am trying out Azure AD Connect with the following: Added to example.local, so that users can log in using azure I have added an AD for "" and added a custom domain which has been verified.windows server 2012 R2 AD with example. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |