Real-time
Two-way sync
Changes in Azure Active Directory or Pigment instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Azure Active Directory to Pigment integration — real-time, two-way sync
Keep Azure Active Directory and Pigment 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 Active Directory and Pigment
Keep the people who can act on financial records in Pigment matched to their identities in Azure Active Directory, so access is provisioned, updated, and revoked in real time.
Pigment runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Azure Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.
Stacksync keeps Dimension lists, Tables, Scenarios, Data imports in Pigment aligned with Group memberships, Applications, Service principals, Directory roles in Azure Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.
For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.
Common use cases
- 01 Sync headcount and compensation data from an HRIS into workforce planning models.
- 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 03 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
- 04 Mirror Applications and Service principals into a database or CMDB to track app ownership and credential expiry.
Common sync patterns
Where Azure Active Directory is the identity source: offboarding reaches the books
When a person is deactivated in Azure Active Directory, their matching user in Pigment is disabled in the same motion, so departed employees keep no standing access to financial records.
One user roster across both systems
People, their status, and their contact details stay matched between Pigment and Azure Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
Group and role membership drives finance permissions
A person's group or role in Azure Active Directory maps to their permission set in Pigment, so who can approve, post, or view is governed from one place instead of maintained twice.
What you can sync between Azure Active Directory and Pigment
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 Active Directory objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Applications Planning models organized by domain such as finance, sales, or workforce | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Groups is specific to Azure Active Directory and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Group memberships is specific to Azure Active Directory and Dimension lists to Pigment — each maps to any object or custom field on the other side. | |
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Tables Row-based transactional data loaded into models from source systems | Service principals is specific to Azure Active Directory and Tables to Pigment — each maps to any object or custom field on the other side. | |
| Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Directory roles is specific to Azure Active Directory and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Devices is specific to Azure Active Directory and Data imports to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Pigment
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 Active Directory Pigment Sub-second propagation
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Azure Active Directory Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
- Pigment: Subject to the platform's API rate limits.
What ships with Azure Active Directory ⇄ Pigment
Connect Azure Active Directory and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Pigment 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 Active Directory or Pigment record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Active Directory and Pigment.
How the Azure Active Directory and Pigment connectors work
Azure Active Directory
- Integration surface
- Microsoft Graph REST API (v1.0)
- Authentication
- OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
- Change detection
- Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
- Capabilities
- read · write · webhooks
- Rate limits
- Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Azure Active Directory to Pigment — 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.
- 01
Connect your apps
Authenticate Azure Active Directory and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Azure Active Directory
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Pigment 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.
objects · Azure Active Directory ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Azure Active Directory PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Pigment: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Applications and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Active Directory and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Azure Active Directory: Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Pigment side: Dimension lists, Tables, Scenarios, Data imports, plus custom fields where Pigment exposes them. On the Azure Active Directory side: Group memberships, Applications, Service principals, Directory roles. Stacksync auto-detects both schemas and converts types between the two systems.
-
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.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 409 integrations available for Azure Active Directory and Pigment.
Popular · 8 of 409
-
Azure Active Directory ⇄ Zuora -
Azure Active Directory ⇄ Adyen -
Azure Active Directory ⇄ Logisense -
Azure Active Directory ⇄ Bill -
Pigment ⇄ Onelogin -
Pigment ⇄ Auth0 -
Pigment ⇄ Jumpcloud - Pigment ⇄ Active Directory
No integrations match .
