TWL-KB-047 · Microsoft 365 · Everyday user

Repeated sign-in prompts across apps

Use your organisation-approved sign-in route only.

Applies to: Microsoft 365 sign-in.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Sign-in required / repeated authentication prompt. Use your organisation-approved sign-in route only.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Sign-in required / repeated authentication promptAn account or policy change may be involved. Repeated MFA requests must never be approved blindly.Use your organisation-approved sign-in route only.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Stop unexpected approvals; Check which apps are affected; Record the message; Contact IT securely
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Stop unexpected approvals

    Do this
    Do not approve an MFA request you did not start.
    What you should see
    No unexpected approval is given.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Check which apps are affected

    Do this
    Note whether one app or several keep asking.
    What you should see
    The scope is known.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Record the message

    Do this
    Note the non-sensitive message and time without capturing codes or tokens.
    What you should see
    You have the details.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Contact IT securely

    Do this
    Use the normal internal support route. Do not clear credentials or remove accounts.
    What you should see
    IT is engaged.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.