Two-way sync
Changes in Azure Synapse Analytics or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Onelogin is the record of who exists and what they can reach; Azure Synapse Analytics is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Onelogin governs are what security, compliance, and analytics teams want to query in Azure Synapse Analytics. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.
Stacksync syncs Groups, Mappings (mapping rules), Events, Authentication factors (MFA) from Onelogin into tables in Azure Synapse Analytics in real time, and the connection works in both directions: values computed in Azure Synapse Analytics, such as risk scores or access-review decisions, can be written back to attributes in Onelogin where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.
A continuously synced copy in Azure Synapse Analytics gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.
Risk scores, anomaly flags, or access-review outcomes computed in Azure Synapse Analytics write back to attributes on the matching user in Onelogin, where the identity team can act on them.
Users, groups, and roles from Onelogin arrive in Azure Synapse Analytics as queryable tables, current within seconds instead of a nightly directory export.
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 Synapse Analytics objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Materialized views is specific to Azure Synapse Analytics and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | SQL pools is specific to Azure Synapse Analytics and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Users to Onelogin — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | External tables is specific to Azure Synapse Analytics and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Views is specific to Azure Synapse Analytics and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | 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. | Schemas is specific to Azure Synapse Analytics and Groups to Onelogin — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
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 Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Onelogin connection.
Changes in Azure Synapse Analytics or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Onelogin data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Onelogin record.
Track your Azure Synapse Analytics ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Onelogin.
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.
Authenticate Azure Synapse Analytics 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.
Pick the Azure Synapse Analytics 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Synapse Analytics and Onelogin: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Materialized views and SQL pools), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Azure Synapse Analytics and Onelogin: Queryable history for audit and compliance; Risk and review results back on the account; Directory data in the warehouse, minus the pipeline. A continuously synced copy in Azure Synapse Analytics gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.
Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. Onelogin: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Azure Synapse Analytics: The serverless SQL pool queries files in the data lake directly, so some 'tables' a sync sees are projections over Parquet or CSV rather than managed storage. Onelogin: The Event Webhook (Event Broadcaster) delivers batches of events to a registered URL for near-real-time triggers, while the Events API filters by since/until for historical pulls; there is no database-level CDC. Stacksync's field mapping accounts for these differences between Azure Synapse Analytics and Onelogin without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Synapse Analytics and Onelogin records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 539 integrations available for Azure Synapse Analytics and Onelogin.