I had the pleasure of spending a significant amount of time elbows deep in a Remote Desktop Services deployment this week. As part of the effort, I published the RDS RDWeb IIS page with the Azure AD Application Proxy so MFA can be leveraged for remote desktop services.
Today I took care of a cleanup task after the ADFS implementation. The problem: SSO did not work with Microsoft Edge and Chrome. When trying to access any Microsoft cloud services from a non-IE browser, I get directed to the web form landing page to enter a password. Continue reading “Single Sign On with Non-Internet Explorer Browser”
Once the Azure implementation of Active Directory Federation Services (ADFS) was in place I ran through the test process. Single Sign on works as expected from inside the network. Going to microsoftonline.com passes my client to the internal ADFS server where I enter my user name and get redirected to the Office 365 landing page. Doing the same from outside the corporate network works similarly only directing me to the external servers where I had to enter my domain UPN (username) and password. All well, but then…
The problem was connecting to an Office 365 site from a domain joined computer connected outside the corporate network via Direct Access (DA). In this scenario I get the prompt for username and password. This is not ideal, the end users expectation is to have the same experience through DA as in the office. Continue reading “Microsoft Direct Access and Azure Single Sign On”
Over the next few weeks I undergo a move of critical organization services to Office 365. Most of the subsequent posts will be related to activities required
to prepare the existing environment for O365. This post will focus on the three options for allowing users to access O365.
In order for users to access O365, they need to authenticate. Office 365 authenticating takes place with the help of Azure Active Directory. There are three options for authenticating to O365:
Continue reading “Accessing Office 365”