How it works
-
1
A user opens your app
The request reaches SecureGate first, not your app.
-
2
They sign in with Microsoft
SecureGate checks their tenant and, if you've set one, their group.
-
3
Only then do they get through
Allowed users reach your app. Everyone else stops at the gate.
What you get
Microsoft Entra ID sign-in
Users log in with their existing work account. Logins from any other tenant are rejected.
Group-based access
Limit each site to one Entra ID group. Members of nested groups count too.
Access changes apply quickly
Group membership is re-checked every 15 minutes, so removing someone in Entra ID takes effect during their session.
No changes to your apps
SecureGate works as a reverse proxy, so your apps stay behind it, including ones hosted on IIS or shared hosting.
Group details for your apps
Pass the user's group names to your backend in a request header, so your app can tailor what each person sees.
Bot and scanner blocking
Known scanners and AI crawlers are turned away before they reach your app, and access is recorded in an audit log.