Error code :80180006

Chadi Boustani 200

Hello Everyone. Trying to enroll devices with microsoft intune using company portal. When trying to sign in receiving error code :80180006 Server message: Unknown error code 0x80180006 Environment is WIN 10 pro 22H2: build 19045. Any advice on how to fix? Thanks

Ginette Hughes 45 Reputation points

2024-01-11T18:44:53.6933333+00:00

I am having the same issue, and also my user account and all folders in it have been hidden.
Sam Huff 80 Reputation points

2024-01-12T13:21:41.9933333+00:00

I am getting the same error message. This happened to two different users, employee that has been with us for about year switching to a laptop running Windows 11 Pro, 10.0.22621 and a brand new employee with a brand new laptop, running Windows 11 Pro, 10.0.22631. This happens when they sign into anything that requires a work/school account. After they use their MS Authenticator app to authenticate, they are asked if they want to register their device with the company policy. After about 30 seconds or so they get this message. I have tried the steps above with no success.
05453900 5 Reputation points

2024-01-12T13:26:43.4166667+00:00

Check your internet connection. Update your Company Portal app. Clear the app cache or reinstall it. Give your device a reboot. Double-check time and date settings. Make sure Windows 10 Pro is up to date. Verify Intune service status. Check Event Viewer for more details. If the hiccup persists, reach out to Microsoft Support.
Jason 45 Reputation points

2024-01-12T13:45:35.8733333+00:00

Also receiving the same error. Been happening for the past 3 days. Not using Intune though, just Entra. Tried on multiple devices on multiple networks with multiple users. Always returning the same error as posted above. Entra Device logs show the device being added, registered and then immediately deleted. Event Viewer always has the following errors: Error 52 MDM Enroll: Server Returned Fault/Code/Subcode/Value=(a:InternalServiceFault) Fault/Reason/Text=(Sorry, something went wrong. Please try again. Call ID: <removed>.). Error 11 MDM Enroll: Failed to receive or parse certificate enroll response. Result: (Unknown Win32 Error code: 0x80180006). Error 71 MDM Enroll: Failed (Unknown Win32 Error code: 0x80180006)
Sam Huff 80 Reputation points

2024-01-12T13:58:47.0533333+00:00

I can confirm with Jason's comment I see the same thing happening in our logs as well.
Matthew Grant 60 Reputation points

2024-01-12T17:13:05.2333333+00:00

I am also receiving this same error code attempting to run intune on new laptops for our users. I'm thankful to know that my company is not alone in this issue. We had a seamless deployment up until this error. It's affected both registering intune as well as attempting to sign into any office suite if we attempted to work around the intune issue.
Timothy Conard 30 Reputation points

2024-01-12T18:09:59.7066667+00:00

Happening for my company as well, for the past 3 days. We use Intune for mobile phones, but not for laptops. Confirmed with 3 test users on 3 different computers.
JC 15 Reputation points

2024-01-12T20:19:02.25+00:00

Same exact issue here as well across multiple tenants. I know Microsoft reported some issues this morning. I'm wondering if this is part of the outage.
Christian Jackson 25 Reputation points

2024-01-12T20:32:09.84+00:00

Same thing happening at my job. Multiple brand new laptops that I cannot sign in to register office with. Also tried on a few desktops that we have setup around here under new profiles and receive the same issue. Becoming a big problem.
Convivial 10 Reputation points

2024-01-15T09:58:25.6366667+00:00

I have the same issue and can confirme Jason`s comment. It stated the 10 january for me too.
Tugay Kaya 10 Reputation points

2024-01-15T19:24:08+00:00

I have the exact same errorcode when enrolling a devices. It is very time consuming for us.
Jet Letters 10 Reputation points

2024-01-16T06:04:49.29+00:00

Having the same issue from 15th - 16th Jan I have tried this across different tenants. 2 failed with the same 80180006 errors and 1 worked. We are not using this for Intune enrollment, only just to use SSO and link the account to Windows for easy sign in for users. Microsoft support has been useless so far.
Ricardo Oliveira da Silva 1 Reputation point

2024-01-16T21:32:15.44+00:00

I got the same error message here, in a computer (desktop) at the office, connected to the network, and of course joined on a domain. It was not running Office products. I reviewed everything on user account and it was fine. I just disconnected the Work or School account and everything is working now. This computer was working fine with that Work or School account, now looks like it does not need it anymore. No Work or School account is needed.

I would say to you to disconnect Work or Shool account and try again. Please, let me know if that works. Thanks. Ricardo.
JM Lapointe 5 Reputation points

2024-01-17T17:07:57.3433333+00:00

Same here since the 15th. Exact same error messages and behavior. For now only a fiew users affected in our organization. I'm on the IT team and I myself am affected by this problem. It wasen't clear to me up until reading all of your posts what was causing this. But now it looks it is on MS's side. Hope it is resolved soon.
David Turner 66 Reputation points

2024-01-18T13:27:55.2033333+00:00

Same here, added then unregistered
Matthew Hankel 10 Reputation points

2024-01-18T22:01:14.61+00:00

I have been having the exact same issue with the exact same error code. It works fine as others have said if you uncheck allow organization to manage my device, but then you have to individually sign into every app, and also it doesn't register with entra at that point. I noticed it started on Wednesday the 10th for me, and prior to then never had this issue. I tried on 5 different devices, I created test accounts and all had the same issue, even on different internet connections. I tried workarounds from online and nothing worked. I am glad to see this is not just me.
Greg Hartman 0 Reputation points

2024-02-05T14:41:08.4566667+00:00

I had a similar issue, turns out the account I was using was not configured as Local Admin. Rookie mistake, I know. However, it did not save my config for the account for some reason and when I tried adding it to Entra, I got this message. In short, confirm the account you are using is a local Admin
Chad Brown 0 Reputation points

2024-02-05T18:07:55.2866667+00:00

Hi All, I finally got a decent tech from Microsoft to explain. What's gone unnoticed is the WIP/MAM section got changed in January. The suggestion is to set the scope to NONE because it was confirmed to me that the old WIP application policy will get processed in the MDM scope. We intend to test this further.

OLD:

NEW:

22 answers

Neil Wilson 0 Reputation points

2024-01-19T15:36:05.79+00:00

Someone posted on here earlier but it seems to have disappeared - but thank you anyway! Resolved for us by changing the MAM/WIP intune setting to "Some" and excluding (well, not including) certain users (in particular those with AD joined machines - they are not hybrid joined, just AAD registered) - took about 20-30 mins to take effect but it worked.

Thank you!
Please sign in to rate this answer.
Anonymous

2024-01-23T04:50:17.0333333+00:00

I tried this and still didn’t work
Sign in to comment
RikC 0 Reputation points

2024-01-19T21:16:43.5233333+00:00

I was looking at this thread as I installed a new PC with Windows 11 Pro and tried to connect to my work account and kept getting the 80180006 error when trying to do so. And when trying the option --> 'Enroll only in device management' as recommended in this topic and got a 80180014 error which stated that my version of windows wasn't supported by my company which struck me as odd. So I contacted my company helpdesk and they gave me a standard answer about running windows update when getting an actual answer Thus, I saw all the recent messages in this topic and figured this problem might resolve itself in due time and that I was just unlucky in my timing in getting a new pc. Then I figured I'd try one more thing - install office and connect it to the company account. And this worked after unchecking 'allow the company to manage my device'. After that my account also is displayed in the configuration screen as a connected work/school account! So I somehow bypassed this problem as an end user in this manner :-).
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
James Walz 0 Reputation points

2024-01-23T15:23:58.7033333+00:00

I have a fix. On the domain PC, login with a domain admin account/Global Admin Account and add the PC/LAPTOP to "Account>Access Work or School" and "Enroll only in device Management." Make sure you us the Global Admin Account to enroll the deivce. Use the following URL "https://enrollment.manage.microsoft.com/enrollment/discovery.svc "/ to enroll. It worked for me. Then reboot. If you check the portal for the device it will ONLY show up as Intune Registered. Now log in with the users domain account and add the work account. Once thats completed the device will show up as a "Corporate" Device, and Entra Registered.
Please sign in to rate this answer.
James Walz 0 Reputation points

2024-01-23T15:31:03.2466667+00:00

One other thing run the "dsregcmd" command before and then after to compare the results. Also check the Event Viewer>Applications and Service logs>Microsoft>Windows>User Device Registration
Sign in to comment
Abhinav 0 Reputation points

2024-01-24T19:10:44.7166667+00:00
Faced the same issue while setting up a new Windows 11 laptop for an employee, and trying to add their O365 account through "Access Work or School".

Resolved by following these steps:

Access Work or School

Enroll only in device management -> add user O365 credentials

Restart computer

Access Work or School -> Add a work or school account (Connect) -> enter user O365 credentials

Look for "Connected by username@org.ca (Connected to <org> MDM)" -> Disconnect

Voila! Issue resolved.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
John Doe 5 Reputation points

2024-01-31T13:10:26.2566667+00:00

I just had a call with a Microsoft representative and during that call we found a permanent workaround that works for our use case.

The fix is to register the device via MS Edge and uncheck the box that says "Allow my organization to manage my device".

Afterwards, the device is registered in the "Work or School account" options.

The steps are described in this MS article:
https://learn.microsoft.com/en-us/entra/identity/conditional-access/how-to-app-protection-policy-windows#sign-in-to-windows-devices

Client Information:
W10 22H2
Active Directory joined (on-prem)
Please sign in to rate this answer.
Chris Wilkinson 0 Reputation points

2024-01-31T13:15:25.0866667+00:00

Not really a fix but it is a workaround. Correct me if I'm wrong but that means the device is not undermanagement which would be a security risk. MS should really fix this properly

John Doe 5 Reputation points

2024-01-31T13:20:07.6733333+00:00

You can also follow the advice in this reddit thread and set WIP user scope to "none" and restore the default URL's.

However, to me this seems like a hail mary approach as this might result in unexpected behavior in other areas.

As I mentioned for our use case this is perfect as we currently do not join our devices into intune and only register them within Entra ID which this approach allows us to do again with no additional workload.
Sign in to comment

Share via

Error code :80180006

22 answers