Sam's IT Knowledgebase

So in my current project I am working on deploying Office 365 in our Organisation. I had an issue in the early stages of testing where some users would get a pop up box (as below) asking for their credentials to activate the product. While this was not a showstopper, we did not want this coming up for every user once we go live with the rollout to over 1300 staff members. There were a few factors which caused this to happen and the fixes below. I was under the impression we were running Active Directory Federation Services. After speaking to one of the System Admins I found out we were actually running Seamless Single Sign On instead. To prevent this from coming up there were a couple of steps which I had to do. For Windows 10 systems it automatically supports AD SSO. For Windows 7 and 8.1 devices I had to install an extra piece of Software called Microsoft Workplace join for non Windows 10 computers here - https://www.microsoft.com/en-us/download/details.aspx?id=53554 On...

I recently had an issue where I am working on an Office 365 rollout and in the early stages of the pilot group I came across a user which was not showing in Azure, and thus missing from the Office Online Portal. I ran the IDfix utility which brought up no issues with the specific user. After engaging with Microsoft it was determined that an attribute in the AD object of this user was different to most other users and the query which Azure runs conflicted with this attribute. In our situation it was the msExchRecipientTypeDetails which was set to 2 for this particular user, and the Azure query we had filtered on only allowing if this was set to 1.