Building an Employee Attrition Prediction Model with Azure ML Studio and Oracle HCM

 Category: Azure ML / HCM Integration

Tags: Azure ML, OTBI, VBCS, Attrition

Predicting employee attrition before it happens is one of the most valuable things an HR analytics team can do. In this post I walk through how I built a full pipeline: Oracle HCM data → Azure ML AutoML → Managed Online Endpoint → OTBI/VBCS for display.

Step 1 — Export the Dataset from Oracle HCM

Use an OTBI analysis or HCM Extract to pull the training dataset. Key columns to include:

• Employee tenure (months)
• Department, Job Function, Grade
• Absence frequency (last 12 months)
• Performance rating (last 2 cycles)
• Last promotion date
• Voluntary termination flag (target variable: 1 = left, 0 = stayed)

Export as CSV and upload to Azure Blob Storage.

Step 2 — Run AutoML Classification in Azure ML Studio

# Azure ML AutoML setup (Python SDK)
from azure.ai.ml import MLClient
from azure.ai.ml.automl import classification

automl_job = classification(
    compute="cpu-cluster",
    training_data=training_data,
    target_column_name="attrition_flag",
    primary_metric="AUC_weighted",
    n_cross_validations=5,
    enable_model_explainability=True
)

returned_job = ml_client.jobs.create_or_update(automl_job)

✦ Use AUC_weighted as the primary metric for attrition prediction — the dataset is almost always imbalanced (far more retained employees than terminations). Accuracy alone will mislead you.

Step 3 — Deploy to Managed Online Endpoint

Once the best model is selected by AutoML, deploy it as a REST endpoint. This gives Oracle VBCS a URL to call for real-time predictions.

az ml online-endpoint create --name attrition-endpoint
az ml online-deployment create \
  --endpoint-name attrition-endpoint \
  --name blue \
  --model azureml:attrition-model:1

Step 4 — Connect to Oracle VBCS

In VBCS, create a new Service Connection pointing to the Azure ML endpoint URL. Pass employee attributes as the request payload. Display the attrition risk score in a custom HCM dashboard tile.

Step 5 — Surface Results in OTBI

Write the prediction scores back into a custom Oracle HCM attribute (using HCM Extracts in reverse or a REST API write-back). Create an OTBI analysis that shows high-risk employees by department, enabling HR to act proactively.

Azure ML StudioOracle Fusion HCMOTBIVBCSAttrition PredictionAutoML