Actions75
- EndpointAutopilot Actions
- TenantAdministrationAlerts Actions
- EndpointMEM Actions
- TenantGDAP Actions
- TenantAdministrationApplicationApproval Actions
- TenantAdministration Actions
- CIPPSetup Actions
- Security Actions
- IdentityAdministrationDevices Actions
- CIPPExtensions Actions
- EmailExchangeTools Actions
EndpointAutopilot → RemoveAutopilotConfig
AI-generatedOverview
This node operation removes an Autopilot configuration from a specified tenant in the Endpoint Autopilot resource of the CIPP API. It is useful for managing device provisioning configurations by deleting obsolete or unwanted Autopilot profiles from a tenant environment. For example, an IT administrator can use this operation to clean up Autopilot configurations that are no longer needed for device deployment in a specific tenant.
Use Case Examples
- Remove an Autopilot configuration by specifying the tenant filter and the configuration ID to delete it from the tenant's Autopilot settings.
- Use the node to remove an Autopilot configuration by tenant domain and optionally specify assignments or display name for precise targeting.
Properties
| Name | Meaning |
|---|---|
| Tenant Filter | The tenant filter used to specify the target tenant domain for the Autopilot configuration removal. |
| Assignments | Optional assignments related to the Autopilot configuration to be removed. |
| Display Name | Optional display name of the Autopilot configuration to be removed. |
| ID | Optional ID of the Autopilot configuration to be removed. |
Output
JSON
debug- Debug information including actual URL, query parameters, headers, and body sent for the API request (if debug option is enabled).response- The response from the API after attempting to remove the Autopilot configuration.
Dependencies
- An API key credential for authenticating with the CIPP API
Troubleshooting
- Ensure the tenant filter is correctly specified and corresponds to an existing tenant in the system.
- Verify that the ID or other identifying fields for the Autopilot configuration are correct and exist.
- Check API authentication credentials and permissions to ensure the node can perform deletion operations.
- Enable debug mode to get detailed request and response information for troubleshooting.