SAML SSO
Route the tenant's domain through the native Supabase SAML provider connection.
MICROSOFT ENTRA CONNECTOR
SSO login and directory evidence are separate capabilities. A tenant deliberately enables directory sync and grants the Microsoft Graph application permissions required for the data it wants to use.
Illustrative product workflow. No customer compliance data is shown.
Who this is for
Route the tenant's domain through the native Supabase SAML provider connection.
Sync users, groups, memberships, and supported authentication-method registration summaries.
Populate employee system access and use explicitly granted write actions for group membership where configured.
With additional administrator consent, read license availability and govern assignment changes.
How it works
Authorize the account and identify its environment.
Collect the broad reasonable configuration returned by the supported API calls.
Redact secret-like values and retain source, account, environment, and timestamp.
Use relevant facts in control analysis and require human review of the result.
Frequently asked
No. Credentials are encrypted for connection use, and secret-like fields are removed from evidence snapshots.
Yes. Separate connections can represent different accounts and environments.
Not by default. Any supported write capability is separately enabled, narrowly scoped, confirmed, and audited.
Authoritative sources
We cite primary sources and describe Technolay as an independent implementation platform. Source ownership and official interpretation remain with the named publisher.
We will use your frameworks, infrastructure, evidence sources, and operating model—not a generic sales deck.
Book a demo