Troubleshooting Office 365

I would to share some advance Office 365 troubleshooting techniques I used to investigate problems with sign-in, activation, authentication, installation and update.

Troubleshooting Authentication/Sign-in/Activation Errors

To investigate about random user problem, usually sign-in prompt, you should enable Office 365 logging and compare a “working attempt” vs a “non working attempt” to compare the results.

Launch cmd as administrator and run the following command:

reg add HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Debug /v TCOTrace /t REG_DWORD /d 1 /f

Once the error occurs collect the following logs:

Collect logs from %temp%
Office.log
<appname>.exe.log (where <appname> is the name of the application used for the Sign-In attempt, for example, Excel.exe.log or Winword.exe.log)

Remove the regkey added. To do this, launch cmd as administrator and run the following command:

reg delete HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Debug /v TCOTrace /f

Note: if you are, as in my case, in a RDS environment, you should create a GPO to deploy/remove this registry key and cooperate with the users to collect logs when error popup

Enable O365 Logs GPO Read More

AD FS & Office 365 Multi Domain Federation

Often happen that a customer has more then one email domain in his On-Premises infrastructure. This should be considered when you plan to deploy AD FS Services to enable Single Sign-On with Office 365.
With the newest version of Azure AD Connect, steps to federate On Premises AD DS with Azure AD is fully automated though it assumes that the domain specified during the wizard steps is the only one domain you want to federate (If you need an overview of Azure AD Connect step-by-step configuration, please refer to Microsoft Docs here).

This will cause disruption of users login to Office 365 apps. To solve this situation you need to change the federation mode configured by the wizard manually using Powershell and set it to a Multi Domain federation. Read More