Actions75
- EndpointAutopilot Actions
- TenantAdministrationAlerts Actions
- EndpointMEM Actions
- TenantGDAP Actions
- TenantAdministrationApplicationApproval Actions
- TenantAdministration Actions
- CIPPSetup Actions
- Security Actions
- IdentityAdministrationDevices Actions
- CIPPExtensions Actions
- EmailExchangeTools Actions
EndpointAutopilot → ExecSyncAPDevices
AI-generatedOverview
This node interacts with the CIPP API to perform operations related to Endpoint Autopilot devices, specifically the ExecSyncAPDevices operation. It is used to synchronize Autopilot devices for a specified tenant or across all tenants. This is useful in scenarios where device synchronization is required to keep the Autopilot device inventory up to date, such as in IT management and automation workflows for device provisioning and management.
Use Case Examples
- Synchronize Autopilot devices for a specific tenant domain to ensure the device inventory is current.
- Perform a multi-tenant synchronization of Autopilot devices by specifying 'AllTenants' as the tenant filter.
Properties
| Name | Meaning |
|---|---|
| Tenant Filter | Target tenant domain or 'AllTenants' for multi-tenant operations. |
| Options | Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout settings. |
Output
JSON
jsondebug- Debug information including the actual URL, query parameters, headers, and body sent for the API request, if debug mode is enabled.
Dependencies
- An API key credential for authenticating with the CIPP API
Troubleshooting
- Ensure the tenant filter is correctly specified as a valid tenant domain or 'AllTenants'.
- Check API credentials and permissions to access the CIPP API endpoints.
- If debug mode is enabled, review the debug output for request details to diagnose issues.
- Handle rate limiting by configuring batching options to control request frequency.