SSO

3 Topics

HTTP ERROR 401 - This page isn’t working right now. However, google Chrome works fine.
Hello all, I am currently getting a HTTP Error 401 message in Edge (Beta). It only happens when trying to authorise via ADFS, Azure AD authorisation is working as expected. When I try the same operation in Google Chrome, everything is working as expected (see pic). I have completed the following: Cleared browser history. Cleared password history. Removed any relevant entries from credential manager Renewed my certificate. Only other relevant info I can think of is that I changed my password at some point last week. Many thanks in advance.
andrewdashBHP
Jan 13, 2020 Place Enterprise
55KViews
0likes
2Comments
Block SSO for specific Edge profiles
Is it possible to block SSO for specific profiles in Edge? Here's my use case: I have a separate M365 tenant for development and testing. I am signed in to my computer with my work account, and I want to create Edge profiles for the user accounts I use to sign in to my dev tenant. I create a new profile, and when prompted to sign in and sync data, I enter the credentials for a dev tenant account. However, when I browse to, say, https://portal.office.com, I get automatically signed in with my work account. Ideally, I would like Edge to perform SSO using the credentials I entered for the dev tenant account when I set up the Edge profile, but I would settle for a way to block Edge from passing through the credentials for my work account.
Solved
Ryan Steele
Apr 24, 2022 Place Enterprise
8.2KViews
0likes
3Comments
Is there a way to have SSO for Office 365 when already signed in with a company account?
I signed into Edge with my company account. Then I browsed to admin.microsoft.com and I'm required to sign in again. Is there a way to have SSO working when I'm already signed into the browser? If not, then I want to suggest this feature. And it would be great if that worked on non-domain joined computers, too!
DanielNiccoli
Nov 14, 2019 Place Enterprise
625Views
0likes
0Comments