HomeSample Page

Sample Page Title


Microsoft 365

Microsoft shared a workaround for a recognized Microsoft 365 subject triggering ‘One thing Went Mistaken [1001]’ sign-in errors and making desktop functions unusable for a lot of clients.

The login points have an effect on these utilizing Excel, Phrase, Outlook, and PowerPoint for Microsoft 365, Microsoft 365 Apps for enterprise, and Workplace apps for iOS and Android.

“When customers try to signal into Microsoft 365 desktop functions, they obtain an error message,” the corporate says.

“We’re experiencing an issue with SSO with Workplace 365 apps (outlook, onedrive). After signing in to the AVD, the workplace apps should not signed in, they continue to be caught,” one affected person stated.

“It’s an Azure AD joined home windows 11 AVD host. The authentication pop-up say one thing when mistaken [1001].”

Whereas these errors could also be encountered when attempting to check in to Microsoft 365 desktop functions on methods when safety software program blocks Net Account Supervisor (WAM) plug-ins from working, Redmond can also be investigating these login issues as a separate subject by reviewing logs from impacted customers.

Microsoft additionally requested affected clients to open help tickets within the M365 Admin Portal and fix Microsoft Workplace Authentication/Id Diagnostic (MSOAID) logs to hurry up the investigation.

'Something went wrong' error
‘One thing went mistaken’ error (mgb0129)​​​

​Microsoft advises customers experiencing points opening Microsoft 365 apps to make use of the Outlook Net App (OWA) and Workplace internet functions or cell functions as a workaround.

Redmond says that the next steps may also assist to eliminate the sign-in errors:

  • Rebooting the machine usually helps to mitigate the difficulty.
  • Run the commandlets beneath in person mode PowerShell to restore WAM (extra context within the Repair authentication points in Workplace functions if you strive to hook up with a Microsoft 365 service article):

    
    Add-AppxPackage -Register "$env:windirSystemAppsMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewyAppxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
    Add-AppxPackage -Register "$env:windirSystemAppsMicrosoft.Home windows.CloudExperienceHost_cw5n1h2txyewyAppxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

Extra steerage is accessible on Microsoft’s help web site on methods to repair Workplace app authentication points when connecting to a Microsoft 365 service and on what to do if you cannot check in to Microsoft 365 desktop apps.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles