Azure DevOps and Salesforce, always in sync
Connect customer support to engineering delivery. ZigiOps syncs Salesforce cases with Azure DevOps work items in real time — state, priority, comments and attachments flow both ways, no scripts required.
Azure DevOps 
Salesforce A customer reports an issue as a Salesforce case while engineering tracks the fix as an Azure DevOps work item. Case status and engineering progress live in separate tools, so account teams chase updates manually.
ZigiOps links each Salesforce case to its Azure DevOps work item and keeps them synchronized in real time. State, priority, comments and attachments propagate both ways automatically.
How the Azure DevOps ↔ Salesforce mapping works inside ZigiOps
A look at the visual field-mapping canvas ZigiOps engineers use to configure this pair — point, click, connect. No scripts, no pipelines.
Azure DevOps 
Salesforce Every field that matters, mapped both ways
Map Azure DevOps entities to Salesforce entities down to the individual field, without writing a script.
More control over how Azure DevOps ↔ Salesforce syncs
Updates flow the moment they happen — no polling delays, no scheduled batch jobs.
Scope every sync with filters on priority, record type, area path or any custom field.
Built-in logic decides which update wins and logs every decision for full traceability.
Sync resumes on its own after downtime or network interruptions — nothing to restart by hand.
Validate field mappings and rules against real data before the integration goes live.
See sync status and catch failures early, without digging through logs.
When a sync fails, ZigiOps surfaces the likely cause and a suggested fix — no log-diving required.
From customer case to shipped fix
Support owns the case; engineering owns the work item. ZigiOps keeps them a single, synchronized thread from report to release.
The account team logs a case with priority and account context.
A mapped Azure DevOps work item is created and linked to the case.
State, comments and attachments sync back to the case as the fix progresses.
Completing the work item resolves the case, with the full delivery history attached.
Azure DevOps ↔ Salesforce FAQ
Is the Azure DevOps–Salesforce sync bidirectional?
Yes. Cases and work items stay aligned in both directions in real time, with conflict-resolution logic keeping both systems authoritative so neither overwrites the other.
What fields map between the two?
Case ↔ work item, status ↔ state, priority, and comments and attachments — all in both directions with full fidelity, fully configurable in the visual editor.
Do I need Apex or Azure DevOps extensions?
No. The entire integration is configured no-code in ZigiOps — no Apex triggers and no Azure DevOps extensions or pipelines to build or maintain.
Can I connect multiple Azure DevOps or Salesforce instances?
Yes. ZigiOps supports unlimited connections between instances, so one Salesforce org can sync with several Azure DevOps organizations — or the reverse — each with its own field mapping and rules.
What happens if a case and work item are updated at the same time?
Built-in conflict-resolution logic decides which update takes precedence and logs the decision, so both systems stay authoritative and every change is auditable.
Can I limit the sync to specific cases or work items?
Yes. Conditional triggers let you scope the sync by priority, record type, area path or any other field, so only the records that matter cross over.
See Azure DevOps ↔ Salesforce sync live
Book a demo and we'll connect your Azure DevOps and Salesforce instances in real time.