Actions79
- Admin Actions
- Alert Summary Actions
- Backup Health Summary Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Enterprise Workloads Actions
- Get Alert History Report
- Get Backup Activity Report
- Get DR Failback Activity Report
- Get DR Failover Activity Report
- Get DR Replication Activity Report
- Get Resource Status Report
- Get Storage Consumption by BackupSets Report
- Get Google Alerts Report
- Get Google License Usage Report
- Get Google Preserved Users Datasources Report
- Get Google Shared Drive Backup Activity Report
- Get Google Shared Drive Restore Activity Report
- Get Google Storage Consumption Report
- Get Google User Count and Status Report
- Get Google User Last Backup Status Report
- Get Google User Provisioning Report
- Get Google User Restore Activity Report
- Get Google User Workload Report
- Get M365 Alerts Report
- Get M365 Groups Backup Activity Report
- Get M365 Groups Discovery Report
- Get M365 License Usage Report
- Get M365 Preserved Users Datasources Report
- Get M365 Public Folder Backup Activity Report
- Get M365 SharePoint Backup Activity Report
- Get M365 SharePoint Site Discovery Report
- Get M365 Storage Consumption Report
- Get M365 Teams Backup Activity Report
- Get M365 Teams Discovery Report
- Get M365 User Count and Status Report
- Get M365 User Last Backup Status Report
- Get M365 User Provisioning Report
- Get M365 User Restore Activity Report
- Get M365 User Workload Report
- Report - Usage Actions
- Service Plan Actions
- Storage Region Actions
- Task Actions
- Tenant Actions
- Tenant Config - Enterprise Workloads Actions
- Tenant Config - inSync Actions
Report - Enterprise Workloads → Get M365 Teams Discovery Report
AI-generatedOverview
This node interacts with the Druva MSP API to retrieve the M365 Teams Discovery Report under the 'Report - Enterprise Workloads' resource. It supports fetching detailed reports about Microsoft 365 Teams usage and discovery data, which is useful for enterprise workload management and monitoring. Typical use cases include generating reports for compliance, auditing, or operational insights into Teams usage across an organization.
Use Case Examples
- An IT administrator uses this node to pull the latest M365 Teams Discovery Report for a specific date range to analyze team collaboration patterns.
- A managed service provider automates the retrieval of Teams discovery data for multiple customers to monitor usage and optimize resource allocation.
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, used when 'Filter by Customer(s)' is true. |
| 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 Teams Discovery Report data.
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 the node returns an error about the resource not being implemented, verify that the resource and operation names are correctly set.
- When using date filters, ensure the date formats are valid and the start date is not after the end date.
- If filtering by customers, confirm that the customer IDs are valid and accessible by the API credentials.