Microsoft Azure Key Vault (beta) connection¶

Introduction¶

A Microsoft Azure Key Vault (beta) connection, created using the Microsoft Azure Key Vault (beta) connector, establishes access to Microsoft Azure Key Vault. Once a connection is configured, you can create instances of Microsoft Azure Key Vault (beta) activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Note

This connector is currently released as a beta version and is available only to select organizations. To participate in the beta program or provide feedback on bugs and enhancements, contact your Customer Success Manager (CSM).

Prerequisites¶

These Microsoft Azure resources are required for a successful connection:

An active Microsoft Entra ID tenant associated with the key vault.
An app registration associated with the tenant and key vault.

Create or edit a Microsoft Azure Key Vault (beta) connection¶

A new Microsoft Azure Key Vault (beta) connection is created using the Microsoft Azure Key Vault (beta) connector from one of these locations:

The design component palette's Project endpoints and connectors tab (see Design component palette).
The Global Connections page (see Create a global endpoint in Global Connections).

An existing Microsoft Azure Key Vault (beta) connection can be edited from these locations:

The design component palette's Project endpoints and connectors tab (see Design Component Palette).
The project pane's Components tab (see Component actions menu in Project pane Components tab).
The Global Connections page (see Edit a global endpoint in Global Connections).

Configure a Microsoft Azure Key Vault (beta) connection¶

Each user interface element of the Microsoft Azure Key Vault (beta) connection configuration screen is described below.

Microsoft Azure Key Vault connection configuration

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

Connection name: Enter a name to use to identify the connection. The name must be unique for each Microsoft Azure Key Vault (beta) connection and must not contain forward slashes / or colons :. This name is also used to identify the Microsoft Azure Key Vault (beta) endpoint, which refers to both a specific connection and its activities.
Tenant ID: Enter the tenant (directory) ID associated with the key vault.
Client ID: Enter the client (application) ID associated with the key vault.
Subscription ID: Enter the subscription ID associated with the key vault.
Client secret: Enter the client secret associated with the key vault.
Test: Click to verify the connection using the specified configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.
Save Changes: Click to save and close the connection configuration.
Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.
Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps¶

After a Microsoft Azure Key Vault (beta) connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector Basics.

These activity types are available:

Certificate: Performs an operation on a Microsoft Azure Key Vault certificate and is intended to be used as a source or target in an operation.
Secret: Performs an operation on a Microsoft Azure Key Vault secret and is intended to be used as a source or target in an operation.
Vault: Performs an operation on a Microsoft Azure Key Vault key vault and is intended to be used as a source or target in an operation.
Key: Performs an operation on a Microsoft Azure Key Vault key and is intended to be used as a source or target in an operation.