Azure SQL Database
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Database / Security and identity · Two-way sync platform
Azure SQL Database and OneLogin integration
Plan how Azure SQL Database and OneLogin should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Built for teams where self-serve, reliability and scale matter
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
Proposed workflow
Application user or identity reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed application user or identity table in Azure SQL Database or OneLogin Users needs a defined result in the other system.
Start with the proposed application user or identity table in Azure SQL Database and OneLogin Users. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve tenant and group references and establish a protected administrative-account policy.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a renamed login, disabled account, missing group, and a user existing in two tenants.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Azure SQL Database record | OneLogin record | Record matching | Field ownership |
|---|---|---|---|
| Proposed application user or identity tableProposed table; choose its name and schema.Reporting dataset | UsersProposed record; confirm Stacksync object support. | Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. | Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes. |
| Proposed group or membership tableProposed table; choose its name and schema.Reporting dataset | GroupsProposed record; confirm Stacksync object support. | Keep group IDs and membership relationships separately from group names. | The access owner controls membership; reporting a group is different from granting its permissions. |
| Proposed event or activity tableProposed table; choose its name and schema.Reporting dataset | EventsProposed record; confirm Stacksync object support. | Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. | Decide whether the destination stores an immutable history or only a current-state summary. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
OneLogin
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Azure SQL Database | OneLogin |
|---|---|---|
| Integration interface | SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers | OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery |
| Authentication | Confirm the credentials, API plan, and permissions required for Azure SQL Database. | Confirm the credentials, API plan, and permissions required for OneLogin. |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Confirm with Stacksync | Confirm with Stacksync |
| Write access | Confirm with Stacksync | Confirm with Stacksync |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
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.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
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:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Azure SQL Database
- Integration interface
- SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
- Authentication
- Confirm the credentials, API plan, and permissions required for Azure SQL Database.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Azure SQL Database account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Azure SQL Database, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Azure SQL Database and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
OneLogin
- Integration interface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- Confirm the credentials, API plan, and permissions required for OneLogin.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the OneLogin account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for OneLogin, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for OneLogin and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Azure SQL Database and OneLogin access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Azure SQL Database setup checklist
- Identify the Azure SQL Database account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Azure SQL Database, including read/write support, authentication, and initial-load limits.
OneLogin setup checklist
- Identify the OneLogin account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for OneLogin, including read/write support, authentication, and initial-load limits.
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Azure SQL Database and OneLogin planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Proposed application user or identity table in Azure SQL Database (choose its name) / Users
Plan a application user or identity dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- OneLogin
- Object support to establish
- Record identity
- Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
- Field ownership
- Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes.
Fields to include
- Source user ID
- Tenant reference
- Account status
- Group references
- Record dependencies
- Resolve tenant and group references and establish a protected administrative-account policy.
- Validation
- Test a renamed login, disabled account, missing group, and a user existing in two tenants.
- Recovery
- Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
Reporting dataset
Proposed group or membership table in Azure SQL Database (choose its name) / Groups
Plan a group or membership dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- OneLogin
- Object support to establish
- Record identity
- Keep group IDs and membership relationships separately from group names.
- Field ownership
- The access owner controls membership; reporting a group is different from granting its permissions.
Fields to include
- Source group ID
- Member references
- Tenant reference
- Group type
- Record dependencies
- Resolve user and tenant identities before membership changes.
- Validation
- Test removed membership, nested groups, and equal group names in different tenants.
- Recovery
- Recompute the approved membership delta before retrying; do not replay an outdated access grant.
Reporting dataset
Proposed event or activity table in Azure SQL Database (choose its name) / Events
Plan a event or activity dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- OneLogin
- Object support to establish
- Record identity
- Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
- Field ownership
- Decide whether the destination stores an immutable history or only a current-state summary.
Fields to include
- Source event ID
- Event type
- Occurred-at time
- Related record ID
- Payload version
- Record dependencies
- Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
- Validation
- Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
- Recovery
- Identify side effects already completed before replaying an event; use the agreed deduplication key.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Proposed application user or identity table in Azure SQL Database (choose its name) / Users to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Azure SQL Database and OneLogin record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Proposed application user or identity table in Azure SQL Database (choose its name) / Users, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Azure SQL Database and OneLogin need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Azure SQL Database / OneLogin migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Application user or identity reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed application user or identity table in Azure SQL Database (choose its name) or Users record needs a defined result in the other system.
- Start with Azure SQL Database Proposed application user or identity table in Azure SQL Database (choose its name) and OneLogin Users. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve tenant and group references and establish a protected administrative-account policy.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a renamed login, disabled account, missing group, and a user existing in two tenants.
If it fails: Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
Group or membership reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed group or membership table in Azure SQL Database (choose its name) or Groups record needs a defined result in the other system.
- Start with Azure SQL Database Proposed group or membership table in Azure SQL Database (choose its name) and OneLogin Groups. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve user and tenant identities before membership changes.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test removed membership, nested groups, and equal group names in different tenants.
If it fails: Recompute the approved membership delta before retrying; do not replay an outdated access grant.
Event or activity reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed event or activity table in Azure SQL Database (choose its name) or Events record needs a defined result in the other system.
- Start with Azure SQL Database Proposed event or activity table in Azure SQL Database (choose its name) and OneLogin Events. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
If it fails: Identify side effects already completed before replaying an event; use the agreed deduplication key.
Manage approved account changes across OneLogin and Azure SQL Database
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: An approved identity change in OneLogin needs to be reflected in the Azure SQL Database process.
- Identify the tenant and immutable user ID in OneLogin; determine whether a selected destination dataset has a legitimate relationship to that user.
- Separate reporting identity context from actions that create users, grant access, or deactivate accounts. Document the approval and effective date before any action.
- Keep identity attributes separate from customer contacts and exclude attributes unnecessary for the process.
Expected result: A rename preserves identity; an unapproved access change is withheld; a future-dated change waits until its approved time.
If it fails: Review current permissions and approval before retrying. A stale event must not restore access that has since been removed.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Proposed application user or identity table in Azure SQL Database (choose its name) / Users
Test case
Test a renamed login, disabled account, missing group, and a user existing in two tenants.
Expected result
The expected application user or identity relationship is preserved with no duplicate action or unintended write.
Proposed group or membership table in Azure SQL Database (choose its name) / Groups
Test case
Test removed membership, nested groups, and equal group names in different tenants.
Expected result
The expected group or membership relationship is preserved with no duplicate action or unintended write.
Proposed event or activity table in Azure SQL Database (choose its name) / Events
Test case
Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
Expected result
The expected event or activity relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated application user or identity change
Investigate
Inspect Azure SQL Database Proposed application user or identity table in Azure SQL Database (choose its name) and OneLogin Users, their IDs, and the destination error.
Next action
Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
Rejected or repeated group or membership change
Investigate
Inspect Azure SQL Database Proposed group or membership table in Azure SQL Database (choose its name) and OneLogin Groups, their IDs, and the destination error.
Next action
Recompute the approved membership delta before retrying; do not replay an outdated access grant.
Rejected or repeated event or activity change
Investigate
Inspect Azure SQL Database Proposed event or activity table in Azure SQL Database (choose its name) and OneLogin Events, their IDs, and the destination error.
Next action
Identify side effects already completed before replaying an event; use the agreed deduplication key.
A record type or update is unavailable
Investigate
Check the Azure SQL Database and OneLogin connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Azure SQL Database and OneLogin
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Azure SQL Database OneLogin Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in OneLogin.
OneLogin Azure SQL Database Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Azure SQL Database.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Azure SQL Database and OneLogin integration FAQ
-
Explore a Azure SQL Database and OneLogin integration with a Stacksync engineer. Stacksync support for Azure SQL Database and OneLogin is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Azure SQL Database account, edition, environment, and business objects the integration must access. Identify the OneLogin account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Proposed application user or identity table in Azure SQL Database (choose its name) in Azure SQL Database and Users in OneLogin. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Proposed application user or identity table in Azure SQL Database (choose its name) / Users to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 441 integrations listed for Azure SQL Database and OneLogin.
Next step
Plan your integration with an engineer
Walk through your Azure SQL Database and OneLogin records, field mappings, and requirements with an integration engineer.
