Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation retrieves the Azure Secure Score data from an Active Directory environment via the Connect Secure API. It is useful for security analysts and IT administrators who want to monitor and assess the security posture of their Azure Active Directory by fetching secure score metrics programmatically. For example, it can be used to automate security reporting or integrate secure score data into dashboards.

Properties

Name Meaning
X USER ID User Id header value required for the API request.
Condition Query condition to filter the secure score results.
Skip Number of records to skip in the result set (pagination).
Limit Maximum number of records to return (pagination limit).
Order By Field(s) to order the results by.

Output

The node outputs JSON data containing the retrieved Azure Secure Score information. The structure corresponds to the API response for secure score data, typically including details such as score values, timestamps, and related metadata. There is no indication that binary data is returned.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API service being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common issues:
    • Missing or invalid user ID header (X USER ID) may cause authentication or authorization errors.
    • Incorrect query conditions or parameters might result in empty or unexpected results.
    • Pagination parameters (skip and limit) must be valid numbers; otherwise, the API may reject the request.
  • Error messages:
    • Authentication failures usually indicate missing or incorrect API credentials.
    • API errors related to query parameters suggest reviewing the syntax and supported fields for filtering and ordering.
  • To resolve these, verify the API key credential, ensure all required headers and parameters are correctly set, and consult the API documentation for valid query formats.

Links and References

Discussion