Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation allows users to retrieve Azure Active Directory (Azure AD) logs. It is useful for scenarios where monitoring, auditing, or analyzing user activities and system events within an Azure AD environment is required. For example, security teams can use this node to fetch logs related to user sign-ins, changes in directory roles, or other administrative actions to ensure compliance and detect suspicious activities.

Properties

Name Meaning
X USER ID The User Id header value to identify the user making the request.
Condition A query condition string to filter the logs based on specific criteria.
Skip Number of records to skip in the result set, useful for pagination.
Limit Maximum number of log records to return.
Order By Field name(s) to order the results by, e.g., timestamp or event type.

Output

The output consists of JSON data representing the retrieved Azure AD logs. Each item in the output corresponds to a log entry matching the specified query parameters. The structure typically includes details such as event timestamps, user information, event types, and other relevant metadata from Azure AD logs.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Azure Active Directory service.
  • The node depends on the Azure AD API endpoint that provides access to audit and sign-in logs.
  • Proper configuration of authentication credentials in n8n is necessary to successfully call the API.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the "X USER ID" property is provided and correctly set; it is required for the request.
  • API authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to read Azure AD logs.
  • Query syntax issues: If using the "Condition" property to filter logs, ensure the query string follows the expected syntax supported by the Azure AD logs API.
  • Pagination problems: When using "Skip" and "Limit", confirm values are non-negative integers and within allowed ranges to avoid empty or incomplete results.
  • Order By field errors: Use valid field names recognized by the Azure AD logs API to prevent ordering failures.

Links and References

Discussion