Microsoft Azure integration with Salesforce

Challenges

- Data related to leads was not recorded in Salesforce.
- Duplicate records in tables in Microsoft Azure.
- Azure database was keeping leads in different tables based on leads’ status.

Solutions

- Integrated Microsoft Azure with the Salesforce org.
- Created field mapping between Azure and Salesforce lead object.
- Used standard Salesforce bulk API for pushing data to Salesforce from Azure in batches.

Results

- Unified Data Structure
- Improved Decision-making
- Enhanced Efficiency

Our client is a lending company that provides loans to the healthcare professionals. They provide quick and easy financing for doctors, nurses, dentists, veterinarians and more. The organization provides different types of loans on the basis of different criteria. This case study outlines the challenges faced by the lending company, the solutions implemented for Azure-Salesforce integration, and the desired outcome of a unified system for improved decision-making and convenience.

The client was looking for a technology partner who would help them with seamless integration of Microsoft Azure and Salesforce. The leads were getting recorded in the Azure database, but the client wanted it to be also recorded in Salesforce to enhance their convenience. They didn’t want to leave Microsoft Azure since it was doing deduplication of leads and was also performing data nurturing/enrichment.

Key Industry

- Financial services

Key Pains

- The client’s Microsoft Azure system was not integrated with Salesforce and therefore the data related to leads was not getting recorded in Salesforce.

Product Mix

- Microsoft Azure database
- Salesforce bulk API

Leads were getting generated through multiple channels and were getting consolidated in Microsoft Azure database. The client wanted this data to be recorded in Salesforce.

01
02

Leads had multiple fields with different data types. Data related to a particular lead was stored in different tables on the basis of its status which led to duplication of records for a particular contact.

Since, Salesforce has only one lead object, there was a need to merge these tables within Azure and do deduplication on the leads records. This was done within Azure.

03
04

The client was facing challenges in analyzing data in Azure database and make data-driven decisions. Therefore, they wanted it to integrate with Salesforce.

  1. Created a field mapping between Azure and Salesforce lead object. Created custom fields on Salesforce lead object and added validations as required.
  2. Created a connected app in Salesforce for authentication and establishing integration between Azure and Salesforce. Also, created an integration user in Salesforce.
  3. Used standard Salesforce bulk API for pushing data to Salesforce from Azure in batches.
  4. Created a function to bring leads from Microsoft azure database to Salesforce on a frequency basis (every 6 hours).
  1. Enhanced Insights: The unified data from both systems enabled the company to gain a 360-degree view, leading to more informed decisions and targeted marketing efforts.
  2. Unified Data Structure: Field mapping and the creation of custom fields in Salesforce's lead object allowed for a standardized data structure, accommodating various data types and ensuring consistency across different statuses of leads.
  3. Improved Decision-making: The integration allowed for a holistic view of lead data, empowering the lending company to analyze information from both Azure and Salesforce collectively. This enhanced insights supported data-driven decision-making processes.
  4. Enhanced Efficiency: Automation of data transfer using the Salesforce Bulk API and the scheduled function to bring leads from Azure to Salesforce every 6 hours increased operational efficiency, ensuring up-to-date information.