MS Azure AD Connector¶
The Harmony MS Azure AD Connector establishes access to Microsoft Entra ID.
Azure Active Directory (Azure AD) is now known as Microsoft Entra ID.
The MS Azure AD connector provides an interface for creating an MS Azure AD connection, the foundation used for generating instances of MS Azure AD activities. These activities, once configured, interact with Microsoft Azure Active Directory through the connection.
The MS Azure AD connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a MS Azure AD 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 MS Azure AD connection and its activities are referred to as an Azure AD endpoint:
Query: Queries object data in Microsoft Azure Active Directory and is intended to be used as a source in an operation.
Create: Creates object data in Microsoft Azure Active Directory and is intended to be used as a target in an operation.
Update: Updates object data in Microsoft Azure Active Directory and is intended to be used as a target in an operation.
Delete: Deletes object data from Microsoft Azure Active Directory and is intended to be used as a target in an operation.
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 MS Azure AD 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 MS Azure AD connector uses the Microsoft Graph API v1.0. Refer to the API documentation for information on the schema nodes and fields.
If you experience issues with the MS Azure AD connector, these troubleshooting steps are recommended:
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).
Check the operation logs for any information written during execution of the operation.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.active.directory" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.