Staff sign-in with Google or Microsoft for your business app
Short answer: If your staff already have Google Workspace or Microsoft 365 accounts, your internal app can let them sign in with those accounts instead of a separate username and password. The app hands the login to Google or Microsoft using OpenID Connect, gets back a verified identity, and only lets in people from your organization. You still need roles inside the app to decide what each person can do, but you gain one less password per person, your existing sign-in security, and one place to switch someone off when they leave.
What "single sign-on" means for a small team
Picture a hypothetical renovation company with a scheduling tool its developer built two years ago. Twelve staff, twelve passwords stored in the app's own database, a reset email every other week, and a nagging worry about the foreman who left in spring. Was his login ever removed?
Single sign-on (SSO) replaces that private password list with the accounts the team already uses for email. When someone opens the scheduling tool, they're sent to Google's or Microsoft's sign-in page, prove who they are there, and come back signed in. The app never sees or stores their password.
How it works, without the jargon
The standard behind "Sign in with Google" and "Sign in with Microsoft" is OpenID Connect, a layer on top of OAuth 2.0. Google's OpenID Connect guide describes the moving parts:
- You set up a project to get credentials (a client ID), register the address users return to (a redirect URI), and set up the consent screen.
- Your app sends the user to Google with a request for basic identity details (scopes such as openid and email).
- After sign-in, your app receives an ID token: a signed package saying who the user is.
- Your app validates the token: the signature, that it was issued by Google, that it was meant for your app, and that it hasn't expired.
Microsoft's Entra ID follows the same standard with its own app registration.
One detail your developer must get right: Google's guide warns not to use the email address as the unique identifier for a user, because emails can change. It says to use the sub field, which stays the same for that Google account. If your app matches people by email alone, a renamed account can turn into a "new" user or, worse, collide with someone else.
Keeping it to your staff only
"Sign in with Google" on its own would let anyone with a Google account through the door. You need to restrict it to your organization, and both providers have settings for that.
Google. In the Google Cloud console, the app's audience setting has a user type. Google's audience help page explains that External apps are available to any user with a Google Account, while projects belonging to a Google Cloud Organization can choose Internal to limit authorization to members of that organization. In the app itself, Google's OIDC guide describes an hd (hosted domain) parameter for your Workspace domain, and says that if you use it, you should verify the returned ID token has an hd claim matching your domain. Treat the server-side check as the real lock; the parameter just smooths the flow.
Microsoft. When registering the app in Entra ID, you choose supported account types. Microsoft's account types page lists "Accounts in this organizational directory only (Single tenant)" alongside multitenant and personal-account options. For an internal tool, single tenant is the one that keeps it to your own staff.
Roles: SSO says who, your app still decides what
SSO answers "is this one of our people?" It doesn't answer "can this person approve invoices?" You still need roles.
There are two common ways:
- Roles stored in the app. The first time a verified staff member signs in, the app creates their profile with a default role, and an admin upgrades them. Simple, and fine for most small teams.
- Roles from the identity provider. Microsoft describes app roles that an administrator assigns to users or groups, which then arrive in the token as a roles claim for the app to check. Microsoft notes that groups and app roles can also be used together. This keeps permissions managed in one admin centre, which helps as the team grows.
Whichever you pick, give new sign-ins the lowest useful role by default. Nobody should become an admin just by having a company email address.
Offboarding: the biggest everyday win
With separate passwords, leaving staff are removed app by app, and something always gets missed. With SSO, suspending the person's Workspace or Microsoft account stops new sign-ins to every app connected this way.
Two caveats to discuss with your developer:
- Existing sessions. If the app keeps people signed in for weeks, a suspended account might still have an open session. Shorter session lengths, or a periodic re-check, close that gap.
- Shared and service accounts. A shared "office@" login defeats the point. Give each person their own account and keep integrations on proper service credentials.
Security you get for free (mostly)
Because sign-in happens at Google or Microsoft, whatever protections you've set up there, such as two-step verification, apply to your app too. That's usually a big step up from a homemade login form. It also moves password resets off your plate.
What doesn't come free: your app still has to validate tokens properly, check the domain or tenant on the server, and protect its own sessions. A sloppy implementation can undo the benefit.
What to check before you switch
- Who isn't on your directory? Contractors, seasonal workers or a bookkeeper without a company account need a plan: guest accounts, a second sign-in method, or a company account.
- Plan features. Some admin features in Google Workspace and Microsoft 365 depend on your subscription. Check the provider's current plan pages for anything you're counting on, rather than assuming.
- Migration. Existing users need to be matched to their new identities (by the stable ID after first sign-in), and the old password login should be switched off once everyone has moved.
- Both providers? If half the team is on Google and half on Microsoft, the app can support both, but agree on one as the source of truth for who works there.
FAQ
Is SSO only for big companies?
No. If your staff already have Google Workspace or Microsoft 365 accounts, an internal app using them is often simpler to run than one with its own passwords.
Can customers use the same login?
That's a different set-up. Customer sign-in usually allows any account (and other options), while a staff tool should be locked to your organization. Keep them separate.
What happens if Google or Microsoft has an outage?
Staff can't sign in to the app until it's resolved, though existing sessions may continue. For most small teams that trade-off is acceptable; for a critical tool, discuss an emergency admin login with your developer.
Do we need a developer to add this?
For a custom app, yes; it touches how users are created, stored and checked. Many off-the-shelf tools offer Google or Microsoft sign-in as a setting.
When your internal tool still runs on its own password list, we can plan the switch to your team's existing accounts with you.