AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves Azure Active Directory (Azure AD) logs for a specified user. It is useful for monitoring and auditing user activities within an organization's Azure AD environment. Typical use cases include security audits, compliance reporting, and troubleshooting user access issues by fetching detailed log entries related to a particular user.

For example, an IT administrator can use this node to pull sign-in logs or audit logs filtered by a specific user ID to investigate suspicious activity or verify access patterns.

Properties

Name Meaning
X USER ID The unique identifier of the user whose Azure AD logs you want to retrieve.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition for logs.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data containing the retrieved Azure AD logs corresponding to the specified user and query parameters. Each item in the output typically represents a single log entry with details such as event type, timestamp, user information, and other relevant metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Azure AD logs service.
  • The node expects proper configuration of the base URL and authentication credentials in n8n to connect to the Azure AD logs API endpoint.

Troubleshooting

  • Missing or invalid User ID: If the "X USER ID" property is empty or incorrect, the API call will fail or return no data. Ensure the user ID is valid and correctly entered.
  • API authentication errors: Errors related to authentication usually indicate missing or invalid API credentials. Verify that the API key or token is correctly configured in n8n.
  • Query parameter issues: Incorrectly formatted or unsupported query conditions may cause the API to reject the request. Validate the syntax and supported fields for the "Condition" parameter.
  • Pagination problems: Using "Skip" and "Limit" incorrectly might result in unexpected subsets of data. Adjust these values carefully to navigate through large datasets.

Links and References

Discussion