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

Deploying an Absence Analyst Agent in Oracle AI Agent Studio — What Nobody Tells You

 

Deploying an Absence Analyst Agent in Oracle AI Agent Studio — What Nobody Tells You

Category: Oracle AITags: AI Agent Studio, Absence, HCM

Oracle AI Agent Studio lets you build intelligent agents that run inside Oracle Fusion — no external tools required. I recently deployed a Workforce Operations Absence Analyst agent, and I want to share the exact issues I hit and how I resolved them.

What the Agent Does

The Absence Analyst agent monitors absence trends across teams, flags unusual patterns, and surfaces insights without a human having to run reports manually. It connects to HCM Absence records and uses configured business rules to classify and summarise absences.

The JSON Node Error — What It Looks Like

The most common failure during deployment is a JSON node misconfiguration. The agent workflow file (.wf) stores node definitions in JSON format. A missing comma, an extra bracket, or a misquoted key will silently break the entire flow.

{
  "nodeType": "ABSENCE_QUERY",
  "parameters": {
    "dateRange": "CURRENT_MONTH"   ← missing comma after this line
    "employeeScope": "ALL_ACTIVE"
  }
}

✦ Always validate your .wf JSON against a linter before saving. Even one syntax error causes the entire agent to fail at runtime with a generic "Node execution failed" message — no line number given.

Debugging the .wf File

1. Download the .wf file from the Agent Studio export
2. Open in VS Code and run JSON validation (Ctrl+Shift+P → Format Document)
3. Look for red squiggles — fix all JSON syntax errors
4. Re-import the corrected file into AI Agent Studio
5. Test in Sandbox environment before promoting to Production

Deployment Checklist

Step	Action	Common Mistake
1	Configure data source connection	Wrong HCM environment URL
2	Define agent role and permissions	Missing Absence Viewer role
3	Upload .wf workflow file	JSON syntax errors
4	Set trigger schedule	Timezone mismatch (use UTC)
5	Test in Sandbox	Skipping this step

Once the agent is live, it saves HR teams hours each week. The output is surfaced directly in the HCM dashboard — no separate tool, no export, no manual refresh.

Oracle AI Agent StudioOracle Fusion HCMAbsence ManagementWorkforce Analytics