Tag: Office 365

Sharepoint Online login failure. Issue Type: User not in directory

Sharepoint Online login failure

Weird glitch with Office 365 when a user who had returned from a two week long holiday tried to access a document in Sharepoint Online. The error message shows that the user is not in directory, which is incorrect. He couldn’t login to Microsoft Office 365 at all, however Outlook still worked and he could send and receive email.

Resetting his password fixed the problem.

But what was the underlying cause could not be discerned. It wasn’t that he was logged in using his MSDN Microsoft account which has the same email address and therefore the same username as his Office 365 organizational account. A Private Browser session was tried and that failed. Also attempting to login from a completely different Pc failed in the same way.

My best guess is that the Azure Active Directory object associated with his account had been locked due to an expired password or the object had become corrupted in some way. Resetting the password then updated the object’s attributes which allowed the account to become active again.



Introducing the new Office 365 Admin Center Preview

The Office 365 Admin Center is being updated with the new visual style that Microsoft has adopted for the Microsoft Azure admin center.

We haven’t received the update yet on our subscription, but I like the look of it and so long as it is as easy for me to administer our company’s subscription I’ll be happy.



Resolving Microsoft Office 2010 issues with Office 365

We have a mixture of licenses for Microsoft Office 2010 and 2013 here and there is the occasional need to reinstall Microsoft Office such as when rebuilding a PC or migrating a user to a new computer.

Problem
New installs of Microsoft Office 2010 will have issues when trying to work with Office 365 i.e. Exchange and SharePoint online.

The issue will be most apparent when trying to connect Outlook with the Exchange mail server as it will continue to request login details on an infinite loop which is difficult to cancel without killing off the Outlook process in Task Manager.

Solution
Microsoft Office 2010 needs to be updated to the most recent version by installing Service Pack 2 (and possibly subsequent Windows Updates that relate to Office 2010).

You can determine what exact version of Office you have by doing the following. On the File tab, click Help. You will see the version information in the About Microsoft section.

office 2010 version number

• The version number of Office 2010 SP2 is greater than or equal to 14.0.7015.1000.
• The version number of Office 2010 SP1 is greater than or equal to 14.0.6029.1000 but less than 14.0.7015.1000.
• The version number of the original RTM release of Office 2010 (that is, with no service pack) is greater than or equal to 14.0.4763.1000 but less than 14.0.6029.1000.



How to whitelist a domain in Office 365 Exchange online

We receive automated emails from a domain other than the one we use for staff and some of these emails were getting misidentified as spam and moved to people’s Junk Email folders in Outlook. So we needed to white list the domain so that any emails originating from there would bypass the spam filter.

  1. In the Exchange admin center click on Mail Flow.
    exchange_mail_flow
  2. Next create a new rule by clicking on the + icon and click Bypass spam filtering…
    new_rule
  3. Select on the *Apply this rule if… for The sender… domain is
  4. Add the domain you wish to whitelist plus any additional domains you also wish to whitelist.
  5. Select Stop Processing more rules and then click save.

Learn more about Office 365 and Exchange Online with my TechSnips screencasts.

Or read the definitive guide to Microsoft Office 365 Administration


Ready to stop reading and start learning about PowerShell, DSC, Windows Server, Sharepoint, IIS and dozens of other categories? If so, check out the hundreds of free technical demo screencasts available on the new, IT career development platform TechSnips.




Office 365 is turning Hungarian

Really bizarre error has turned up in the Term Store for my company’s instance of Sharepoint Online.

Listed under Department we now have the following Hungarian terms and their English equivalents as translated by Bing Translator

Alföldi Retail Régió – Great Plains Region Retail
Dunántúli Retail Régió – The Population Of The Retail Region
Hitelezési Kockázati Metodológiák szakterület – Credit Risk Methodologies practice areas
Nagyvállalati Finanszírozás törzs – Enterprise Financing body
Okmányos Műveletek szakterület – Documentary Operations Specialist
Wholesale vezérigazgató-helyettes törzs – Deputy General Manager of Wholesale trunk

I think Bing has mistranslated Dunántúli though, I think it should read Transdanubian. Regardless I have no idea how they got into our Sharepoint.

Hungarian_term_store



Office 365: So it begins

So setting up and configuring Office 365 is my next major project at my new company following the installation and configuration of a WSUS server.

We’ve signed up for the E1 Enterprise Plan which will gives us Sharepoint and Exchange Online. This project has been a long time in the planning and pre-dates my employment by several months and I will be liaising with one of my colleagues Jeff who has been working on the project since the start. The underlying purpose of the project is document management but there is I believe great benefits to moving our archaic email system to Exchange and having it based in the cloud gives us resiliency for Disaster Recovery (which is another of my major projects here). Jeff’s expertise is in document management so he will be overseeing the Sharepoint side of things and I will be configuring Exchange and administering my company’s entire use of Office 365.

The first part of the project was ensuring that all staff had a sufficiently up to date version of Microsoft Office on their laptop or desktop PC so I upgraded everyone that had Office 2007 or didn’t have any version of Microsoft Office to Microsoft Office 2013.

Second part of the project was creating the user accounts which was straightforward as I was able to output user account details from our Active Directory as a CSV file and then with a bit of editing to remove service accounts and format the CSV according to the guidance supplied by Microsoft I was then able to upload the edited CSV file and automate the creation of the accounts for everyone in the company.

Thirdly was adding domains and then configuring the Office 365 services to use the added domain names. This was where I hit problems. It is simple to add a domain but in order to prove ownership and configure to use the Office 365 services then certain DNS fields needed to be created and our ISP didn’t allow creation or editing of any fields other than the basic A, MX and CNAME.

Finally ideally we’d wish to use Single Sign-On through Active Directory Federation Services, but having now delved into the pre-requisites and resources required for this functionality I have decided that DirSync will provide a level of integration with Active Directory that would suit our needs.