ADL Connect - Salesforce - Azure DevOps Integration

ADL Connect is a powerful, bidirectional integration tool that connects Salesforce with Azure DevOps, enabling a unified workflow across Sales, Support, and Engineering teams. Available on the Salesforce AppExchange, the connector allows users to synchronize Azure DevOps work items, comments, attachments, and status updates directly within Salesforce. By consolidating cross-system activities, ADL Connect eliminates manual updates, reduces context switching between applications, and improves overall response times.

Its intuitive configuration interface and secure authentication model ensure accurate, reliable data synchronization across both platforms.

Purpose

The primary objective of ADL Connect is to provide a frictionless bridge between Salesforce users and Azure DevOps users, ensuring customer issues, development tasks, and product enhancements move efficiently through their lifecycle.

This integration is especially valuable for the following roles:

• Salesforce Administrators
• Configure and manage a secure, flexible integration that supports internal teams.
• Developers
• Gain consistent visibility into Azure DevOps work items directly linked to Salesforce records.
• Project Managers & Product Owners
• Reduce duplicate work and improve communication between business and engineering teams.
• Support & Operations Teams
• Create, view, and track Azure DevOps issues directly from Salesforce without switching tools.

By establishing a single source of truth, ADL Connect improves collaboration and accelerates issue resolution across customer-facing and engineering teams.

1. Core Features of ADL Connect

An overview of the key capabilities, including:

• Create and update Azure DevOps work items directly from Salesforce
• Bidirectional synchronization of fields, comments, and attachments
• Search for and link existing Azure DevOps items to Salesforce records
• Secure authentication using API tokens
• Configurable field and object mapping between Salesforce and Azure DevOps projects

These features ensure seamless workflows and data consistency across systems.

2. Installation and Initial Setup

A high-level walkthrough of the setup process, including:

• Installing ADL Connect from the Salesforce AppExchange
• Authenticating Salesforce and Azure DevOps using secure API tokens
• Configuring initial project mappings and data models

This setup establishes the foundation required to activate and use the integration successfully.

3. How Salesforce and Azure DevOps Data Sync Works

An explanation of the bidirectional synchronization model, covering:

• Outbound sync: Salesforce updates pushed to Azure DevOps
• Inbound sync: Azure DevOps updates reflected back in Salesforce
• Field mapping, record ID mapping, and synchronization rules
• Handling of comments and attachments across both platforms

This section helps users understand how data behaves once the connector is configured.

4. Key Benefits for Operational Teams

Organizations using ADL Connect gain several practical advantages:

• Reduced manual data entry and administrative overhead
• Improved visibility into engineering progress for customer-facing teams
• Faster issue resolution through centralized communication
• Stronger collaboration between Sales, Support, and Development
• Increased data consistency, traceability, and auditability

Together, these benefits drive better cross-functional alignment and improved service delivery.

Installation and Connection Setup

To begin using ADL Connect, the first step is to install the package from the Salesforce AppExchange and complete the initial connection configuration. This setup establishes a secure communication channel between Salesforce and Jira, enabling all subsequent synchronization activities.

1. Install the ADL Connect Package

Navigate to the Salesforce AppExchange and locate the ADL Connect listing. Select Get It Now to initiate the installation process.

During installation:

• Choose the target environment (Production or Sandbox)
• Review and approve the required permissions
• Install the package for Administrators only or All Users, based on organizational requirements

Once the installation is complete, ADL Connect becomes available in the Salesforce App Launcher and is ready for configuration.

2. Launch the Configuration Console

After installation, open the ADL Connect Setup Console from the App Launcher.

This console serves as the central workspace for:

• Providing authentication details
• Configuring Jira project mappings
• Defining field mapping rules
• Managing inbound and outbound synchronization settings

The configuration console is designed to simplify both the initial setup and the ongoing administration of the integration.

How to Generate an API Token from Your Microsoft Account

To establish a secure connection between Salesforce and Azure DevOps, a Personal Access Token (API token) must be generated from your Microsoft account. This token replaces password-based authentication and provides a secure method for external applications such as ADL Connect to access Azure DevOps data.

Follow the steps below to generate and configure a new API token.

Step 1: Sign in to Your Microsoft Account

1. Open a web browser and navigate to:
2. https://azure.microsoft.com/
3. Sign in using your Microsoft (Azure DevOps) email address and password.
4. Complete multi-factor authentication if it is enabled for your account.

Step 2: Access Personal Access Token Settings

1. After signing in, click User Settings located at the top-right corner near your profile avatar.
2. From the dropdown menu, select Personal Access Tokens.

This section allows you to create, manage, and revoke API tokens used by external integrations.

Step 3: Create a New API Token

Click Create API Token. In the token creation dialog:

• Enter a descriptive name for the token
• Set the access scope to full access (recommended for ADL Connect)
• Set the expiration date (recommended: one year)
• Click Create to generate the token.

Setting a Custom Scope (Alternative)

If your organization's security policies restrict the use of "full access" tokens, you can restrict the token's permissions by selecting Custom defined under the access scope settings.

To configure this, click Show all scopes at the bottom of the list and check the following permissions:

• Identity: Read
• Member Entitlement Management: Read
• Project and Team: Read & write
• Work Items: Read, write, & manage

Step 4: Copy and Store the Token Securely

1. Once the token is generated, click Copy to Clipboard.
2. Store the token temporarily in a secure location. (For security reasons, Microsoft will not display the token again after the dialog is closed)
3. Keep the token available for the Salesforce configuration step.

Step 5: Connect Salesforce to Azure DevOps Using the API Token

Before synchronization can begin, a secure connection must be configured in ADL Connect.

To complete the connection:

1. Open the ADL Connect authentication settings in Salesforce.
2. Enter your Azure DevOps email address or username.
3. Paste the generated API token into the API token field.
4. Save the credentials.

Once saved, ADL Connect can securely access Azure DevOps based on the permissions granted to the token.

Security Best Practices

• API tokens act as credentials and must be handled with care.
• Do not share tokens publicly or store them in unsecured locations.
• If a token is compromised, revoke it immediately from the Personal Access Tokens page.
• Always use the token together with your Microsoft email address when configuring ADL Connect.

Project Mapping Between Salesforce and Azure DevOps

Project mapping establishes the relationship between Salesforce and Azure DevOps by defining which Salesforce object corresponds to a specific Azure DevOps project and work item type.

As part of this configuration, a custom Azure DevOps field is required to store the Salesforce Record ID, enabling reliable cross-system linkage and bidirectional synchronization.

Follow the steps below to configure a project mapping.

Step 1: Create a New Project Mapping

1. In ADL Connect, navigate to the Field Mappings section.
2. Click New Project Mapping or New Mapping.
3. Select the appropriate Integration App from the dropdown.

This identifies the Azure DevOps environment to which the mapping belongs.

Step 2: Select the Azure DevOps Project

1. In the Azure DevOps Project field, select the project you want to integrate with Salesforce.
2. Enter a Project Mapping Name to label the connection.

Examples:

• Support Cases → Azure DevOps Bugs
• Opportunities → Azure DevOps Stories

This name serves as the reference point for all synchronization rules related to this project.

Step 3: Choose the Salesforce Object

1. From the Salesforce Object dropdown, select the object whose records you want to synchronize.
   1. Standard objects (e.g., Case, Opportunity)
   2. Custom objects
2. This determines:
   1. Where Azure DevOps work items are created from
   2. Which Salesforce records can be linked to Azure DevOps

Step 4: Select the Azure DevOps Work Item Type

1. In the Azure DevOps Work Item Type dropdown, choose the type to be created.

Examples include:

• Task
• Story
• Epic
• Custom work item types

This ensures the correct Azure DevOps structure is used when issues are created from Salesforce.

Step 5: Select or Create the Azure DevOps Field to Store Salesforce Record ID

To maintain a persistent link between Salesforce records and Azure DevOps work items, Azure DevOps must store the Salesforce Record ID in a dedicated field.

Option A: Select an Existing Custom Field

1. Open the Salesforce Record ID Mapping Field dropdown.
2. If a suitable Azure DevOps custom field already exists, select it.

Option B: Create a New Azure DevOps Custom Field (Recommended)

If no appropriate field exists, create one using the steps below.

Step 6: Create the Required Azure DevOps Custom Field (Text Field)

1. Navigate to the Azure DevOps Work Item page you want to map.
2. Click the Action Dots (⋮) on the page.
3. Select Customize.

In the customization panel:

1. Click New Field.
2. Set Field Name to SFID.
3. Choose Field Type as Text.
4. Enter the Description as shown in the reference configuration.
5. Review the field details.
6. Click Add Field to save and create the field.

Step 7: Return to Salesforce and Complete the Mapping

1. Go back to Salesforce and refresh the ADL Connect configuration page.
2. In the Salesforce Record ID Field dropdown, select the newly created Azure DevOps field.
3. Verify all other mapping details:

• Salesforce Object
• Azure DevOps Project
• Work Item Type

Step 8: Save the Project Mapping

1. Click Save to complete the setup.
2. The project mapping is now active and ready for use.

Result

The project mapping is successfully established.

This configuration links a Salesforce object to an Azure DevOps project and work item type, ensuring that every Azure DevOps item created through ADL Connect maintains a reference to its originating Salesforce record.

This mapping serves as the foundation for:

• Field mappings
• Synchronization rules
• Issue creation and update workflows

Field Mapping Configuration

Once the project mapping has been established, the next step is to configure field-level mappings.

Field mappings define how individual Salesforce fields correspond to Jira fields and determine the direction of data synchronization.

These mappings ensure that updates made in either system flow correctly and consistently based on business requirements.

Follow the steps below to configure field mappings for the selected project connection.

Step 1: Open the Field Mapping Section

1. Navigate to the Project Connection created earlier.
2. Locate and click the Field Mapping action button.

This opens the configuration panel where you define how data moves between Salesforce and Jira.

Step 2: Select the Salesforce Field

1. In the Salesforce Field dropdown, select the field you want to synchronize.
2. The system automatically displays all available fields from the Salesforce object associated with the project connection.
3. Choose the appropriate field based on your integration requirements.

Examples include:

• Title
• Description
• Assignee
• Any custom field created for integration purposes

This selection determines which Salesforce data will participate in the synchronization process.

Inbound rules allow Azure DevOps to send updates back into Salesforce through ADL Connect. These updates can include:

• Field value changes
• Status transitions
• Comments
• Assignments

To enable inbound synchronization, you must:

1. Create an Inbound Rule in ADL Connect
2. Configure a Salesforce Site to receive Azure DevOps webhook requests

Follow the steps below to complete the configuration.

Prerequisites

Before proceeding, ensure that:

• A Project Mapping has already been created in ADL Connect
• The Azure DevOps integration instance is configured and authenticated
• You have Salesforce System Administrator access to configure Salesforce Sites

Step 1: Open the Inbound Rule Configuration

1. Navigate to the Project Mapping you previously created.
2. Locate the Inbound Rule section for that project mapping.
3. Click New Inbound Rule.

This opens the inbound rule configuration interface where you define how incoming updates are processed.

Step 2: Select the Integration App

1. In the Integration App dropdown, select the Azure DevOps integration instance.
2. This ensures the inbound rule is connected to the correct Azure DevOps environment and authentication setup.

Step 3: Choose the Project Mapping

1. In the Project Mapping field, select the mapping created earlier.
2. Verify that the selected mapping corresponds to:

• The correct Salesforce object
• The intended Azure DevOps project and work item type

This ensures inbound data is applied to the correct records.

Configuring the Salesforce Site for Inbound Access

To allow Azure DevOps to call back into Salesforce, a Salesforce Site must be created. This Site provides the public endpoint URL used by Azure DevOps webhooks.

Step 4: Copy the Site Subdomain Prefix ID

1. In the inbound rule configuration panel, locate the Site Subdomain Prefix ID.
2. Copy this value — it will be used while creating the Salesforce Site.
3. Click Add in the Site configuration section.

You will be redirected to the Salesforce Sites setup page.

Step 5: Register a Salesforce Site Domain (If Not Already Enabled)

If Salesforce Sites have not been enabled previously:

1. You will be prompted to register a Site Domain.
2. Enter a unique domain name and click Save.
3. Once registered, you can proceed to create a new Site.

This is a one-time setup per Salesforce org.

Step 6: Create a New Salesforce Site

1. On the Sites page, click New.
2. Enter a Site Label, for example:
   1. ADL Connect Inbound Site
   2. Azure Inbound
3. In the Site Name / Subdomain Prefix field, paste the Site Subdomain Prefix ID copied earlier.
4. This ensures the Site URL matches what ADL Connect expects.
5. Complete the required fields:
   1. Active: ✔ Enabled
   2. Site Contact
   3. Default Web Address
6. Set Active Site Home Page to:
7. ADL_Connect_inbound
8. Click Save to create the Site.

The Site will now generate a public-facing URL that Azure DevOps uses for inbound updates.

Step 7: Finalize the Inbound Rule in ADL Connect

1. Return to ADL Connect.
2. Confirm that the newly created Salesforce Site is selected in the inbound rule configuration.
3. Click Save.

Inbound processing is now enabled for the selected project mapping.

Result

After completing this configuration:

• Azure DevOps can push real-time updates into Salesforce
• The Salesforce Site acts as the secure inbound endpoint
• ADL Connect processes inbound field updates, status changes, comments, and assignments

ADL Connect allows users to create, view, and manage Azure DevOps Work Items directly from Salesforce Case records. This is achieved by adding ADL Connect components to the Case Lightning Record Page and leveraging the configured project mappings and synchronization rules.

This article explains:

• How to configure the Case page layout
• How users create and manage Azure DevOps Work Items from Salesforce
• How outbound and inbound synchronization works
• How to manage Azure DevOps comments from Salesforce

Prerequisites

Before proceeding, ensure that:

• ADL Connect is installed and configured
• Azure DevOps integration and Project Mapping are already set up
• You have permission to edit Lightning Record Pages
• Inbound and outbound sync rules are configured (if bi-directional sync is required)

Step 1: Open and Edit the Case Record Page

1. Open any existing Case record in Salesforce.
2. Click Edit Page to open the Lightning App Builder.

This opens the Case record layout where managed components can be added.

Step 2: Add the ADL Azure DevOps Details Component

1. In the Lightning App Builder, scroll to Custom – Managed Components.
2. Locate ADL AzureDevOps Details.
3. Drag and drop the component into the desired region of the Case page.

Purpose of this component:

• Displays linked Azure DevOps Work Item details
• Allows users to create new Azure DevOps Work Items from Salesforce

1. Click Save.
2. Activate the page for the required apps and profiles if prompted.

Once added, every Case record will support Azure DevOps Work Item management.

Step 3: Start Creating a New Work Item

1. Open a Case record.
2. Locate the ADL AzureDevOps Details component.
3. Click New.

This opens the Azure DevOps Work Item creation panel inside Salesforce.

Step 4: Select the Mapped Azure DevOps Project

1. In the project search field, enter the name of the Azure DevOps project configured in Project Mapping.
2. Select the correct project from the list.

ADL Connect automatically:

• Loads the mapping configuration
• Prepares the Work Item form based on mapped fields

This ensures consistency between Salesforce and Azure DevOps.

Step 5: Review Pre-Populated Field Values

Based on your field mappings, ADL Connect automatically pre-fills values such as:

• Summary
• Description
• Assigned To
• Custom synchronized fields

This minimizes manual entry and ensures data consistency across systems.

Step 6: Assign the Azure DevOps Work Item

1. Use the Assignee field to select an Azure DevOps user.
2. You can choose any user who has access to the selected project.

The assignment is applied immediately in Azure DevOps.

Step 7: Save the Azure Dev Ops Work Item

1. Click Save.
2. The generated Azure DevOps Work Item ID is displayed within Salesforce.

This confirms:

• Successful Work Item creation
• A live link between the Salesforce Case and Azure DevOps

Step 8: Open the Linked Azure DevOps Work Item

1. Click the Azure DevOps Work Item ID shown in Salesforce.
2. The corresponding Work Item opens in Azure DevOps.

Verify that:

• The Work Item is assigned to the correct user
• The Salesforce Case ID appears in the custom Azure DevOps field created for integration

This confirms proper mapping and linkage.

Step 9: Update Work Item Fields from Salesforce

1. In Salesforce, update Azure DevOps–related fields such as:

• Work Item State
• Summary Prefix
• Any custom mapped fields

1. Click Save.

ADL Connect pushes these updates to Azure DevOps using outbound field mappings.

Step 10: Confirm Updates in Azure DevOps

1. Open the same Work Item in Azure DevOps.
2. Verify that:

• The Summary reflects Salesforce changes
• The State is updated (for example, Pending)

This confirms outbound synchronization is working correctly.

Step 11: Update Azure DevOps and Observe Changes in Salesforce

1. In Azure DevOps, update the Work Item (for example, change the State to Done).
2. ADL Connect synchronizes this update back to Salesforce.
3. Refresh the Salesforce Case and verify:

• Azure DevOps State is updated
• All inbound-mapped fields reflect the latest values

This validates inbound synchronization.

Step 12: Add the ADL Azure DevOps Comments Component

1. Click Edit Page on the Case record again.
2. Navigate to Custom – Managed Components.
3. Drag and drop ADL AzureDevOps Comments onto the page.
4. Click Save.

This component enables comment collaboration directly from Salesforce.

Step 13: Post and Sync Comments

1. In the ADL AzureDevOps Comments component, enter a comment.
2. Click Send to post the comment to Azure DevOps.
3. Edit comments if required.
4. Open Azure DevOps and confirm the comment appears on the Work Item.

This ensures seamless, bi-directional collaboration between Salesforce and Azure DevOps teams.

Result

After completing these steps:

• Salesforce users can fully manage Azure DevOps Work Items from Cases
• Field updates sync in both directions
• Comments are shared across platforms
• Teams collaborate without switching systems

This completes the configuration and usage flow for Azure DevOps Work Item integration with Salesforce Cases using ADL Connect.

ADL Connect enables Salesforce users to create Azure DevOps Work Items directly from Salesforce records such as Cases. This capability improves collaboration between support, sales, and development teams by allowing issue creation, assignment, and updates without leaving the Salesforce interface.

This article explains how to:

• Create Azure DevOps Work Items from Salesforce
• Verify synchronization between Salesforce and Azure DevOps
• Update Work Items bidirectionally

Prerequisites

Before creating Azure DevOps Work Items from Salesforce, ensure that:

• A Project Mapping is configured between Salesforce and Azure DevOps
• The ADL AzureDevOps Details component is added to the Salesforce record page
• Users have the required Salesforce and Azure DevOps permissions

Step 1: Access the Work Item Creation Interface

1. Open the Salesforce record (typically a Case) from which you want to create an Azure DevOps Work Item.
2. Locate the ADL AzureDevOps Details component on the record page.
3. Click New.

This opens the Azure DevOps Work Item creation panel embedded within Salesforce.

Step 2: Select the Mapped Azure DevOps Project

1. In the project selection field, begin typing the name of the Azure DevOps project.
2. Select the project that was configured in Project Mapping.

ADL Connect automatically loads:

• Associated Work Item types
• Field mappings
• Default values defined during configuration

This ensures consistent issue creation.

Step 3: Review Pre-Populated Field Values

Based on your mapping configuration, ADL Connect automatically populates fields such as:

• Salesforce field values mapped to Azure DevOps fields
• Summary prefixes or templates
• Priority or classification fields
• Custom integration fields

This reduces manual effort and enforces data consistency.

Step 4: Assign the Azure DevOps Work Item

1. Use the Assignee dropdown to select the Azure DevOps user responsible for the Work Item.
2. Assigning ownership during creation ensures immediate visibility for the development team.

Step 5: Save the Azure DevOps Work Item

1. After completing the required fields, click Save.
2. ADL Connect creates the Azure DevOps Work Item in real time.
3. The generated Azure DevOps Work Item ID is displayed directly in Salesforce.

The Work Item ID becomes the permanent reference for synchronization between Salesforce and Azure DevOps.

Verifying the Azure DevOps Work Item

Step 6: Open and Review the Created Work Item

1. Click the Azure DevOps Work Item ID displayed in Salesforce.
2. The Work Item opens in a new browser tab in Azure DevOps.

Verify that:

• The Work Item is assigned to the correct Azure DevOps user
• The Salesforce record ID appears in the Azure DevOps custom integration field
• All mapped fields are populated correctly

This confirms outbound synchronization is functioning properly.

Step 7: Modify Azure DevOps Fields in Salesforce

1. In the ADL AzureDevOps Details component, update fields such as:
   1. Work Item State
   2. Summary
   3. Description
   4. Other mapped fields
2. Click Save.

ADL Connect immediately pushes these updates to Azure DevOps based on configured sync rules.

Step 8: Validate Changes in Azure DevOps

1. Open the same Work Item in Azure DevOps.
2. Confirm that updates (for example, state or summary changes) are reflected correctly.

This confirms outbound synchronization is working as expected.

Step 9: Confirm Inbound Synchronization

1. In Azure DevOps, update the Work Item (for example, change the State).
2. Return to Salesforce and refresh the record.
3. Confirm that updated values appear in the ADL AzureDevOps Details component.

This verifies that inbound synchronization is enabled and functioning.

Summary

Using the ADL AzureDevOps Details component, Salesforce users can:

• Create Azure DevOps Work Items directly from Salesforce Cases
• Assign Work Items to Azure DevOps team members
• Update issue details bidirectionally
• Maintain real-time visibility into Azure DevOps progress
• Eliminate duplicate data entry across systems

This integration significantly streamlines collaboration between Salesforce teams and Azure DevOps development teams.

ADL Connect allows Salesforce users to view, add, and edit Azure DevOps comments directly from Salesforce. This capability enables customer-facing teams to collaborate with development teams without leaving the Salesforce interface.

Comments added in either system are synchronized automatically, ensuring consistent and up-to-date communication across both Salesforce and Azure DevOps.

Prerequisites

Before working with Azure DevOps comments from Salesforce, ensure that:

• Azure DevOps integration is configured in ADL Connect
• The Salesforce record (typically a Case) is already linked to an Azure DevOps Work Item
• Users have the required Salesforce and Azure DevOps permissions

Step 1: Add the ADL AzureDevOps Comments Component

1. Open any Salesforce record (typically a Case).
2. Click Edit Page to open the Lightning App Builder.
3. Scroll to Custom – Managed Components.
4. Locate the ADL AzureDevOps Comments component.
5. Drag and drop the component onto the desired location on the page layout.
6. Click Save and activate the page for the required apps or profiles.

The Salesforce page is now ready to display and manage Azure DevOps comments.

Step 2: Post a Comment to an Azure DevOps Work Item

1. Open the Salesforce record where the ADL AzureDevOps Comments component is available.
2. In the comment input area, type your message.
3. Click Send.

Once submitted:

• The comment is added to the linked Azure DevOps Work Item
• It becomes immediately visible to Azure DevOps users

Step 3: Edit Existing Comments (If Required)

1. Locate the comment you want to update within the Salesforce component.
2. Click the Edit option.
3. Modify the comment content.
4. Click Save.

The updated comment is synchronized back to Azure DevOps, ensuring both systems display the latest version.

Step 4: Confirm Salesforce → Azure DevOps Comment Sync

1. Open the corresponding Azure DevOps Work Item.
2. Navigate to the Comments section.
3. Verify that the newly added or edited comment from Salesforce is visible.

This confirms that outbound comment synchronization is working correctly.

Step 5: Add a Comment in Azure DevOps

1. Open the Azure DevOps Work Item linked to the Salesforce record.
2. Add a new comment in the Azure DevOps comments section.
3. Save the comment.

Step 6: Refresh Salesforce to View Azure DevOps Comments

1. Return to the Salesforce record.
2. Refresh the page.
3. Verify that the new comment appears in the ADL AzureDevOps Comments component.

This confirms inbound comment synchronization from Azure DevOps to Salesforce.

Summary

By using the ADL AzureDevOps Comments component, Salesforce users can:

• View Azure DevOps comments directly within Salesforce
• Add and edit comments without switching systems
• Maintain synchronized communication between Salesforce and Azure DevOps
• Improve collaboration between customer-facing and development teams

This functionality ensures transparent, real-time communication across platforms and eliminates context switching for users.

ADL Connect enables Salesforce users to view, preview, and upload Azure DevOps attachments directly from Salesforce records. This functionality provides customer-facing teams with full visibility into Azure DevOps Work Item context and allows them to contribute files without switching systems.

Attachments added in Salesforce synchronize instantly to Azure DevOps, and existing Azure DevOps attachments are displayed within the Salesforce interface.

Prerequisites

Before working with Azure DevOps attachments from Salesforce, ensure that:

• Azure DevOps integration is configured in ADL Connect
• The Salesforce record (such as a Case) is linked to an Azure DevOps Work Item
• Users have the required Salesforce and Azure DevOps permissions

Configuring the Salesforce Page Layout for Azure DevOps Attachments

Before viewing or uploading attachments, the ADL AzureDevOps Attachments component must be added to the Salesforce record page.

Step 1: Add the ADL AzureDevOps Attachments Component

1. Open the Salesforce record linked to the Azure DevOps Work Item (for example, a Case).
2. Click Edit Page to open the Lightning App Builder.
3. Scroll to Custom – Managed Components.
4. Locate the ADL AzureDevOps Attachments component.
5. Drag and drop the component into the desired area of the page layout.
6. Click Save and activate the page if required.

Once added, the component displays all attachments associated with the linked Azure DevOps Work Item.

Viewing Azure DevOps Attachments in Salesforce

Step 2: View or Preview Existing Attachments

1. Navigate to the updated Salesforce record.
2. In the ADL AzureDevOps Attachments component, review the list of attachments already stored in Azure DevOps.
3. Optionally, switch the display to Tile View.
   1. Tile View allows image previews without downloading files.
4. Click any attachment to preview it or download it directly from Salesforce.

Tile View is especially useful for image-heavy attachments such as screenshots, diagrams, and UI mock-ups.

Uploading Attachments to Azure DevOps from Salesforce

Step 3: Upload New Attachments

1. In the ADL AzureDevOps Attachments component, click Add or Upload Attachments.
2. Select one or more files from your device.
3. Confirm the upload.

The selected files are immediately uploaded to the associated Azure DevOps Work Item.

Step 4: Verify the Upload in Azure DevOps

1. Open the corresponding Azure DevOps Work Item.
2. Navigate to the Attachments section.
3. Confirm that the files uploaded from Salesforce are visible.

This verifies that Salesforce → Azure DevOps attachment synchronization is functioning correctly.

Summary

Using the ADL AzureDevOps Attachments component, Salesforce users can:

• View all Azure DevOps attachments directly within Salesforce
• Preview images using Tile View without downloading
• Upload new files from Salesforce into Azure DevOps
• Maintain complete context for customer cases and development work

This capability reduces platform switching and significantly improves collaboration between support and engineering teams.

ADL Connect allows Salesforce users to search for existing Azure DevOps Work Items directly from Salesforce and link them to Salesforce records such as Cases. This capability helps prevent duplicate issue creation, improves traceability, and automatically retrieves related Azure DevOps details—including comments and attachments—into Salesforce.

Prerequisites

Before using the Search and Link feature, ensure that:

• Azure DevOps integration is configured in ADL Connect
• A Project Mapping exists between Salesforce and Azure DevOps
• The Salesforce record page includes the ADL AzureDevOps Details component
• Users have the required Salesforce and Azure DevOps permissions

Step 1: Initiate an Azure DevOps Work Item Search

1. Open the Salesforce record where ADL Connect is enabled (for example, a Case).
2. In the ADL AzureDevOps Details component, click Search.

This opens the Azure DevOps Work Item search interface within Salesforce.

Step 2: Enter a Search Keyword

1. In the search field, enter a keyword related to the Azure DevOps Work Item you want to locate.
   1. Keywords may include Work Item ID, summary text, description keywords, or other searchable values.
2. Review the list of Azure DevOps Work Items returned by the search.

Search results are fetched in real time from Azure DevOps, ensuring the latest data is displayed.

Step 3: Select the Azure DevOps Work Item to Link

1. From the search results, select the Azure DevOps Work Item to associate with the Salesforce record.
2. ADL Connect displays a preview of mapped fields.

During preview:

• Fields are pre-populated based on your Project Mapping configuration
• You can verify that the correct Work Item is being linked

Step 4: Save the Link

1. Click Save to complete the linking process.
2. The selected Azure DevOps Work Item is now associated with the Salesforce record.

This creates a direct relationship between Salesforce and the existing Azure DevOps Work Item.

Automatic Retrieval of Azure DevOps Details

After the Work Item is linked:

• ADL Connect automatically retrieves associated comments, attachments, and other mapped data
• Retrieved details are displayed within the relevant ADL AzureDevOps components on the Salesforce page
• Salesforce users gain full visibility into Azure DevOps activity without navigating away from Salesforce

Summary

Using the Search and Link feature, Salesforce users can:

• Search Azure DevOps Work Items directly from Salesforce
• Avoid creating duplicate Azure DevOps Work Items
• Link the correct Work Item to a Case or other Salesforce record
• Automatically retrieve existing comments, attachments, and status information

This functionality creates a unified workflow and strengthens collaboration between support, engineering, and product teams by keeping all relevant issue context inside Salesforce.

General Overview

Q1: What is ADL Connect and what problem does it solve?

A: ADL Connect is a bidirectional integration tool that synchronizes Salesforce records with Azure DevOps Work Items. It eliminates duplicate data entry, improves collaboration between support and development teams, and provides real-time visibility into issue progress—without requiring users to switch systems.

Q2: Which Jira versions does ADL Connect support?

A: ADL Connect supports:

• Jira Cloud
• Jira Data Center
• Jira Server (if still active in your environment)

Authentication methods vary depending on the Jira deployment.

Q3: Can I try ADL Connect before purchasing a license?

A: Yes. ADL Connect offers a free 30-day trial via Salesforce AppExchange, allowing full feature evaluation before purchase.

Setup and Configuration

Q4: Do I need admin permissions to configure ADL Connect?

A: Yes.

• Salesforce: System Administrator permissions are required to install the package, configure page layouts, set up Salesforce Sites, and manage field-level security.
• Azure DevOps: Administrator permissions are required to create custom fields and manage API tokens.

Q5: Why is a custom Azure DevOps field required for Salesforce record IDs?

A: ADL Connect requires a custom short-text field in Azure DevOps to store the Salesforce record ID. This field enables the connector to:

• Link Azure DevOps Work Items back to Salesforce
• Maintain bidirectional field synchronization
• Prevent duplicate issue relationships

Without this field, linking and synchronization will not function correctly.

Q6: How do I authenticate Salesforce with Azure DevOps?

A: Authentication is performed using:

• Microsoft email or username
• Azure DevOps API Token

The token must be generated in Azure DevOps user settings and entered into the ADL Connect Authentication Console.

Q7: Which Salesforce objects can be synced with Azure DevOps Work Items?

A: ADL Connect supports:

• Standard objects (e.g., Case, Opportunity, Account)
• Custom objects

Any field can be mapped as long as the Salesforce and Azure DevOps data types are compatible.

Q8: What is a Project Mapping and why is it required?

A: A Project Mapping defines:

• Which Salesforce object maps to which Azure DevOps project
• Which Azure DevOps Work Item type is used
• Which Azure DevOps field stores the Salesforce record ID

It is the foundation for all field mappings and synchronization logic.

Synchronization Behavior

Q9: What synchronization directions are supported?

A: ADL Connect supports:

• Salesforce → Azure DevOps (Outbound)
• Azure DevOps → Salesforce (Inbound)
• Bidirectional synchronization

Sync direction is configurable at the field level.

Q10: How often does data synchronization occur?

A: Synchronization is near real-time.

• Outbound sync occurs immediately when Salesforce records are saved.
• Inbound sync occurs as soon as Azure DevOps sends webhook events to Salesforce via the configured Salesforce Site.

Q11: Can I control which fields sync between Salesforce and Azure DevOps?

A: Yes. Field-level mapping allows you to define:

• Field-to-field relationships
• Sync direction
• Required, optional, or read-only behavior

Q12: Are comments and attachments synchronized?

A: Yes.

• Comments synchronize bidirectionally between Salesforce and Azure DevOps.
• Attachments can be viewed, uploaded, and downloaded directly from Salesforce.

Q13: How does ADL Connect prevent accidental data overwrites?

A: Each field mapping includes a defined sync direction, allowing you to control which system acts as the source of truth for each field.

Usage Questions

Q14: Can Salesforce users create Azure DevOps Work Items without Azure DevOps licenses?

A: Yes. Salesforce users do not require Azure DevOps licenses to create or update Work Items through ADL Connect. Azure DevOps license restrictions apply only within Azure DevOps itself.

Q15: Can Azure DevOps Work Items be edited directly from Salesforce?

A: Yes. Using the ADL AzureDevOps Details component, users can update:

• State
• Summary
• Assignee
• Any mapped fields

All updates sync to Azure DevOps in real time.

Q16: Can I link an existing Azure DevOps Work Item instead of creating a new one?

A: Yes. The Search & Link feature allows users to:

• Search Azure DevOps by keyword
• Select an existing Work Item
• Link it to a Salesforce record
• Automatically retrieve comments and attachments

Q17: Can multiple Salesforce records link to the same Azure DevOps Work Item?

A: This depends on configuration. By default, one Salesforce record maps to one Azure DevOps Work Item, but advanced configurations can support one-to-many relationships.

Troubleshooting

Q18: Some Salesforce fields do not appear in the Azure DevOps Details component. What should I check?

Verify that:

• The field is on the Page Layout
• The field is included in the Lightning Record Page
• Field-Level Security allows visibility
• The field is included in Project Mapping and Field Mapping

Q19: Inbound synchronization is not working. What should I verify first?

Check the following:

1. Salesforce Site domain is registered
2. Correct Site Subdomain Prefix ID is used
3. Guest User permissions are configured correctly
4. Azure DevOps webhook points to the correct Site endpoint
5. Inbound Rule is saved and mapped correctly

Q20: Why are Azure DevOps comments not appearing in Salesforce?

Common causes include:

• Azure DevOps webhook not configured
• Missing inbound permissions
• Azure DevOps Comments component not added to the page
• Incorrect project or field mapping

Q21: Why does the Azure DevOps Work Item ID not appear after creation?

Verify that:

• API token authentication is valid
• Project Mapping is correctly configured
• Salesforce record is saved before Work Item creation
• Azure DevOps custom Salesforce ID field exists and is mapped

Q22: Attachments are not appearing in Salesforce. What should I do?

Ensure that:

• ADL AzureDevOps Attachments component is added to the page
• Salesforce Site Guest User has read access to attachment fields
• Azure DevOps API permissions allow attachment access

Security and Access

Q23: How secure is Salesforce–Azure DevOps authentication?

A: Authentication uses API tokens and HTTPS endpoints. Passwords are never stored in Salesforce, and tokens can be revoked at any time in Azure DevOps.

Q24: Does the Salesforce Site Guest User pose a security risk?

A: No, when properly configured. Security is maintained by:

• Granting only required permissions
• Restricting object and field access
• Using Salesforce sharing rules

ADL Connect accesses only mapped objects and fields.

Q25: Can I restrict who can create Azure DevOps Work Items in Salesforce?

A: Yes. Component access can be controlled using:

• Profiles
• Permission sets
• Lightning page visibility rules

Licensing and Maintenance

Q26: Do all Salesforce users need ADL Connect licenses?

A: Only users who interact with ADL Connect components require licenses. Administrators configuring the integration also require licenses.

Q27: What happens if the ADL Connect license expires?

A: Issue creation and synchronization are disabled until renewal. Existing mappings and integrated data remain intact.

Q28: How often are updates released?

A: Updates are released periodically through Salesforce AppExchange. Administrators are notified when new versions are available.