Skip to content
Database ⇄ Human resources

Azure Cosmos DB to Ukg Pro integration — real-time, two-way sync

Keep Azure Cosmos DB and Ukg Pro 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 Cosmos DB and Ukg Pro

Put your workforce data where your apps can reach it: Azure Cosmos DB and Ukg Pro share the same people, positions, and org structure in real time.

Ukg Pro is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Azure Cosmos DB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations in Ukg Pro need to exist as queryable Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB with Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations in Ukg Pro field by field, in real time. You decide which system owns which fields — Ukg Pro typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Consolidate documents from multiple containers into a single reporting store.
  • 02 Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
  • 03 Keep Configuration code tables (jobs, locations, departments, cost centers) aligned between UKG Pro and an ERP so org and cost-center hierarchies match.
  • 04 Two-way sync of Employee and Job Details (position, department, supervisor, location, cost center) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR edits in UKG Pro.

Common sync patterns

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations replicate into Azure Cosmos DB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Ukg Pro stay consistent in Azure Cosmos DB, so hierarchy-driven logic and permissions don't drift.

What you can sync between Azure Cosmos DB and Ukg Pro

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 Cosmos DB objects Ukg Pro objects How this pairing syncs
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Employee (Person Details) Core worker record with demographics and identifiers; read by listing employee IDs then fetching each profile, and created on hire via the personnel/onboarding endpoints. Items (JSON documents) is specific to Azure Cosmos DB and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. Partition keys is specific to Azure Cosmos DB and Employment Details to Ukg Pro — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. Change feed entries is specific to Azure Cosmos DB and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. Stored procedures and triggers is specific to Azure Cosmos DB and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. Databases is specific to Azure Cosmos DB and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. Containers is specific to Azure Cosmos DB and Terminations to Ukg Pro — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Ukg Pro

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 Cosmos DB Ukg Pro Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

Ukg Pro Azure Cosmos DB Sub-second propagation

DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.

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

Rate-limit considerations

  • Ukg Pro: An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
What ships with Azure Cosmos DB ⇄ Ukg Pro

Connect Azure Cosmos DB and Ukg Pro for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Ukg Pro connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Cosmos DB or Ukg Pro 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 Cosmos DB or Ukg Pro record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Ukg Pro.

How the Azure Cosmos DB and Ukg Pro connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

Ukg Pro

Integration surface
REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services
Authentication
Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint.
Change detection
No CDC stream. UKG Pro publishes Pro HCM Webhook Events for changes such as new hire, employee and job detail changes, termination, and PTO, which Stacksync subscribes to for near-real-time triggers; bulk and historical loads use paged reads with each service's modified-since filters.
Capabilities
read · write · webhooks
Rate limits
An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
Ukg Pro setup guide
How it works

How to connect Azure Cosmos DB to Ukg Pro — 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 Cosmos DB and Ukg Pro 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 Cosmos DB connected
    Ukg Pro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Cosmos DB and Ukg Pro 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 Cosmos DB ⇄ Ukg Pro
    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 Cosmos DB Ukg Pro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Cosmos DB and Ukg Pro 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 438 integrations available for Azure Cosmos DB and Ukg Pro.

Popular · 7 of 438
All Azure Cosmos DB integrations All Ukg Pro 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