Skip to Content

Microsoft Azure Files (Beta) connector for Jitterbit Integration Studio

Summary

The Microsoft Azure Files (Beta) connector establishes access to Microsoft Azure Files.

The Microsoft Azure Files (Beta) connector provides an interface for creating a Microsoft Azure Files (Beta) connection, the foundation used for generating instances of Microsoft Azure Files (Beta) activities. These activities, once configured, interact with Microsoft Azure Files (Beta) through the connection.

The Microsoft Azure Files (Beta) connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Note

To provide feedback on this beta feature, contact the Jitterbit Product Team.

Connector overview

This connector is used to first configure a Microsoft Azure Files (Beta) connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Microsoft Azure Files (Beta) connection and its activities are referred to as a Microsoft Azure Files (Beta) endpoint:

Microsoft Azure Files activity types

  • 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.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The Microsoft Azure Files (Beta) connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Microsoft Azure Files (Beta) connector uses the Microsoft Azure Files REST API. Refer to the API documentation for information on the schema nodes and fields.

See the Microsoft Azure Files (Beta) prerequisites page for more information on successfully establishing a connection with and using the Microsoft Azure Files (Beta) connector.

Troubleshooting

If you experience issues with the Microsoft Azure Files (Beta) connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Ensure any Microsoft Entra ID app registrations associated with the connection are not using the deprecated Azure AD Graph.

  3. Check the operation logs for any information written during execution of the operation.

  4. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  5. If using private agents, you can enable connector verbose logging for this connector by adding this logger configuration entry to your private agent's logback.xml file:

    <logger name="org.jitterbit.connector.microsoft.azurefiles" level="DEBUG"/>

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

  6. If using private agents, you can check the agent logs for more information.

  7. For additional troubleshooting considerations, see Operation troubleshooting.