Guide · Microsoft 365

Microsoft 365 sign-in fails: the twelve causes

From an expired licence to a two-factor lockout to Conditional Access: why sign-ins fail and how to tell the causes apart.

By Dipl.-Ing. Mohamed Khater, Founder and Managing Director since 1992 · · 8 min read

Narrow it down first, then search

“I can’t get in” can have a dozen causes that have nothing to do with each other. Three questions narrow the case down in a minute and save most of the searching.

Does it affect one person or several? Does it affect all of that person’s devices or just one? And does signing in work via the web interface in the browser? These three answers almost always point in the right direction.

  • Several people affected. Then the cause is a setting in the directory, a policy or a Microsoft outage – not the workstation.
  • One person, all devices. Account, password, licence or two-factor authentication.
  • One person, one device. Cached credentials, system time, certificates or a network problem at the workstation.
  • It works in the browser but not in the application. Then the cause lies with the application or the device, not the account.

By frequency

The most common causes

Sorted by how often we actually encounter them.

1. Licence removed or expired

A subscription was not renewed, a licence was removed during a clean-up, or a payment failed. Signing in often still works, but the applications refuse to run.

  • Recognisable by licence messages
  • Can be checked in the admin portal

2. Two-factor: device gone

New phone, reset device, deleted app. Signing in with the password works, the second factor is missing – and nobody gets any further without it.

  • Always set up the second factor twice
  • Reset only by an administrator

3. Account locked

After too many failed attempts, or when Microsoft detects unusual sign-in attempts. Often triggered by an old device that keeps trying in the background with an outdated password.

  • Sign-in log shows the source
  • Often a forgotten second device

4. Conditional Access kicks in

Rules that block sign-ins from abroad, from unknown devices or from outside the company network. This shows up on business trips and on holiday – the rule is intentional, it just has not been communicated.

  • Message usually names the policy
  • Plan exceptions in advance

5. System time or certificate

If the system time is significantly off, encrypted connections fail. Typical after a flat CMOS battery in the computer or on devices that have been switched off for a long time.

  • Check date and time
  • Enable time synchronisation

6. Old credentials on the device

Windows stores credentials. After a password change, it keeps trying with the old one – and may lock the account as a result.

  • Clear Credential Manager
  • Often affects Outlook and OneDrive too

What the sign-in log reveals

The Microsoft 365 admin portal records what happened for every sign-in. It is the most reliable source – and is rarely used.

  • Whether the attempt arrived at all. If nothing is recorded, the device never sent the sign-in – then the cause lies with the network or the application.
  • The error code. It clearly distinguishes between wrong password, locked account, missing licence and a blocking policy.
  • Where from. Location and address show whether it was your own connection – or an attempt from outside that triggered the lockout.
  • Which application. Often only one particular application is blocked while others work.
  • Which policy applied. With Conditional Access, it states explicitly which rule prevented the sign-in.

Frequently asked questions

What we are often asked about this

An employee has a new phone – how does she get back in?

The second factor has to be reset by an administrator and set up again. That is intentional: if you could reset it yourself, it would be worthless.

You can prevent this by having everyone register two methods from the start – for example the app and a phone number. Then one route remains open when a device is changed. Setting this up takes two minutes and saves quite a few calls a year.

Why does the account keep getting locked even though the password is correct?

Almost always, a device in the background keeps trying with an old password – a second phone, a tablet, a printer with scan-to-email, or an old Outlook installation. Every attempt counts towards the lockout.

The sign-in log shows where the attempts are coming from. After that, it is usually sorted in five minutes.

Does it make sense to block sign-ins from abroad?

For many businesses, yes – it significantly reduces the number of automated attacks. The prerequisite is that you take business trips and holiday periods into account and have a way of setting an exception at short notice.

Communication is key. A rule that nobody knows about turns the first business trip into an emergency that is not really one.

We have accounts both on-premises and in the cloud. What do we need to bear in mind?

Directory synchronisation creates two sources of error. First, synchronisation can stall – then password changes do not arrive, and sign-in fails exactly one hour after the change. Second, duplicate accounts arise if someone already had a cloud account before synchronisation.

Both are visible in the admin portal, but only if you know where to look. This belongs in the documentation.

How can we tell whether the problem lies with Microsoft?

The admin portal has a service health overview. If several people are affected at the same time and for no obvious reason, that is the first place to look.

Keep an access route that works independently of your own environment – an admin account whose two-factor authentication is not tied to a company device, stored securely. Otherwise, during an outage, you will be unable to get into exactly the place you need to check.

Dipl.-Ing. Mohamed Khater

Dipl.-Ing. Mohamed Khater founded INFONET Computer GmbH in Cologne in 1992. Sign-in problems are the most common Microsoft 365 support call – and in most cases can be resolved within a few minutes by reading the sign-in log instead of guessing.

Further reading

Free inventory

Who has access, and how is it secured?

We look at accounts, licences, two-factor set-up and policies as a whole – and regularly find licences for people who left the company long ago.

+49 221 984300-0Switchboard and support hotline

[email protected]Reply within 4 hours on working days

Robert-Perthel-Straße 7250739 Köln – Bilderstöckchen

Mon–Fri 9 am–6 pmEmergency support outside these hours by arrangement