Cyber Security

Secure sign-in with MFA and single sign-on: sign in once, and do it properly

With multi-factor authentication, a stolen password is not enough to break in. With single sign-on, you sign in securely once for all your business apps. We set it up with Microsoft Entra ID.

As a project

The problem

Many break-ins do not start with a complicated attack, but with a stolen password. From a phishing email, a leaked database or because someone uses the same password everywhere. Whoever has the password simply signs in.

With multi-factor authentication (MFA), that password alone is no longer enough: a confirmation on the phone is also needed. With single sign-on, you also sign in to all your business apps with one Microsoft account. We set it up for you with Microsoft Entra ID, as a project, and make sure your team finds it easy to work with.

What will you notice?

Your team mainly notices that signing in becomes easier: one account for everything, and confirming with a tap on the phone. You know that a leaked password is no longer enough to get in.

What it does for you

How Secure sign-in with MFA and single sign-on helps you

  1. 01

    A password alone is not enough

    When signing in, a confirmation is needed in addition to the password, for example in the app on your phone. If an attacker has got hold of your password, they still cannot get in.

  2. 02

    Sign in once for all your apps

    With single sign-on, you also use your Microsoft account for your other business apps. Fewer passwords to remember, and fewer places where a password can leak.

  3. 03

    If someone leaves, everything is closed in one go

    Because all apps are linked to the same account, you block one account when someone leaves instead of dozens of separate logins.

How it works

How we arrange it

Not a technical story, but what happens and who does what.

Plan an introduction
  1. Step 1

    Mapping it out

    We look at how your team signs in now, which apps you use and which apps support single sign-on.

  2. Step 2

    Setting up MFA

    We turn on multi-factor authentication for everyone, with the Microsoft Authenticator app or a passkey. We also arrange what happens when someone gets a new phone.

  3. Step 3

    Sign-in rules

    With Conditional Access, we decide when an extra check is needed, for example when signing in from an unknown device or from abroad. We shut off old ways of signing in without MFA.

  4. Step 4

    Connecting apps

    We connect your business apps to Microsoft Entra ID, so you sign in to them with your Microsoft account. Then we explain to your team how it works.

Frequently asked questions

Questions about Secure sign-in with MFA and single sign-on

Is your question not listed? Feel free to call us, we are happy to think along with you.

What do we need?

Microsoft 365 with Microsoft Entra ID. The sign-in rules (Conditional Access) require Entra ID P1; that is included in Microsoft 365 Business Premium.

Isn't MFA a hassle for my team?

Usually it is not too bad. On a trusted device you do not have to confirm again every time, and with a passkey or the Authenticator app it is one tap. We explain it to your team and help everyone the first time.

Which apps work with single sign-on?

Many business apps support signing in with a Microsoft account, such as accounting, CRM and HR software. We check per app what is possible.

What if someone loses their phone?

Then we block the old phone and set up MFA again on the new device. Until then, nobody can sign in with just the password.

Is this eligible for a subsidy?

Two-factor and multi-factor authentication are on the list of the NCSC's Mijn Cyberweerbare Zaak subsidy scheme.

Shall we meet?

Tell us about your organisation. We listen, think along and show how we can take IT off your hands. No obligation.

Cookie settings

Choose which cookies you allow. You can always change your choice via Cookie settings at the bottom of every page.

Necessary and functional

Needed to make the website work and keep it secure, and to remember choices you make yourself, such as your cookie choice. No consent is required for these.

View 10 cookies
  • nso_toestemming · NSO · cookie · 12 months
    Remembers your cookie choice, so we don't keep asking you.
  • nso-popup-gesloten · NSO · local storage · 3 days
    Remembers that you closed the notice in the bottom corner, so we don't keep showing it.
  • nso-popup-gezien · NSO · session storage · Until you close the tab
    Remembers during a visit that you've already seen the notice in the bottom corner, so it doesn't return on every page.
  • nso-contact-bericht · NSO · session storage · Until you open the contact form or close the tab
    Prepares a message in the contact form when you click Request a proposal, for example your address and the result of the postcode check. Deleted as soon as the form opens.
  • nso-kennisbank-stem · NSO · local storage · Until you delete it
    Remembers which knowledge base articles you've already voted on with Was this article helpful?, or where you closed the question at the bottom of the screen, so we don't ask again. Contains only the articles and your vote.
  • nso-taal · NSO · local storage · Until you delete it
    Remembers which language you chose yourself (Dutch or English), so next time we show you the page in that language straight away and do not ask again whether you want to switch.
  • beweging · NSO · session storage · Until you close the tab
    Remembers during a visit whether animations are on or off.
  • cf_clearance · Cloudflare · cookie · Up to 1 year
    Only if Cloudflare shows a security check: remembers that you've completed it.
  • Turnstile · Cloudflare · cloudflare frame · While filling in a form
    Protects the forms against spam, without puzzles and without tracking. Runs in a frame from challenges.cloudflare.com and does not set any cookies on nso.eu itself.
  • CF_AppSession, CF_Authorization · Cloudflare · cookie · 24 hours
    Only for NSO staff: sign-in for internal pages.

Preview: animaties geforceerd Uitzetten