---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Create an AI connection for Veza access intelligence

# Create an AI connection for Veza access intelligence {#ariaid-title1}

Release version: Brazil  
Updated September 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Connect AI Control Tower to Veza using OAuth 2.0 so that agent risk scores and severity levels from Veza access intelligence appear in the agent map. Since Veza is an enrichment connector, it doesn't import new
assets.

## Before you begin

Confirm the following are in place:

* An OAuth 2.0 app or client configured in your Veza tenant. For more information, see [OAuth2 apps](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/developers/api/authentication/oauth2-apps) and [OAuth2 clients](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/developers/api/authentication/oauth2-clients) in Veza documentation.
* An OAuth profile configured on the ServiceNow platform and linked to the pre-provided <kbd class="ph userinput">SN AI Security Veza Connector</kbd> connection alias. For more information, see [Set up OAuth](https://www.servicenow.com/docs/r/platform-security/authentication/t_SettingUpOAuth.html).

Role required: sn_ai_governance.ai_steward

## About this task

The Veza connector authenticates using OAuth 2.0 only. Create the AI connection after you complete OAuth setup on both the Veza tenant and the ServiceNow platform.

## Procedure

1. Navigate to SettingsIntegrationsConnectors.
2. On the Available connectors tab, select the Veza tile from security connectors.
3. On the Configure connector page, confirm that Provider type is set to Security.  
   The Connection alias field is pre-populated with SN AI Security Veza Connector and can't be edited.
4. Select the I have configured the Veza user integration check box.  
   This confirms you completed the Veza-side OAuth setup. See [Configure OAuth in Veza](https://www.servicenow.com/docs/7G2cQTN0PxCykr9aDhj8bQ "Create an OAuth 2.0 client and an OAuth 2.0 app in your Veza tenant so that AI Control Tower can authenticate to Veza using OAuth 2.0 instead of an API key.").
5. Select the I have configured ServiceNow connectors/alias settings check box.  
   This confirms you completed the ServiceNow-side OAuth setup. See [Configure OAuth for Veza in ServiceNow](https://www.servicenow.com/docs/eIK_L7EyQZq4B0e987rX2g "Set up two application registries, their OAuth entity scopes and credentials, then link them to the pre-provided connection alias, so that AI Control Tower can authenticate to Veza using OAuth 2.0.").  
   The Validate Connection button is disabled until both check boxes are selected.
6. Select Validate Connection.  
   If the connection already has a valid OAuth token, a Connection Valid message appears. If it doesn't, the button instead shows Authenticate Connection.
   * If the button shows Validate Connection, continue to the next step.
   * If the button shows Authenticate Connection, select it to log in to Veza. After you log in and allow access, the connection revalidates.
7. Select Save.
{#aict-create-ai-connection-veza__steps_veza_connector}

## Result

The connection appears on the Established connections tab. Selecting Re-Validate from that tab updates the connection status.

*[\>]: and then