Error AADSTS165000 when launching portal.office.com

David - QCH 85

We have several users reporting an AADSTS165000 error when launching portal.office.com from their work computers. This issue is present for a portion of our users across multiple devices and browsers, Edge and Chrome. During testing we tried the following links as alternatives but they all produce the same issue.

https://portal.office.com?domain_hint=domain.com

https://office.com/login?domain_hint=domain.com

https://microsoft365.com/login?domain_hint=domain.com

Clearing the browser cache will allow the user to login once before returning to the same error on next launch.

Other links including Office.com and outlook.office.com are functioning as a workaround but this does not provide a permanent solution. We require a working link that allows the user to access the main O365 portal page without having to click the sign-in button on the main office.com site.

We experienced this issue for a few hours on Friday and thought it was resolved but it was reported again this afternoon.

User's image

Error is as follows;

Request Id: 5c47017d-aca9-4d80-8838-7f1ccfe1ae00

Correlation Id: 479d28d7-bc57-423c-8ed2-d9e0b78d7991

Timestamp: 2023-06-20T21:32:04Z

Message: AADSTS165000: Invalid Request: The request did not include the required tokens for the user context. One or more of the user context values (cookies; form fields; headers) were not supplied, every request must include these values and maintain them across a complete single user flow.

Notable Details

Edge: 114.0.1823.51

Chrome: 114.0.5735.110

OS: Windows 10 22H2 (Desktops) and LTSC 1809 (VMware Horizon)

Antivirus: Crowdstrike

Thanks in advance for any help you can provide.

XuDong Peng-MSFT 10,176 Reputation points Microsoft Vendor

2023-06-21T06:20:38.92+00:00

Hi @David - QCH,

Looks like an authentication issue. Have you tried the InPrivate mode in Edge, does it has same issue?
David - QCH 85 Reputation points

2023-06-21T11:40:16.2733333+00:00

Hi @XuDong Peng-MSFT

In InPrivate mode I am able to log in manually to portal.office.com.

After further testing last night the issue appears to be related to the SSO process for domain accounts but only using the links that access the portal landing page. Our other shortcuts that access services like Outlook and Teams directly are working without issue. eg https://outlook.office365.com/domain
Tom Sztur 0 Reputation points

2023-06-22T00:40:16.5433333+00:00

We have the same issue with a couple of users - very odd.

Even a brand new Chrome profile same issue.

Let me know if you find an answer. - looks like our issues are dated around the same day.

Possibly an MS issue - although nothing in their status page indicating any such advisories.
Egon Gamper 0 Reputation points

2023-06-23T18:23:59.71+00:00

Same problem here. ESET AV and Sonicwall FW. Clearing Browser History or Incognito mode works for a while. outlook.office.com/?realm=domain.com works but portal.office.com/?realm=domain.com not.
David - QCH 85 Reputation points

2023-06-23T18:41:00.27+00:00

Hi @Tom Sztur & @Egon Gamper Thank you for confirming that this issue is not limited only to our site. I currently have tickets open with both Office365 and Azure support, I'll be sure to include any provided solution in this thread.
D Sharman 0 Reputation points

2023-06-26T08:38:29.99+00:00

was there a solution to this ? we have been seeing this with users across a couple of sites, but am currently struggling to narrow down the issue, clearing browsing data does get it going for a bit but then it stops working again
Kumar Krishnamoorthy 1 Reputation point

2023-06-27T02:06:13.94+00:00

We are noticing same issue across multiple sites as well.
Christian Schett 0 Reputation points

2023-06-28T10:26:02.0733333+00:00

Same problem in Chrome und Edge since yesterday. Only Firefox works.
Wesley van den Brink 5 Reputation points

2023-06-28T12:43:45.7566667+00:00

Did anyone have a fix this problem?

Only way we could fix this is opening Chrome with a batchfile and load the pages after 3 seconds instead of all at the same time.
CiprianITDTVH-5530 0 Reputation points

2023-06-28T14:28:31.2+00:00

We've got the same issue at our site. Seems largely random, happens to some users on a workstation but other users have no issues on the same workstation. The volume of reports is also random, we had several users report it June 23rd but the past two days have been quiet. Today we've received a bunch of additional reports.

Clearing the browsing history will solve the issue one time only, subsequent attempts to go to portal.office.com causes the login to fail with the same error. One workaround is to go to outlook.office.com > waffle icon in top right but that's not ideal.
Beauregarde Young 75 Reputation points

2023-06-28T18:39:35.6233333+00:00

We are having a smattering of users with the same issue. One user did report that they were able to sign in after clearing their cache and cookies and restarting several times. The others have not reported back that they were able to successfully log in, though they also didn't say if they tried clearing their cache and cookies. I will also open a ticket with Microsoft about it to ensure it's getting appropriate attention.
Jasper van de Kraats 15 Reputation points

2023-06-29T08:22:07.5333333+00:00

We are getting this when logging in to websites using SSO. But it only occurs when the browser is not yet opened and two sites with SSO are opened at the same time. It seems to confuse the two SSO sessions and randomly one of them will result in this error.
CiprianITDTVH-5530 0 Reputation points

2023-06-29T14:16:18.8233333+00:00

FVH Jun 29, 2023, 3:02 AM The issue only occurs in very specific situations. When no other connection to Office apps has been made already (Teams, Outlook, Sharepoint, OneDrive, ...) and one tries to connect to https://portal.office.com (e.g. using the "Office Online" icon on desktop, you can get the error. Our Home page connects to Sharepoint, so when a browser is opened first, our users do not get the error, but when no browser is open yet (and no other connection to Office Apps is active), when users try to connect to "Office Online" they seem to get the error. We managed to find a workaround on this issue, normally when browsing to https://portal.office.com, after providing credentials, the landing page is https://www.microsoft365.com/?auth=2. When changing the URL behind the "Office Online" icon to this URL, our users do not get the error. Looks like something has changed at Microsoft with the signon process on the "portal.office.com" website (as previous comments also have stated)

We found the same solution that FVH mentions. Changing our shortcuts to https://www.microsoft365.com appears to have resolved the issue for now and we are no longer receiving reports of issues.

That is until that URL breaks too. :D
Wesley van den Brink 5 Reputation points

2023-07-07T14:36:21.8133333+00:00

Anybody got a fix for multiple SSO tabs or reply back from Microsoft support on this issue?
David - QCH 85 Reputation points

2023-07-07T14:46:33.2433333+00:00

Hi @Wesley van den Brink I still have two support requests open with Microsoft and the most recent reply I received was that multiple clients have reported issues with portal.office.com and they suggest using https://www.microsoft365.com as a workaround.

I tried updating the link to microsoft365.com and get the same error as portal.office.com when using the domain_hint to allow for SSO. Our workaround has been to have staff use the direct links for Outlook and Teams.

https://outlook.office365.com/domain

https://teams.microsoft.com/_?realm=domain

6 answers

LINDROS99 0 Reputation points

2024-03-28T13:07:10.83+00:00

Just noticed this, this week.

I'm wondering if Microsoft has stepped up re-auth on conditional access, and/or is shortening TTL for sessions.

I can force this to occur by "pinning" office.com/?auth=2 in Chrome, then at the end of the day, leaving the browser session active, and coming back the next morning.

Note that it used to maintain the "welcome to Microsoft 365" page (overnight), but now users return to "Trust [company_name].com?" ... and then the error page occurs.

Again, for us it's a brand new issue - did not occur last year.

This coupled with Teams garbled audio with expensive mics is pushing us to explore Google Workspace and dump 5000 seats of E5.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment