Error code 80180002

Some customers have reported that an error message prevents them from adding work access to Microsoft 365. In this blog, we will go over the…

Some customers have reported that an error message prevents them from adding work access to Microsoft 365. In this blog, we will go over the most effective solutions to help you resolve the error code 80180002 when adding work access to Microsoft 365. Follow through for more information on how to resolve error code 80180002.

How to fix error code 80180002 when adding work access to a PC running the Windows operating system:

  1. Firstly, sign in to Office 365.
  2. Click on the launcher.
  3. Now click on “Admin”.
  4. Under “Admin centers” click on “Azure Active Directory”.
  5. Click on “All services”.
  6. Now click on “Azure AD Conditional Access”.
  7. In my example, there is a policy that causes the error.
  8. Select and remove it to resolve the issue.

In this blog post, I’ll explain the causes of this error and demonstrate the steps you must undertake to fix it, including screenshots along the way.


Causes of the error 80180002 in Microsoft 365

When the error occurs a warning similar to the one shown above will display complete with the error code ID and the code itself. This allows you to reference this issue and find a solution to help mitigate the error. The error correlation ID is your maid ID liked with your account. You may require this if you have the issue fixed by a professional group of individuals.

Error Code 80180002 can be caused by a number of various problems. The following are the most Prevalent reasons for this error message:

  • Errors in the registry
  • System files that have been mistakenly associated with and removed by other applications.
  • Viruses or malware that cause application or system file corruption
  • Installations that haven’t been completed to their full potential

Common symptoms include:

  • Runtime issues with previously working apps
  • Your computer’s reaction time to commands input using the keyboard or mouse is slow.
  • You’re having trouble shutting down or setting up your computer.
  • An error notice about your registry, updates, or response time has shown.

You can try a variety of different techniques to try to fix Error Code 80180002. Because the problem has various roots, some of the approaches used to properly resolve the issues are rather easy, while others require extensive knowledge or expertise. If the procedures listed below aren’t effective in resolving the problem, or if you aren’t confident in your ability to use them, hire a competent Windows repair professional to help you.

security office365 windows 11

info Recommended Software

Additional Information and Repair Instructions for error code 80180002

There are several strategies you may take to try to fix the difficulties underlying Error Code 80180002 due to the variety of circumstances that might lead to the error. While some of these procedures are simple to follow, others may necessitate the use of applications such as registry cleaners and driver installation wizards. If you are unsure about using such software, call a trained Windows repair specialist for assistance.

Fix error code 80180002 in Microsoft 365 by cleaning out the registry

There are many different registry cleaning software available on the Internet, but not all of them come from reliable sources. You can use the registry cleaning utility included in your Windows software package instead of trusting a file from an unknown vendor.

Run this utility to do a file scan and determine which ones may need to be repaired. Most of the time, the registry cleaner can repair the relevant files and fix the problem on its own.

It’s a good idea to restart your computer after using the registry cleaner to ensure that your computer can appropriately examine the newly restored files.

Fix error code 80180002 in Microsoft 365 by making sure your drivers and software are up-to-date

Error Code 80180002 occurs when drivers are out of date in some circumstances. If you feel this is the case, you may check the status of your different drivers by going into your operating system’s settings and selecting “Update Drivers.”

You may also check your system for any essential Windows software updates that may help you resolve the problem code.

After you’ve double-checked and installed any required drivers, restart your computer to completely implement any changes made during the installation process.

  • Firstly, sign in to Office 365.

Use your regular login details to sign into to your account.

  • Click on the launcher.

The launcher is illustrated by nine dots, click on this to access it.

  • Now click on “Admin”.

  • Under “Admin centers” click on “Azure Active Directory”.

I have Azure Active Directory, pinned to the Admin page, however, if you haven’t click on “Show all”.

  • Click on “All services”.

All service is a feature within to allow users to access the entire Azure directory feature page.

  • Now click on “Azure AD Conditional Access”.

  • Select and remove it to resolve the issue.

That’s it for this Blog thank you for taking time out to read our content, please feel free to email our team about how it went if you followed the steps or if you need more help with the questions we answered in this Blog.

One of my customers recently decided it was time to upgrade their systems. Their entire operation is home-based for each employee, so we had their systems delivered directly to their homes. We got started with the process of logging in and activating Office 365 (they are running E3 licenses), and ran into a number of errors that all basically just give a code and say «Something went wrong…»
Documentation is very sketchy on the errors, and they all seem to reference InTune, but InTune has never been part of this customer’s setup, and all of their pre-existing systems work fine.

We managed to find a work-around for one user, and got their system fully activated, but that was followed by Outlook being unable to access their email account. An Exchange engineer from MS was able to get us the rest of the way working, but after several hours of messing with it and doing repairs with the SARA tool on 1 system, I wasn’t about to do this on all the systems. And it’s a good thing I didn’t, because 3 days later Outlook is hanging for up to a minute followed by kicking the user out and asking for a log in every 10 minutes.

I have spent inordinate amounts of time troubleshooting this myself over the last several weeks, with no results. I have been able to prove that these systems have no problem logging into my own O365 account as normal (we’re running MS 365 Business Standard, not E3) and I’ve also wiped one of them and found that even a fresh version of Win10 Pro and Office is still unable to sign-in/activate (so it can’t be anything the system integrator did).

We’re approaching 4 weeks since the systems were purchased, the customer is pissed, the systems integrator is willing to help, but there is a limit to the ways they can help, and MS is basically incompetent as they can’t even get someone on their Azure team on the phone to speak with me, but have had the Exchange team speak with me twice, even though I was very clear that I needed to speak with the Azure team.

I would appreciate any help or advice anyone has to offer. (Yes, I plan to cross-post this in r/O365 or wherever makes sense.) Also going to see about adding screenshots of the errors.


Value: -2145910782 | 0x80180002 | 2149056514

What does it mean ?

MENROLL_E_DEVICE_AUTHENTICATION_ERROR

 

Windows MDE: Server failed to authenticate the user.

Value: 2 | 0x0002 | 0b0000000000000010

Where does it come from ?


FACILITY_WINDOWS_CE

 

Windows CE
Value: 24 | 0x018 | 0b00011000

fix-microsoft-teams-error-code-80180002-something image

WebJun 18, 2021 Steps to Fix Microsoft Teams Error Something Went Wrong Error Code 80180002 Unknown Error Code 0x80180002 Step 1) Disconnect Old Work and school account, then sign out …
From youtube.com
Author AarohanTechSol
Views 33.6K
See details »


[SOLVED] ERROR JOINING AZURE AD DOMAIN — THE …

solved-error-joining-azure-ad-domain-the image

WebJan 8, 2020 We have a client using 365 business, fully Azure AD, no hybrid. We have a new Windows 10 PC and are getting Server error code: 80180023 when trying to join the domain. PC has internet, DNS is fine, …
From community.spiceworks.com
See details »


80180002 ERROR — MICROSOFT COMMUNITY

80180002-error-microsoft-community image

WebJan 20, 2023 Created on July 11, 2020 80180002 error Hi there, I’ve use Windows 7 before so was time to get windows 10 on my PC so now I have PC and laptop running Windows 10. When try sign in to my one of …
From answers.microsoft.com
See details »


SOMETHING WENT WRONG ERROR CODE 8018001C ENTERING …

something-went-wrong-error-code-8018001c-entering image

WebAug 20, 2021 1. Sign in to the Microsoft Endpoint Manager admin center https://go.microsoft.com/fwlink/?linkid=2109431 . 2. Go to Users > All Users. 3. Select the affected user account, and then click Devices. 4. Select any …
From answers.microsoft.com
See details »


FIX UNKNOWN ERROR 0X80070002 IN MICROSOFT OUTLOOK — SPICEWORKS

WebBy default Outlook creates its data files (PST) at one of the two following locations: • AppDataLocalMicrosoftOutlook • DocumentsOutlook Files
From community.spiceworks.com
See details »


YOUR ACCOUNT WAS NOT SET UP ON THIS DEVICE BECAUSE …

WebApr 16, 2021 According to the Error code:80070002, you might be experiencing Windows activation issues, but since you post in Microsoft 365 community, we should confirm with …
From answers.microsoft.com
See details »


CAN’T ADD OFFICE 365 EMAIL TO MY MICROSOFT ACCOUNT

WebWhen I try to add my school’s Office 365 account on my computer, I repeatedly get the error code 80180002 and a message that reads «your account was not set up on this …
From answers.microsoft.com
See details »


OFFICE ERROR «ACCOUNT NOTICE: WE’VE RUN INTO A PROBLEM WITH YOUR …

WebStep 1: Make sure your Microsoft 365 for Home, Personal, or University subscription is active Close all Office apps. Go to your Services & subscriptions page. If prompted, …
From support.microsoft.com
See details »


ERROR CODE 80180014 — MICROSOFT COMMUNITY

WebJan 20, 2023 You may need to contact the admins of the Office 365 tenant for help. In this article: Troubleshoot Windows device enrollment problems in Microsoft Intune. We can …
From answers.microsoft.com
See details »


MDM ENROLLMENT ERROR 0X8018002B ON WINDOWS 10 1709

WebDec 28, 2017 MDM Enrollment Error 0x8018002B on Windows 10 1709 1 1 34 Thread MDM Enrollment Error 0x8018002B on Windows 10 1709 archived cdacf477-87ac-42d5 …
From social.technet.microsoft.com
See details »


TROUBLESHOOT WINDOWS 10 INTUNE AUTO-ENROLLMENT ERROR …

WebOct 28, 2022 Solution Use the following steps to fix the issue. On the affected device, open an elevated Command Prompt window, and then run the dsregcmd /leave command. …
From learn.microsoft.com
See details »


USER GETTING 8018002 ERROR WHEN TRYING TO REGISTER DEVICE …

WebAug 23, 2020 In Windows 10>Settings>Account>Access Work> Connect, device registration fails and returns 80180002 error. Activating Office 365 desktop apps returns …
From learn.microsoft.com
See details »


ERROR CODE 0X80080002 — MICROSOFT COMMUNITY

WebDec 5, 2009 To do this, follow these steps: Click Start, click Run, type services.msc, and then click OK. Right-click the Automatic Updates service, and then click Stop. …
From answers.microsoft.com
See details »


ERROR CODE 80180002 — MICROSOFT COMMUNITY HUB

WebJan 12, 2023 If you’re a client only, you need to ask your IT admin to fix this. While, if you’re the IT admin, you need to change the Scope to None for both MDM and MAM via …
From techcommunity.microsoft.com
See details »


80180002 ERROR CODE — MICROSOFT COMMUNITY

WebMar 10, 2021 ZE zeyer Created on March 8, 2021 80180002 error code Your account was not set up on this device because device managenement could not to be enabled.This …
From answers.microsoft.com
See details »


Related Search


Hi I am getting the following error when trying to auto-enroll hybrid Ad joined devices to Intune.

Auto MDM Enroll: Device Credential (0x0), Failed (Unknown Win32 Error code: 0x8018002b)

I ran dsrecmd /status and go the following.

===========================================

PS C:Usersuser> dsregcmd /status                                                             
                                                                         
                                                  
+———————————————————————-+
| Device State                                                         |
+———————————————————————-+

             AzureAdJoined : YES
          EnterpriseJoined : NO
              DomainJoined : YES
                DomainName : contoso

+———————————————————————-+
| Device Details                                                       |
+———————————————————————-+

                  DeviceId : 34b1d597-68f2-4d59-86ce-b2fc0exxxxxx
                Thumbprint : B6B241987D54D10468FE74FAExxxxxxxxxxx
 DeviceCertificateValidity : [ 2020-04-16 04:37:38.000 UTC — 2030-04-16 05:07:38.000 UTC ]
            KeyContainerId : 4c0a6fbf-1e4a-469d-b740-b8353bxxxxxx
               KeyProvider : Microsoft Platform Crypto Provider
              TpmProtected : YES

+———————————————————————-+
| Tenant Details                                                       |
+———————————————————————-+

                TenantName : Contoso, Inc.
                  TenantId : 3db4791b-32eb-4576-a3bb-42b6e4c0d3a5
                       Idp : login.windows.net
               AuthCodeUrl : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/oauth2/authorize
            AccessTokenUrl : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/oauth2/token
                    MdmUrl :
                 MdmTouUrl :
          MdmComplianceUrl :
               SettingsUrl :
            JoinSrvVersion : 1.0
                JoinSrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/device/
                 JoinSrvId : urn:ms-drs:enterpriseregistration.windows.net
             KeySrvVersion : 1.0
                 KeySrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/key/
                  KeySrvId : urn:ms-drs:enterpriseregistration.windows.net
        WebAuthNSrvVersion : 1.0
            WebAuthNSrvUrl : https://enterpriseregistration.windows.net/webauthn/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/
             WebAuthNSrvId : urn:ms-drs:enterpriseregistration.windows.net
    DeviceManagementSrvVer : 1.0
    DeviceManagementSrvUrl : https://enterpriseregistration.windows.net/manage/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/
     DeviceManagementSrvId : urn:ms-drs:enterpriseregistration.windows.net

+———————————————————————-+
| User State                                                           |
+———————————————————————-+

                    NgcSet : NO
           WorkplaceJoined : NO
             WamDefaultSet : YES
       WamDefaultAuthority : organizations
              WamDefaultId : https://login.microsoft.com
            WamDefaultGUID : {B16898C6-A148-4967-9171-64D755DA8520} (AzureAd)

+———————————————————————-+
| SSO State                                                            |
+———————————————————————-+

                AzureAdPrt : YES
      AzureAdPrtUpdateTime : 2020-04-17 15:21:59.000 UTC
      AzureAdPrtExpiryTime : 2020-05-01 22:38:04.000 UTC
       AzureAdPrtAuthority : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5
             EnterprisePrt : NO
    EnterprisePrtAuthority :

+———————————————————————-+
| Diagnostic Data                                                      |
+———————————————————————-+

        AadRecoveryEnabled : NO
               KeySignTest : PASSED

+———————————————————————-+
| Ngc Prerequisite Check                                               |
+———————————————————————-+

            IsDeviceJoined : YES
             IsUserAzureAD : YES
             PolicyEnabled : NO
          PostLogonEnabled : YES
            DeviceEligible : YES
        SessionIsNotRemote : YES
            CertEnrollment : none
              PreReqResult : WillNotProvision

===============================

I have assigned proper group policy, configure MDM auto enrollment in Azure Ad and assigned (E5, P2, and Intune) license to the user. The user is also local admin on the computer. 

I get the error even when I am using autopilot to register computer as Azure AD and enroll in Intune. The computer registers in Azure Ad but not in Intune. 

Я не могу войти в свой профиль Microsoft Teams, каждый раз появляется ошибка 80080300. Сообщение вообще ни о чем: «Мы сожалеем, что столкнулись с проблемой». Есть ли что-то, что я могу сделать?

Решение

Здравствуйте! Предлагаю вам выполнить следующее:

  • Перейти на другую учетную запись Windows. Так вы поймете, связана ли проблема с профилем Microsoft.
  • Выйти из своей учетной записи Microsoft, которая подключена в Windows. После этого следует попробовать снова войти в программу связи.
  • Запустить программу в режиме совместимости с Windows 8 или 10 (если у вас Windows 11).
  • Удалить все данные об учетной записи. Для этого откройте «Панель управления» – «Диспетчер учетных данных». Переключитесь на вкладку «Учетные данные Windows» и удалите все связанные аккаунты в программах. Или можно сделать это только с Teams, но другие связанные приложения все равно могут помешать.

Должно сработать что-то из перечисленного выше, но в любом случае вы можете зайти на сайт и воспользоваться их веб-сервисом связи. Особенно полезно, если вы торопитесь и решать ошибку будете позже.

  • Ok, as an update, I’ve managed to get it sorted out on my boss’s computer. I’m not as up on using the acronyms as others, so I’ll explain what I did in layman’s speak.

    It seemed to me the issue was something to do with user accounts, so after working my way through the posts above of how to fix it, and spending more time searching what the abbreviations meant than anything else, I tried searches on «Microsoft Accounts»,
    «Windows 365» and «enrolling devices». It said somewhere about deleting the «Work/School» account by going to settings > accounts > Access work or school, then highlight the account and selecting disconnect and saying yes
    to the warnings. So that the account could be disconnected.

    When I tried to delete the the ‘Work/School’ account from the computer, I was getting an error message that read «This PC isn’t connected to a domain». I then searched on that error message. The internet search told me that you could log onto a
    PC now with either a local account or a microsoft account. And that if you logged on with a local account, you could delete that error message, whereas you couldn’t with a microsoft account. The error message was described as an «unexpected behaviour»
    in the help article I read. So I found out how to set up a local account (settings > accounts > sign-in options) and logging in with that account successfully enabled me to delete the work/school account. I then was able to log out as the local user
    and log back in under the microsoft account, return to settings > accounts > Access work or school and selected «connect» to connect to work’s Azure AD. This needed access to my boss’s phone, so I waited til I could have it alongside me so
    I could easily enter the necessary codes.

    It gave me one further error message/code (0x80180002b) at this point. Something about the enrollment process not working properly. I searched on that, and the search took me here: https://support.microsoft.com/en-us/help/4469913/troubleshooting-windows-device-enrollment-problems-in-microsoft-intune.
    I investigated the MDM user scope first of all (Azure Portal > Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune), and discovered that the MDM User scope was set to none. I changed this to All, and made sure MAM User scope was set
    to None.

    I then returned to settings > accounts > Access work or school hit connect, put in the necessary codes and passwords and it worked! I rebooted the computer and logged in again and it continued to work, no error messages, no nothing, just connections
    to office 365, outlook, onedrive and so forth.

    Vignesh, that worked for me, in any case, hopefully it can work for you as well.

    I also see that the troubleshooting page gives a link to an end user guide to enroll Windows 10 devices. That might assist you as well, Vignesh.

    Is it possible that this was caused by a recent upgrade to one or more aspects of the Microsoft software? Nothing was done at our end to cause the problems to start happening, at least nothing that we know of.

    Once again, thanks and I hope this is helpful to others.

    Russell

    • Marked as answer by

      Monday, August 12, 2019 2:29 AM

  • РЕКОМЕНДУЕМЫЕ: Загрузите этот инструмент, который поможет вам безопасно исправить распространенные ошибки Windows и автоматически оптимизировать производительность системы.

    С использованием Команды Microsoft может позволить вам общаться с другими людьми удаленно. Даже если вы находитесь далеко друг от друга, вы можете видеть друг друга в режиме реального времени с помощью видеоконференцсвязи. Это также полезно для онлайн-классов, встреч, семинаров и многого другого.

    Однако Microsoft Teams также имеет свою долю ошибок, особенно при использовании на ПК с Windows 10. Одним из примеров является ошибка Microsoft Teams. 0xcaa80000. Вы увидите сообщение об ошибке,

    «Мы не можем вас соединить. Похоже, сейчас мы не можем подключиться к одному из наших сервисов. Повторите попытку позже или обратитесь в службу поддержки, если проблема не исчезнет. 0xcaa80000 ”

    Код ошибки 0xcaa80000 также связан и отображается в аналогичной проблеме Outlook. Если в настоящее время вы получаете именно эту ошибку Интернет-сети на ПК, продолжайте читать ниже, чтобы узнать, как устранить и решить проблему с сетевым подключением.

    Исправление-Microsoft-Teams-Internet-Network-Connection-Error-0xcaa80000

    Код ошибки Microsoft Teams 0xcaa80000 — это Настольное приложение Windows 10 проблема и обычно не появляется в Интернете. Это мешает вам войти в свою учетную запись. Чтобы помочь вам устранить проблему, следуйте каждому из приведенных ниже методов.

    Решение №1 — используйте веб-приложение Microsoft Teams.

    Решение №2 — Очистить кеш Microsoft Teams

    Как-очистить-Microsoft-Teams-Cache-на-Windows-10-ПК

    • Закройте приложение Microsoft Teams.
    • На панели поиска на рабочем столе введите % appdata% Microsoft команд.
    • Перейдите в Microsoft Teams.
    • Удалите файлы в следующих папках.
      • % appdata% Microsoft team кеш приложений кеш
      • % appdata% Microsoft team blob_storage
      • % appdata% Microsoft team кеш
      • % appdata% Microsoft team баз данных
      • % appdata% Microsoft team GPUcache
      • % appdata% Microsoft team IndexedDB
      • % appdata% Microsoft team Локальное хранилище
      • % appdata% Microsoft team tmp
    • Перезагрузите компьютер.

    Решение №3 — Изменить настройки Интернета

    • Запустите Панель управления вашего ПК с Windows.
    • Зайдите в Свойства обозревателя.
    • Щелкните вкладку Дополнительно.
    • Найдите Use TLS 1.1 и Use TLS 1.2.
    • Установите оба флажка.
    • Щелкните Применить.
    • Щелкните ОК.
    • Перезагрузите приложение Microsoft Teams.

    Решение №4 — Отключить другие программы

    Запуск программ в фоновом режиме может быть источником кода ошибки Microsoft Teams. Вы можете завершить задачу каждой программы через диспетчер задач и повторить вход в Microsoft Teams.

    Решение № 5 — Установите время автоматически

    • Откройте меню настроек вашего ПК.
    • Перейдите к дате и времени.
    • Обязательно установите время и часовой пояс автоматически.

    После решения проблемы с приложением Microsoft Teams вы можете обновить его, чтобы ошибки не возникали снова. Некоторые из вышеперечисленных решений также могут работать, если вы столкнулись с ошибкой в ​​Outlook 2019 или других версиях приложения.

    Вы пробовали другие решения, которые работали с ошибкой Microsoft Teams? Если вы поделитесь ими с нами, это также поможет другим пользователям. Пожалуйста, запишите их ниже.

    ЕЩЕ ЕСТЬ ВОПРОСЫ? Попробуйте этот инструмент для устранения ошибок Windows и автоматической оптимизации производительности системы.

    Понравилась статья? Поделить с друзьями:
  • Error code 80092004
  • Error code 80090016
  • Error code 8007139f
  • Error code 80070643 wsus установка
  • Error code 80070002 resident evil 5