Skip to content
Database ⇄ Security and identity

Azure SQL Database to Onelogin integration — real-time, two-way sync

Keep Azure SQL Database and Onelogin in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure SQL Database and Onelogin

Close the gap between your application data and your directory: Azure SQL Database and Onelogin share users, groups, and access in real time, in both directions.

Onelogin is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. Azure SQL Database holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.

Stacksync syncs Rows and columns, Stored procedures, Change tracking / CDC tables, Tables in Azure SQL Database with Apps (app instances), Groups, Mappings (mapping rules), Events in Onelogin field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.

Common use cases

  • 01 Expose SaaS data (billing, support tickets) as tables in Azure SQL for reporting teams already on Microsoft tooling.
  • 02 Replicate Azure SQL tables to a warehouse without building custom CDC pipelines.
  • 03 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
  • 04 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.

Common sync patterns

Deprovision the moment the record changes

When someone is marked inactive or removed in Azure SQL Database, the matching account in Onelogin is disabled within seconds, closing the window between a departure and a login that still works.

Read users and groups as ordinary tables

Users, groups, and their memberships from Onelogin land in Azure SQL Database as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.

Keep group and role membership aligned

A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.

What you can sync between Azure SQL Database and Onelogin

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure SQL Database objects Onelogin objects How this pairing syncs
Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Stored procedures is specific to Azure SQL Database and Roles to Onelogin — each maps to any object or custom field on the other side.
Change tracking / CDC tables System-maintained change records used to drive incremental sync. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Change tracking / CDC tables is specific to Azure SQL Database and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map one-to-one to records in the paired system. Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. Tables is specific to Azure SQL Database and Groups to Onelogin — each maps to any object or custom field on the other side.
Views Read-only projections used when the sync should expose a curated shape rather than raw tables. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Views is specific to Azure SQL Database and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
Schemas Namespaces that organize tables and control which objects a sync user can reach. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Schemas is specific to Azure SQL Database and Events to Onelogin — each maps to any object or custom field on the other side.
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Rows and columns is specific to Azure SQL Database and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between Azure SQL Database and Onelogin

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure SQL Database Onelogin Sub-second propagation

DetectionChanges in Azure SQL Database are captured at the source via change data capture — no polling loop against its API. Change data capture or change tracking, both supported on Azure SQL Database.

DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.

Onelogin Azure SQL Database Sub-second propagation

DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.

DeliveryEach detected change is applied to Azure SQL Database as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Azure SQL Database ⇄ Onelogin

Connect Azure SQL Database and Onelogin for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure SQL Database–Onelogin connection.

Real-time

Two-way sync

Changes in Azure SQL Database or Onelogin instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure SQL Database or Onelogin data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure SQL Database or Onelogin record.

Observability

Monitoring

Track your Azure SQL Database ⇄ Onelogin sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Onelogin.

How the Azure SQL Database and Onelogin connectors work

Azure SQL Database

Integration surface
SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
Authentication
SQL authentication (database credentials) or Microsoft Entra ID authentication
Change detection
Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback
Capabilities
read · write · CDC

Onelogin

Integration surface
OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
Authentication
OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
Change detection
Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
Capabilities
read · write · webhooks
Rate limits
Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works

How to connect Azure SQL Database to Onelogin — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure SQL Database and Onelogin with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure SQL Database connected
    Onelogin connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure SQL Database and Onelogin objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure SQL Database ⇄ Onelogin
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure SQL Database Onelogin
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure SQL Database and Onelogin integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 441 integrations available for Azure SQL Database and Onelogin.

Popular · 8 of 441
All Azure SQL Database integrations All Onelogin integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own