Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, "Retrieve Azure Licenses" under the "Active Directory" resource, is designed to fetch information about Azure licenses assigned to users in an Active Directory environment. It allows querying license data with various filters and pagination controls, making it useful for administrators who need to audit or report on user license assignments.

Common scenarios include:

  • Auditing which Azure licenses are assigned to a specific user.
  • Generating reports on license usage across an organization.
  • Filtering license data based on custom conditions or sorting preferences.

For example, an admin could retrieve all licenses assigned to a user by specifying their User ID, optionally filtering results with a condition, and limiting the number of records returned.

Properties

Name Meaning
X USER ID The unique identifier of the user whose Azure licenses you want to retrieve.
Condition A query condition string to filter the license data (e.g., filter by license type).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of license records to return.
Order By Field name(s) to order the results by (e.g., license name, assignment date).

Output

The node outputs JSON data containing the retrieved Azure license information for the specified user. Each item in the output typically represents a license record with details such as license type, status, assignment dates, and other relevant metadata.

If binary data were involved (e.g., license documents), it would be included in a separate binary property, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API that interfaces with Active Directory.
  • The node depends on the external Connect Secure API service to fetch license data.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid User ID: The operation requires a valid User ID; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Query syntax issues: If using the Condition property, ensure the query string is valid according to the API's expected format.
  • Pagination parameters: Incorrect use of Skip and Limit may result in empty or incomplete data sets.
  • Order By field errors: Using unsupported fields in Order By can cause errors; check available sortable fields in the API documentation.

Links and References

Discussion