Products · HCM OneConnect

Identity provisioning, driven by Fusion HCM.

HCM OneConnect provisions and de-provisions user identities across enterprise systems from a single source of truth — Oracle Fusion HCM. New hires, transfers, and terminations flow automatically.

Overview

What it does.

HCM OneConnect listens to lifecycle events in Oracle Fusion HCM — hire, transfer, leave, terminate — and propagates them to Microsoft Entra ID, Google Workspace, Microsoft Teams, internal applications, and downstream systems within minutes. Account creation, group membership, license assignment, and offboarding execute as policy, not as tickets. Audit trail is captured for every change.

Capabilities

Key capabilities.

Architecture

How it works.

HCM OneConnect listens to Oracle Fusion HCM lifecycle events via Oracle Integration Cloud and an event-driven architecture. Events route to a rule engine that resolves the policy for the affected worker, then dispatches provisioning actions to the appropriate destination systems. The product is currently delivered on Oracle Fusion, architected to extend to other HCM systems (Workday, SAP SuccessFactors) when warranted.

Source

  • Oracle Fusion HCMHire, transfer, leave, terminate

Integration

  • Oracle Integration CloudEvent-driven routing

HCM OneConnect

  • Rule engineResolves the policy per worker
  • Audit trailEvery change recorded

Destinations

  • Microsoft Entra ID
  • Google Workspace
  • Active DirectoryOn-premise
  • Downstream applicationsTeams, licenses, custom REST
HCM OneConnect architecture diagram showing Oracle Fusion HCM as the source, Oracle Integration Cloud routing lifecycle events to Microsoft Entra ID, Google Workspace, Active Directory, and downstream applications, with a central rule engine resolving policy per worker.

Audience

Who it's for.

HR and IT operations leaders

Tired of joiner-mover-leaver tickets blocking new hires from being productive on day one.

CISOs and compliance teams

Want audit-ready evidence that access reflects employment status, not last quarter's HR snapshot.

Enterprise IT architects

Modernizing identity around Fusion HCM as the system of record, without bespoke ETL.

Frequently asked questions.

Does it work with non-Fusion HCM systems?

Currently delivered on Oracle Fusion HCM. The architecture is designed to extend to other HCMs (Workday, SAP SuccessFactors) by replacing the event source and the worker-data mapping. Non-Oracle source support is roadmapped; current commitments are Fusion-only.

How fast is provisioning after an HR event?

Typically minutes from the Fusion event to the destination system. The exact latency depends on the destination's API rate limits and the policy complexity — measured and dashboarded per environment.

Can we customize the policies?

Yes. Policies are configuration, not code — managed through a rule editor with naming conventions, group memberships, license tiers, and access profiles per role, location, employment type, or any combination.

What happens if a destination system is down?

Provisioning actions retry with exponential backoff. Failed actions enter a dead-letter queue with notifications to operations. Reconciliation jobs catch up once the destination recovers.

Does it support de-provisioning on termination?

Yes — scheduled, immediate, or grace-period de-provisioning depending on policy. Mailbox conversion, group removal, license reclamation, and downstream account closure are all configurable per termination type.

Want to see it in action?

Tell us about your environment. We respond to inquiries within 2 business days.