Knox MSP Portal 25.07 release notes

Profile cloning support for MSPs

Knox MSP Portal 25.07 introduces support for profile cloning operations across Knox Manage, Knox Configure, and Knox Mobile Enrollment. These new endpoints enables Knox MSP partners to programmatically retrieve, copy and overwrite profiles from one fully managed customer to another fully or jointly managed customer account, eliminating the need to recreate profiles manually. The following are the API endpoints available for profile cloning:

• GET /profiles endpoint lets you retrieve profile information from your MSP account based on profile IDs, customer IDs, and other criteria.

• POST /profiles/copy endpoint lets you copy profiles from one fully managed customer to another fully or jointly managed customer account. You can specify new profile names in the request body of the copy operation.

• POST /profiles/overwrite endpoint lets you facilitate propagation of updates from a parent profile to its child profiles, ensuring they reflect the latest changes.

Added support for new scopes

With 25.07, new Knox MSP Portal scopes are introduced to integrate your app with Knox MSP Portal API using Knox OAuth 2.0 Authentication. These scopes enable you to grant granular control over Knox MSP Portal functionality. The newly added scopes include:

• msp - Grants full access permission to manage all Knox MSP Portal functionality.
• msp.profiles – Grants permission to allow copying of existing profiles to managed customers.

You can configure these scopes in the Knox Developer Portal when registering or updating your app. For more information, see Scopes for Knox cloud services APIs.

Knox Manage API now available for MSPs

With this release, the Knox Manage API is now accessible for Knox MSPs. This enables Knox MSPs to programmatically manage Knox Manage features on behalf of their customers. For more information, see Knox Manage API for MSPs.

Parameter type updates

With Knox MSP Portal 25.07, the GET /managedCustomers endpoint has updated parameter type definitions for consistency. The pageNum and pageSize parameters are changed from string to integer types to better align with their usage in pagination. The sortOrder parameter now uses lowercase values—ascending and descending—while still maintaining backward compatibility for legacy values Ascending and Descending.

Back to release notes