Windows 10 Teams/Other MS Cloud Services Error - WAM 80080300

[petben]

Hello, we are slowly seeing a propagation of an error with Teams showing the user 'Something went wrong' message when signing in. This is now also being noted in OneDrive and a bit of Outlook.

 

Teams logs have a fairly consistent error:

 

warning -- wamAccountEnumService: [AUTH] WAM enumeration response for AAD accounts was non-success. Status: 3. ErrorCode: 80080300.

 

We use AADConnect to sync our AD to Azure, nothing obvious here.

 

Has anyone seen this or has any ideas?

 

Thanks

[DavR]

Not massively reliant on MS cloud services here, but, I am getting Errorcode 80080300 and my OneNote isn't syncing properly.

 

Assuming a Microsoft service outage!

[Hybrid]

Hello, we are slowly seeing a propagation of an error with Teams showing the user 'Something went wrong' message when signing in. This is now also being noted in OneDrive and a bit of Outlook.

 

Teams logs have a fairly consistent error:

 

warning -- wamAccountEnumService: [AUTH] WAM enumeration response for AAD accounts was non-success. Status: 3. ErrorCode: 80080300.

 

We use AADConnect to sync our AD to Azure, nothing obvious here.

 

Has anyone seen this or has any ideas?

 

Thanks

 

Oddly enough, we're seeing this randomly now too.

 

Did you get anywhere with finding a solution? Nothing at all has changed on our network so we're a little perplexed at why it's starting to happen.

 

We're fully SSO and utilise OneDrive and Teams quite heavily, both of which are now failing to sign in automatically.

 

Do you use a Smoothwall at all?

[chris11256]

We're having the same thing this morning. Staff randomly not being signed into Office(and this coming up as inlicensed), with Outlook & Teams not working properly.

[psynegy]

I work with petben.

 

We are still seeing the issue this morning. Affecting Outlook, Teams, OneDrive, seemingly at random.

 

We do use Smoothwall, but we have taken a broken session, put it on a completely unfiltered/firewalled network and the issue has persisted.

 

We run Azure AD Sync, with password hash synchronisation.

[Hybrid]

I work with petben.

 

We are still seeing the issue this morning. Affecting Outlook, Teams, OneDrive, seemingly at random.

 

We do use Smoothwall, but we have taken a broken session, put it on a completely unfiltered/firewalled network and the issue has persisted.

 

We run Azure AD Sync, with password hash synchronisation.

 

That sounds identical to our issue, and setup incidentally. Ours started happening last week (Thursday) and it has persisted since then. Users see this error for OneDrive

 

 

Teams loads but the user just sees a message saying something went wrong.

 

Office apps come back as unlicensed.

[PlantHead]

https://support.microsoft.com/en-us/office/error-code-0x8004deb4-when-signing-in-to-onedrive-e8a8d97c-a87e-4dda-a67e-bae4fef05dcb

Security patch issue by the look of it

 

[Boredguy]

We had that on 1 user last week... they had logged on with a cached network profile before the station had updated it's IP address. A reboot of the station and it then worked fine.

[DavR]

Given the timing, I was wondering if this is a bug introduced by the latest round of Windows Updates? Haven't had a chance to test it yet though.

[Hybrid]

https://support.microsoft.com/en-us/office/error-code-0x8004deb4-when-signing-in-to-onedrive-e8a8d97c-a87e-4dda-a67e-bae4fef05dcb

Security patch issue by the look of it

 

 

Heck!

 

Do you know when this notification was released at all? I can't seem to see a date stamp.

[Boredguy]

Well the associated KB it refers to was created on the 04/08/2021 regarding connection issues signing in to Office 2016 (https://docs.microsoft.com/en-US/office365/troubleshoot/authentication/connection-issue-when-sign-in-office-2016) so it's been a possible issue for the last month or so?

[Hybrid]

I'm diving deeper into this now.

 

Looks like the machines/users that I'm having the issues with aren't hybrid domain joining any more. Event viewer spits out:

Device is not cloud domain joined: 0xC00484B2

AAD Cloud AP plugin call Plugin initialize returned error: 0xC00484B2

[chris11256]

In our case it's the remaining machies we had on 1909(about 8 of them) and it's completely random. A teacher could be fine period 1, but period 2 another teacher comes along and Office wants them to sign in, then rejects it and deactivates(we have 365 version deployed & it updates automatically).

 

The only thing in common these machines have is that they're 1909. I checked the Azure AD status and they're reporting normally.

[psynegy]

In our case it's the remaining machies we had on 1909(about 8 of them) and it's completely random. A teacher could be fine period 1, but period 2 another teacher comes along and Office wants them to sign in, then rejects it and deactivates(we have 365 version deployed & it updates automatically).

 

The only thing in common these machines have is that they're 1909. I checked the Azure AD status and they're reporting normally.

You think going 20H2 might solve the issue then?

[chris11256]

You think going 20H2 might solve the issue then?

 

I've updated one of them during a free period and suspect so. We've had no reports of this problem on our 20H2 machines at all.

[chris11256]

Just to update this on our problem. I upgraded the 8 problematic computers to 20H2 on Monday night and the problems with Office & Teams have gone away, all teachers concerned report everything is now working normally.

[Hybrid]

Just to update this on our problem. I upgraded the 8 problematic computers to 20H2 on Monday night and the problems with Office & Teams have gone away, all teachers concerned report everything is now working normally.

 

Are your machines registering as normal on Azure AD now, Chris?

 

We found that a simple restart of the PC kicked the whole thing into play again and it started working as expected. Obviously not a concrete fix, but it gets them back on again.

[chris11256]

Are your machines registering as normal on Azure AD now, Chris?

 

We found that a simple restart of the PC kicked the whole thing into play again and it started working as expected. Obviously not a concrete fix, but it gets them back on again.

This has now been published in the Office 365 status page, MS confirm a reboot does fix the problem.

 

Although to be honest I did need to upgrade those machines to 20H2 anyway, they were are last remaing ones.

[MartinByard]

We've got a few machines with this issue as well (all 1909) and the MS recommendation we saw was several reboots after installing the update can resolve it - seems to have worked for us so far ... but your mileage may vary.

[psynegy]

We have found that reboots do not always resolve this. MS do give a recommendation of using the web apps if a reboot does not resolve it, so, they know very well that it's not a fix for everyone.

[Hybrid]

Just in case anyone was having this issue, MS released a statement and 'fix'.

https://admin.microsoft.com/AdminPortal/Home?ref=MessageCenter/:/messages/MC257668

 

Message Summary

Problem detected: Some users on Windows version 19H2 may be unable to connect to desktop clients for some Microsoft 365 services, including Microsoft Teams, Outlook, and OneDrive for Business.

 

As described in Service Health Dashboard post MO257074, we’ve detected a problem related to some Windows clients running version 19H2, and specifically the update delivered via KB 5003169. We are sending you this communication because we’ve determined that your organization has some users running Windows version 19H2 and if they have taken the update they may have issues connecting to one or more Microsoft 365 services. The following communication provides instructions on how to correct the problem for any affected users.

 

How this will affect your organization:

 

Users affected by this problem are potentially unable to connect to Microsoft 365 services including Microsoft Teams, Outlook and OneDrive for Business. When encountering this problem, users may see the following errors: "We're sorry – we've run into an issue," or “80080300” when attempting to connect or sign in.

 

What action do I need to take:

 

To fix this problem for users that are reporting this issue on devices that have already installed Windows Update KB 5003169, we’ve confirmed that an additional device reboot will resolve the problem.

For users on Virtual Desktop Interface (VDI) clients, we have confirmed that a reboot of the underlying VDI host may also be required.

For users on devices which have yet to install Windows Update KB 5003169, those devices will require an additional reboot after the final automated Windows Update restart, and any hosts of VDI instances should also be rebooted as part of this process. We recommend incorporating these steps into your update process as you adopt Windows Update KB 5003169.

[rickjames]

Trying to decide if this issue I have is related to this MC

 

I have a user who is unable to sign into Teams all of a sudden after being enrolled for MFA last week. When they open the application, they get this message.

 

 

After clicking next, they then get this below

 

 

The user does not get a code sent to their phone either. I have revoked any sessions as well as made them re-register for MFA, but it still seems to happen

[psynegy]

Trying to decide if this issue I have is related to this MC

 

I have a user who is unable to sign into Teams all of a sudden after being enrolled for MFA last week. When they open the application, they get this message.

 

[ATTACH=CONFIG]61924[/ATTACH]

 

After clicking next, they then get this below

 

[ATTACH=CONFIG]61923[/ATTACH]

 

The user does not get a code sent to their phone either. I have revoked any sessions as well as made them re-register for MFA, but it still seems to happen

It doesn't sound like it, no.

 

Best place to look at stuff like that, I've found at least, is the Azure AD > Sign Ins section, you can usually see some fairly detailed logging there. Good luck!

[rickjames]

It doesn't sound like it, no.

 

Best place to look at stuff like that, I've found at least, is the Azure AD > Sign Ins section, you can usually see some fairly detailed logging there. Good luck!

 

Done that, there's failures in the log section saying 'Strong Authentication Required'. Seems a bit weird, because up until yesterday they were fine; we haven't changed anything in relation to our MFA setup either.

 

Thinking about it now I'm wondering if it's registry related.

[Hybrid]

For that, I think I'd be just disabling MFA for the user and recreating it again. Get them to check their MS account too. https://account.microsoft.com/security