Byteet
Book a call
Back to articles

Cybersecurity / Guide

Single Sign-On for SMEs: How It Works and When You Need It

Nov 16, 20269 min read

Every SME ends up with a pile of separate logins: Microsoft 365, a CRM, a bookkeeping package, a supplier portal. Single sign-on replaces that pile with one sign-in, and most Dutch SMEs already own the layer that does it: Microsoft Entra ID, bundled with Microsoft 365. This guide covers what SSO solves, what's already built in, when a dedicated identity provider is worth adding, and how to roll it out in phases.

Single Sign-On for SMEs: How It Works and When You Need It

Every Dutch SME ends up running more applications than anyone planned for: Microsoft 365, a bookkeeping package, a CRM, a project tool, a supplier portal, maybe a time-tracking app one department bought without telling IT. Each one wants its own username and password by default. Single sign-on (SSO) replaces that pile of separate logins with one: sign in once, with your work account, and every application you're assigned to opens without asking again. It isn't an enterprise-only feature — for a small business it's usually the fastest way to cut password-related help desk tickets and the quiet risk of an account nobody remembered to close. This guide covers what SSO actually does, what's already built into Microsoft 365 if you're using it, when a dedicated identity provider is worth adding on top, and how to roll it out without locking your own staff out on day one.

What single sign-on actually solves

With SSO, a user authenticates once and reaches every app assigned to them without a second sign-in. The identity provider — in most Dutch SMEs, that's Microsoft Entra ID, the identity service behind Microsoft 365 — checks who someone is and tells the application to let them in; the application itself no longer stores or checks a separate password for that person.

That one change produces a few practical effects for a small business:

  • Fewer passwords for staff to juggle and reuse. Password reuse across business apps is one of the most common ways a single leaked credential turns into several compromised accounts.
  • One place to cut off access. When someone's laptop is lost, stolen, or they leave the company, disabling their single work account removes their access to everything connected to it, instead of someone working through a list of a dozen separate app logins and inevitably missing one.
  • Fewer password-reset tickets reaching whoever handles IT support. Every app with its own login is another place a password can be forgotten.

The layer you probably already have: Microsoft Entra ID

If your business already runs on Microsoft 365, Azure or Dynamics CRM Online, you already have an identity layer in place: every one of those subscriptions automatically creates a Microsoft Entra tenant, whether or not anyone has configured anything beyond the basics. Microsoft Entra ID is the identity and access management service behind it — it already handles authentication for Microsoft's own apps, and it can do the same for most other business software your company uses.

What that means in practice: the SSO question for most Dutch SMEs isn't "do we need to buy an identity platform?" — it's "how far are we using the one we already have?" A lot of small businesses are sitting on an Entra tenant that only authenticates Outlook and Teams, while a dozen other paid business apps each still run their own separate login.

SAML, OIDC, and what to check before you commit to an app

Entra ID connects to most modern business apps one of two ways. Federation uses an open standard — either SAML, an older but still widely supported standard, or OpenID Connect (OIDC), a newer one built on top of OAuth 2.0 — where Entra ID itself proves someone's identity to the app directly, every time they sign in. Password-based SSO is the fallback for apps that were never built to support federation: Entra ID stores a login credential for that app and fills it in automatically, which gets you a single-click experience without a real identity handshake underneath it.

There's also a third, more limited option worth knowing about so a vendor doesn't oversell it to you: some setups just add a shortcut link into a staff portal, without any shared identity check at all. Microsoft itself is explicit that this isn't actually single sign-on — the app still asks for its own separate login behind that link — and treats it only as a stepping stone while a proper integration is still being built.

The practical takeaway: before signing a contract for a new business app, ask whether it supports SAML or OIDC-based SSO, and at what pricing tier. Some vendors gate real federation-based SSO behind a higher plan than the one you'd otherwise choose, which is worth knowing before you budget the rollout rather than after.

The part SSO quietly fixes: offboarding

The security benefit of SSO that gets talked about least is what happens when someone leaves. Rather than relying on whoever handles HR or IT remembering to manually revoke access across every separate app someone used — and discovering months later that an ex-employee's account in some forgotten tool was never actually closed — identity governance tooling built into Microsoft Entra ID can automatically assign a new starter's accounts, groups and licences on their first day, and automatically remove every one of them the moment their employment record changes.

This matters more than it sounds: a password manager and MFA (covered in our guide to setting up MFA in Microsoft 365) protect an account while someone still has a legitimate reason to use it. SSO combined with identity governance is what actually closes the gap once that reason ends.

When Entra ID alone isn't enough

For most Dutch SMEs under roughly a hundred people, running most of their software through Microsoft 365, Entra ID's built-in identity layer covers the job. A few signals suggest it's time to look at a dedicated identity provider sitting on top of it instead of relying on it alone: a long and growing list of SaaS apps that were never built to trust Entra ID as their identity source, several separate Microsoft tenants after a merger or acquisition that need to be bridged, or a need to manage logins for customers rather than staff — which Microsoft itself handles through a separate product, Entra External ID, built specifically for consumer-facing applications rather than internal staff access.

Dedicated, Microsoft-independent identity providers — Okta is the best-known example — exist for exactly this gap, and some SMEs with a particularly complex software stack do end up running one alongside Entra ID rather than instead of it. For most Dutch SMEs, though, the built-in layer handles the job long before that complexity shows up, and adding a second identity platform on top of Entra ID without a clear reason just creates a second system to maintain.

On licensing: a basic Conditional Access policy and SSO to most apps work with Microsoft 365 Business Premium; richer identity governance and risk-based policies sit in the separate Entra ID P1 and P2 tiers Microsoft prices on top of a standard Microsoft 365 subscription. One detail worth knowing if a future licence review ever trims costs without checking with IT first: if the licence a Conditional Access policy needs lapses, Microsoft doesn't quietly switch the policy off — it stays in place and visible, just no longer editable, until someone restores the licence or deletes the policy outright. Our guide on outsourcing Microsoft 365 management covers what each licence tier actually includes in more detail.

Rolling it out without breaking anything

A phased rollout avoids the two most common ways an SSO project goes wrong: locking staff out of something they need on day one, or discovering six months in that half the company's apps were never actually connected.

  • 1. Inventory what's actually in use. Most SMEs find more apps than IT expected, including ones a single department signed up for directly. You can't connect what you don't know exists.
  • 2. Check each app's SSO support and protocol, not just whether it has a login box. Ask specifically about SAML or OIDC support, since that's the difference between real federation and a glorified bookmark.
  • 3. Start with the highest-value target, not the easiest one — usually whatever system holds the most sensitive data or the widest staff access.
  • 4. Pilot with one team before rolling out company-wide, so a misconfigured policy affects ten people, not everyone, on day one.
  • 5. Decide what happens to the apps that will never get SSO. Some older or niche tools genuinely won't support it; those still need a password manager, which we cover separately in our [guide to choosing a password manager](/articles/password-manager-smb-guide).
  • 6. Write down who approves access to what, once group membership rather than a manual request decides who gets into an app. Without that, SSO just makes it faster to grant access nobody reviewed.

Already running Microsoft 365 but only using Entra ID for Outlook and Teams? Our Cybersecurity & Identity team can map what's connected, what should be, and build the Conditional Access policies to go with it. Pair it with Managed IT & Support once onboarding and offboarding through SSO needs an owner day to day.

FAQ

Is single sign-on the same thing as multifactor authentication? No — they solve different problems. SSO reduces how many separate logins exist; MFA makes each sign-in harder to fake with a stolen password alone. Most SMEs end up running both: SSO for convenience and centralized control, MFA on top of the sign-in itself for security. Our guide to MFA in Microsoft 365 covers that setup directly.

Do we need to pay for Entra ID P1 or P2, or is the free tier enough? That depends on what you're trying to do with it, not just how many staff you have. Basic SSO and Conditional Access are available once you're on Microsoft 365 Business Premium; identity governance features and risk-based policies sit in the paid Entra ID tiers. Work out which specific feature you actually need before buying a tier to get it.

What happens to the handful of apps that don't support SSO at all? They stay outside the single-login setup and need their own password, ideally a long, unique one stored in a password manager rather than memorized or reused. SSO reduces how many of those exceptions exist; it rarely eliminates all of them for a typical SME's software stack.

Is single sign-on a security risk in itself, since one compromised account now opens everything? It's a trade-off, not a free improvement: SSO concentrates risk onto one account instead of spreading it thin across many weak ones. That's exactly why MFA on the single sign-in matters more, not less, once SSO is in place — and why reviewing who has standing access to what shouldn't stop just because logging in got easier.

Do we need a separate identity provider like Okta if we're already on Microsoft 365? Usually not, at least not at first. Entra ID, included with Microsoft 365, already acts as an identity provider for most business apps. A dedicated, separate identity provider becomes worth considering once you're dealing with a large non-Microsoft software stack, multiple Microsoft tenants to bridge, or customer-facing logins rather than staff ones — not as a default starting point.

  • SSO
  • Identity Management
  • Cybersecurity
  • SME

Related Articles