Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Enterprise Workloads → Get M365 User Provisioning Report

AI-generated

Overview

This node interacts with the Druva MSP API to retrieve the Microsoft 365 User Provisioning Report under the 'Report - Enterprise Workloads' resource. It allows users to fetch detailed provisioning data for M365 users, which is useful for enterprise administrators to monitor user provisioning activities, audit compliance, and manage user lifecycle events within their organization.

Use Case Examples

  1. An enterprise IT admin wants to generate a report of all M365 user provisioning activities for the previous month to audit new user accounts.
  2. A compliance officer needs to filter M365 provisioning data by specific customers and date ranges to ensure regulatory adherence.

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), used when 'Specific Dates' is selected.
End Date End date for filtering report data (inclusive), used when 'Specific Dates' is selected.
Date Range Predefined relative date range for filtering report data, used when 'Relative Date Range' is selected.
Filter by Customer(s) Whether to filter results by specific customers.
Customer IDs IDs of the customers to filter the report by, applicable if filtering by customers is enabled.
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 - The main JSON output containing the M365 User Provisioning Report data items.

Dependencies

  • Druva MSP API with appropriate API key credentials

Troubleshooting

  • Ensure the API credentials are correctly configured and have permissions to access the 'Report - Enterprise Workloads' resource.
  • If filtering by customers, verify that the customer IDs are valid and accessible by the API key used.
  • Date filters must be valid ISO date strings; invalid dates may cause errors or empty results.
  • If 'Return All' is false and the limit is set too low, the report may not include all desired data.
  • Network or API rate limiting issues may cause request failures; retry or check API usage limits.

Discussion