Using Baseline via Mosyle
Baseline is a zsh script, and due to limitations of Mosyle running all scripts through bash, it is recommended to use the PKG or find some way to deliver the script locally to the device.
Unfortunately, the Mosyle "Install PKG" profile is not compatible with Baseline, due to limitations of the Mosyle platform. The Mosyle "Install PKG" profile can only reliably install and report on packages which contain a single Bundle Identifier, and Baseline does not include one. For that reason, it is recommended to either use a signed/notarized version of the Baseline pkg (all releases on this github are signed and notarized) or use a Custom Command script to download and install a Baseline pkg.
Upload the mobileconfig file to Mosyle using the "Custom Certificates/Profiles" feature and assign accordingly for your use case.
In order for Baseline to work in a "zero touch" context with Mosyle, a signed/notarized version of the Baseline pkg (including the LaunchDaemon) should be uploaded to your Automated Deployment Profile so that it is installed via MDM protocol Install Enterprise App immediately upon enrollment.
A configuration profile should be assigned in a way that it is delivered to the device immediately and automatically upon enrollment.
If you would like to initiate Baseline via Self-Service or by "pushing" the program from the admin console, a scripted installation of the pkg is recommended. If you use the provided LaunchDaemon, Baseline will start immediately upon installation.
For scripted installation of the PKG, you can see an example here: https://github.com/SecondSonConsulting/macOS-Scripts/blob/main/installGenericPKG.sh
You can host the PKG yourself on the Mosyle CDN (or any URL of your choosing) or download directly from Github (not generally recommended).
Alternately, you can deliver the Baseline script/assets via a custom package, and then use a Mosyle Custom Command to initiate it like this:
/usr/local/Baseline/Baseline.sh