Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Enterprise Workloads → Get M365 License Usage Report

AI-generated

Overview

This node interacts with the Druva MSP API to retrieve Microsoft 365 License Usage Reports under the 'Report - Enterprise Workloads' resource. It supports fetching detailed license usage data filtered by date ranges (specific dates, relative date ranges, or no date filter) and optionally filtered by specific customers. The node is useful for enterprises or MSPs managing multiple customers and needing insights into M365 license consumption over various time periods.

Use Case Examples

  1. An MSP wants to generate a report showing M365 license usage for all their customers for the previous month.
  2. A company wants to analyze license usage between two specific dates to optimize their M365 subscriptions.
  3. A user wants to retrieve all license usage data without any date filtering to get a comprehensive overview.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when 'Return All' is false.
Date Selection Method Choose whether to use specific dates, relative date ranges, or include all dates (no date filter).
Start Date Start date for filtering report data (inclusive).
End Date End date for filtering report data (inclusive).
Date Range Select a predefined relative date range for filtering report data.
Filter by Customer(s) Whether to filter results by specific customers.
Customer IDs IDs of the customers to filter the report by.
Wrap Output Items When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times.
Wrapper Property Name The property name to use for the wrapped array of items in the output. Default is 'items'.

Output

JSON

  • json
    • error - Error message if the operation fails for a specific item.

Dependencies

  • Druva MSP API
  • An API key credential for Druva MSP API authentication

Troubleshooting

  • If the node throws an error about the resource not being implemented, ensure the 'resource' parameter is set to 'reportEnterprise'.
  • Errors related to date filtering may occur if startDate is after endDate or if invalid date formats are provided; verify date inputs.
  • If filtering by customers, ensure valid customer IDs are selected; otherwise, the API may return no data or errors.
  • API rate limits or network issues may cause request failures; check API credentials and network connectivity.

Links

Discussion