Salesforce Azure DevOps integration
Integrating Salesforce and Azure DevOps
Connecting Salesforce with Azure DevOps links customer records with engineering work, keeping sales, support, and development teams aligned. Cases raised by customers reach the development backlog without manual re-entry, and progress made by engineers flows back to the teams that own the customer relationship. Follow this guide to set up bidirectional synchronization between your Salesforce org and your Azure DevOps organization.
Salesforce Azure DevOps Licensing Model
The Getint licensing model for Salesforce and Azure DevOps covers different integration needs. Here is an overview:
Standard Licensing
For non-Jira connectors, we offer a simple license tied to a fixed fee depending on the apps you are syncing.
This license covers the integration between 1 instance A (Salesforce) and 1 instance B (Azure DevOps).
No hidden costs. You can sync an unlimited number of work items between these instances.
You can find more information about our pricing structure here: Getint Pricing.
Network License
For managed services companies or organizations integrating three or more instances (whether the tools are the same or different), Getint offers a Network License. This custom license covers a specific number of connections (for example, up to 10 instances) and imposes no restrictions on the tools involved. You can also swap the integrated tools while the license remains active.
For more details on licensing, visit our Licensing Page.
Salesforce API Requirements
Salesforce requires API access for integration. API access is enabled by default in the following editions:
Enterprise Edition
Unlimited Edition
Performance Edition
Developer Edition
API access is NOT enabled by default in:
Group Edition
Essentials Edition
Professional Edition
Requirements to Build Your Integration
Deployment Options: Getint provides two ways to host your integration, a managed SaaS platform or a self-hosted On-premise version. More information about Getint On-premise here.
Authentication: Azure DevOps requires a Personal Access Token, and Salesforce requires OAuth credentials (
client_idandclient_secret). You can find the steps to generate credentials for both connectors here: Connection Guide.Service Accounts: Comments are attributed to the user who created the connection, so we recommend using dedicated Service Accounts on both sides to keep automated updates distinct from individual user activity.
Setting Up Your Salesforce Azure DevOps Integration
1. Access the Getint App
Log in at app.live.getint.io. If you do not have an account, click Sign up to create one.
Enter your details, select the apps you want to connect, and click Create new workspace.
After you create the workspace, go to it to launch Getint.
2. Create an Integration
Go to Workflows (lightning bolt icon) and click Create Integration. From this menu, select Continuous Sync or Data Migration.
3. Generate an Azure DevOps Token
To integrate Azure DevOps (Server or Cloud), you must provide a token with the necessary permissions. Follow the steps below to generate one:
Log in to your Azure DevOps organization.
Open User Settings from the profile menu.
Select Personal Access Tokens from the left sidebar.
Click New Token and enter a name for the token.
Set the expiration and select the appropriate scopes:
Work Items: Read & Write
Project and Team: Read & Write
Graph: Read (required for accurate user data retrieval)
Code: Read (if you are syncing repositories with the Git Connector)
Click Create, then copy and securely store the generated token. This token authenticates and authorizes Getint to access your Azure DevOps organization.
When configuring the Azure DevOps connection details in Getint, provide the generated token as the password.
4. Generate Salesforce Credentials
Salesforce uses OAuth authentication. You grant permissions to Getint through an External Client App, and the resulting credentials are stored in a dedicated Getint database for use by that user only.
Sign in to Salesforce, click the Cog icon in the upper-right corner, and select Setup.
Go to Platform Tools > Apps > External Client Apps, then open the External Client App Manager.
Select New External Client App and enter a unique name, your email address, and the API name.
Enable OAuth:
Scroll down and turn on OAuth.
Enter the Callback URL:
https://login.salesforce.com/services/oauth2/callback.Select the OAuth scope Manage user data via APIs (API).
In the Flow Enablement section, activate Client Credentials Flow, then turn off all other options in the Security section.
Click Create at the bottom of the page. Once the app exists, go back into its settings to continue.
Select Edit, open OAuth Policies, enable Client Credentials Flow, and enter the username shown under Personal Information in your profile. Click Save.
Open the Settings tab, select Consumer Key and Secret, complete the verification screen, and copy the Consumer Key (
client_id) and Consumer Secret (client_secret).
5. Connect to Azure DevOps
In Getint, click Connect App and choose Azure DevOps, then select Create a new connection. Enter the URL for the connection and click Next.
Provide a name for the connection, enter your email, and paste the token generated in the previous steps. Click Add to complete.
Once the connection is established, select the Azure DevOps project you want to synchronize from the dropdown menu and click Connect.
You can only select one project when syncing with Salesforce. Selecting multiple projects will cause Salesforce to disappear from your available integration options.
6. Connect to Salesforce
Click Connect App and choose Salesforce. Enter your Salesforce instance URL in the URL field and click Next.
Assign a name to the connection and enter the client_id and client_secret credentials.
Add the connection and select it.
7. Configure Type Mapping
Quick Build: Automatically map fields and types between applications with this feature.
Manual Mapping: Use this option for full control over the integration. Click + Add Type Mapping to define how your types map between systems. This could include:
Salesforce Case to Azure DevOps Bug.
Salesforce Account to Azure DevOps Task.
8. Field Mapping
Review or manually map fields within mapped types, including subject, description, priority, and assignees.
Define the synchronization flow for each field, using the arrows in the middle and selecting Apply.
Inline images are not supported for the Description field.
9. Assignee Mapping
Use the assignee mapping option to match Salesforce users to Azure DevOps users, which keeps ownership of work items accurate on both sides. For more details, visit our doc: Assignees (users) mapping.
10. Status Mapping
Go to the Status tab and map status fields to align between Salesforce and Azure DevOps. For example, Salesforce New could be mapped to Azure DevOps New, Salesforce Working to Azure DevOps Active, and Salesforce Closed to Azure DevOps Done.
You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
11. How to Manage Comments & Attachments:
The Comments & Attachments tab is enabled by default. You can configure these settings to match your organization's needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
Use the Customize comments creation setting to manage how comments are processed. You can set comments to Public or Private, or choose to skip them entirely.
To synchronize attachments, toggle on the Synchronize attachments setting and choose the sync direction between bidirectional, App A (left), or App B (right).
12. Advanced Tab
Enable Customize create/update actions to manage item synchronization. This allows for specific rules, such as one-way creation for the left application combined with bidirectional updates.
13. Filtering:
It is possible to filter the synchronization to have it customized for your needs and requirements. Please see the doc Items Filtering for more details.
UI Filtering Option:
Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
Select if the filtering applies to All, New, and Synced items.
Note that if the option New items is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option Synced items is selected, only the already synced items will be updated based on that filter.
Choose the options and add the value for the filter. It is possible to filter more than one option for each field.
Select Apply after creating the filters and Save the integration.
14. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to confirm data flows correctly between Salesforce and Azure DevOps.
Verification Steps
Initial Creation:
Create a test case in Salesforce.
Create a test work item in Azure DevOps.
Confirm that the counterparts appear on the opposite side according to your mapping rules.
Field & Feature Validation:
Updates: Modify a mapped field and confirm the change is reflected in the linked item.
Comments & Attachments: Add a comment or upload a file to verify the sync direction and visibility.
Status Transitions: Change the status on one side and verify the linked item updates accordingly.
Audit Logs:
Access the Logs tab within the platform.
Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
Conclusion
Following this guide lets you set up the Salesforce-Azure DevOps integration with Getint. This configuration synchronizes cases, work items, comments, and status changes across your CRM and your development platform, so customer-facing teams and engineering teams work from the same information.
For further assistance, please contact us at the Support Center or Schedule a Demo.
Last updated
Was this helpful?