Learn about Reltio's support for executing Lifecycle Actions as Azure Functions hosted in your own Azure environment.

Azure Function Lifecycle Actions (LCAs) let you run your own custom code when specific Reltio events occur—like validating data or enriching profiles. Instead of hosting this logic in Reltio, you can now deploy it as a serverless function in your own Microsoft Azure environment. This brings Azure support in line with what Reltio already offers for AWS Lambda and Google Cloud Functions.

Previously, you needed to host LCAs in Reltio's AWS environment, resulting in limited autonomy and requiring Reltio Support for deployment and maintenance. With Azure Function LCAs, you can now self-manage their lifecycle logic directly within their cloud infrastructure.

Azure Function LCAs support two authentication methods. You can configure Microsoft Entra ID authentication by using Reltio's Azure app registration flow, or you can configure OAuth2 client credentials so that Reltio authenticates through your own identity provider. Choose the authentication method that matches your Azure Function security model.

Use Azure Function LCAs when:

• Your organization is standardized on Microsoft Azure

• You want to define custom actions triggered by Reltio workflows (e.g., enrich, validate, export)

• You need full control over function deployment, configuration, and observability

You can implement this feature by:

• Building your logic using Reltio's sample repo from https://bitbucket.org/reltio-ondemand/life-cycle-sample/src/master/
  Attention: The repository containing sample code for building LCAs is temporarily unavailable. If you plan to use the sample code, create a support ticket to request it.

• Deploying the function as an Azure Function App

• Choosing one authentication method:

  • For Microsoft Entra ID authentication, contact Reltio Support to create an Azure app, then see Configure Microsoft Entra ID authentication for Azure LCAs

  • For customer-managed OAuth2 authentication, see Configure OAuth2 client credentials for Azure LCAs

• Updating L3 configuration to enable invocation