You can deploy Jamf Trust manually to a small number of unmanaged Windows devices.
This solution is not suitable for large-scale production deployments. Jamf recommends that you use a UEM solution to deploy Jamf Trust to managed devices.
Windows devices that meet the system requirements for the capabilities you plan to activate. Jamf Trust for Windows natively supports devices with x64 or ARM processors.
An activation profile that is compatible with Windows devices and which defines the service capabilities you would like to deploy to your target devices.
To allow users to activate the app by signing in via your organization's identity provider (IdP), identity-based provisioning mus be enabled.
For more information, see Enabling Identity-Based Provisioning with Jamf Security Cloud.
If a Windows app or service with a blocked hostname is added to a device, traffic to the app or service will be blocked but the hosted block page will not be displayed. To enable the page, you must create a custom rule for the new app or service.
The Windows device is enrolled and assigned the service capabilities defined in the activation profile that was used to activate the Jamf Trust app.