Microsoft Azure Files (Beta) connection
Introduction
A Microsoft Azure Files (Beta) connection, created using the Microsoft Azure Files (Beta) connector, establishes access to Microsoft Azure Files. Once a connection is configured, you can create instances of Microsoft Azure Files (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
To provide feedback on this beta feature, contact the Jitterbit Product Team.
Create or edit a Microsoft Azure Files (Beta) connection
A new Microsoft Azure Files (Beta) connection is created using the Microsoft Azure Files (Beta) connector from one of these locations:
- The design component palette's Project endpoints and connectors tab (see Design component palette).
- The Global Endpoints page (see Create a global endpoint in Global Endpoints).
An existing Microsoft Azure Files (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 Endpoints page (see Edit a global endpoint in Global Endpoints).
Configure a Microsoft Azure Files (Beta) connection
Each user interface element of the Microsoft Azure Files (Beta) connection configuration screen is described below.
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 Files (Beta) connection and must not contain forward slashes
/
or colons:
. This name is also used to identify the Microsoft Azure Files (Beta) endpoint, which refers to both a specific connection and its activities. -
Storage account name: Enter the name used for the Azure Files storage account.
-
Authentication type: Select the authentication type, one of the following.
Important
For information on obtaining credentials, see the Microsoft Azure Files (Beta) prerequisites page.
-
Microsoft Entra ID: Select to authenticate using Microsoft Entra ID:
-
Tenant ID: Enter the tenant (directory) ID associated with Azure Files.
-
Client ID: Enter the client (application) ID associated with Azure Files.
-
Client secret: Enter the client secret associated with Azure Files.
-
-
Shared Access Signatures: Select to authenticate using a shared access signature (SAS) token:
- SAS token: Enter a SAS token for authentication.
-
Access Keys: Select to authenticate using an access key:
- Key: Enter an access key for authentication.
-
-
Optional settings: Click to expand additional optional settings:
- Use Proxy Settings (Private Agent Only): When using a private agent, this setting can be selected to use private agent proxy settings.
-
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 Files (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:
-
Move Files: Moves files in a Microsoft Azure Files file share and is intended to be used as a target in an operation.
-
Get File: Retrieves a file from a Microsoft Azure Files file share and is intended to be used as a source in an operation.
-
Create Files: Creates files in a Microsoft Azure Files file share and is intended to be used as a target in an operation.
-
List Files: Lists files in a Microsoft Azure Files file share and is intended to be used as a source in an operation.
-
Delete Files: Deletes files from a Microsoft Azure Files file share and is intended to be used as a target in an operation.