Integrations
Overview
This document provides an overview of Lifecycle Management (LCM) integrations supported by Veza, including their capabilities and supported actions. It also outlines how to enable and manage these integrations for LCM.
Supported Integrations
The table below outlines whether each integration can serve as a Source of Identity and the lifecycle actions it supports.
| Integration | Source of Identity | Manage Relationships | Other Supported Actions |
|---|---|---|---|
Active Directory | No | Yes | Sync Identities, De-provision Identity |
AWS SSO | No | Yes | Sync Identities, De-provision Identity |
Azure AD | No | Yes | Sync Identities, De-provision Identity |
Exchange Server | No | No | Create Email |
GitHub | Yes | Yes | Sync Identities, De-provision Identity |
Google Cloud | Yes | Yes | Sync Identities, De-provision Identity |
Custom HRIS (OAA Template) | Yes | No | N/A |
Okta | Yes | Yes | Sync Identities, De-provision Identity |
Salesforce | No | Yes | Sync Identities, De-provision Identity |
SAP ECC | No | Yes | Sync Identities, De-provision Identity |
Snowflake | No | Yes | Sync Identities, De-provision Identity |
Workday | Yes | Yes | Write Back Email |
Custom Application (OAA Template) | No | Yes | Sync Identities, De-provision Identity |
Insight Point for Lifecycle Management
An Insight Point is required to enable Lifecycle Management operations and identity discovery for systems that Veza cannot access directly. The Insight Point is a lightweight connector that runs in your environment, enabling secure gathering and processing of authorization metadata for LCM tasks.
A Veza Insight Point is typically deployed as a Docker container or VM OVA, running within your network for metadata discovery and LCM job execution. This ensures secure communication between your environment and Veza.
For deployment instructions, refer to the Insight Point Documentation.
Enabling Lifecycle Management
Scheduled and Manual Extractions
You can configure extraction intervals for your integrations to ensure data is regularly updated for Lifecycle Management processes.
Go to Veza Administration > System Settings
In the Pipeline > Extraction Interval section, set the global extraction interval
To override the global setting for specific integrations, use the Active Overrides section
Available extraction intervals:
Auto (hourly, but may take longer when the extraction pipeline is full)
15 Minutes
1 Hour
6 Hours
12 Hours
1 Day
2 Days
3 Days
7 Days
30 Days
To manually trigger an extraction:
Go to Integrations > All Data Sources
Search for the desired data source
Select Actions > Start Extraction
Note: Custom application payloads are extracted after the payload is pushed to Veza using the Open Authorization API.
Enabling Lifecycle Management
To enable Lifecycle Management for a specific integration:
Browse to the main Veza Integrations page, or go to Lifecycle Management > Integrations
Search for the integration you want to enable
Toggle the Lifecycle Management option to Enabled
Additional Resources
For more information:
Refer to individual integration documentation for detailed LCM capabilities
Consult the Lifecycle Management user guide for troubleshooting and best practices
Contact Veza support for assistance with enabling or configuring LCM for your integrations
Last updated
