August 12, 2026
New in Numaga: SSO with Microsoft Entra ID
People sign in with the account they already have. That worked with Google Workspace; it now works with Microsoft Entra ID too — with a shorter login flow and a tenant lock that cannot be switched off.
As of today, Numaga also connects to Microsoft Entra ID. People sign in with their own organisation’s Microsoft account, alongside the existing Google Workspace federation. No separate password, no second user administration: your directory is in charge.
Why this was needed
Many organisations run on Microsoft 365; their identity lives in Entra ID. An AI platform that builds its own login world next to that creates exactly what governance doesn’t want: accounts nobody manages, passwords that get reused, and former employees who quietly keep access. So Numaga connects to your directory: an account comes into existence at first sign-in, and whoever is blocked in your IdP doesn’t get in anymore.
Authorisation follows your directory too. Roles and groups from your IdP determine who administers, who audits and which teams can reach which knowledge bases: no second authorisation model. Here’s how that works.
What you’ll notice
The login flow got shorter. Whoever hits the login page is sent straight to their own Microsoft or Google sign-in: no interstitial, no extra click. And new users no longer pick a separate username; the e-mail address from the directory is the identity. For most people the first sign-in is exactly one action: the account screen they already see every day.
Administrators keep a separate emergency entrance, independent of the federation. If your IdP ever goes down, administration can still get in.
Locked to your own tenant
One detail we’re strict about: the Entra connection is always locked to your own tenant. Multi-tenant connections that recognise users by e-mail address carry a well-known takeover pattern (nOAuth): anyone who controls their own Entra tenant can enter any e-mail address there — including your colleague’s — and walk into someone else’s account. So Numaga only accepts accounts from your own directory. That’s not a setting you might forget to enable; without the tenant lock, the platform refuses the connection.
Who this is for
For IT and identity management this means one place where access is managed, and on- and offboarding that follows the directory automatically. For the organisation: fewer passwords, less friction, and AI usage that traces cleanly to people and teams — inside the same governance as the rest of your AI traffic.
SSO is part of every Numaga environment, with Microsoft Entra ID or Google Workspace. Want to see what that looks like for your organisation? Book a demo.