All of those other items in the profile start with "Allow", so if you want to ensure that those services and options are still allowed on devices that receive your profile, then yes, you should keep them checked. Unchecking any of them would mean that function gets blocked.

Oof course, like anything, test out such a Restrictions profile on one or two devices to see what the effects will be, before you consider rolling it out to your whole fleet of Macs.

Ahhh ok, sorry, so...if i don't have a restrictions profile already in place, then all of these will be allowed anyway, and the default profile has them all ticked to "Allow"

Yeah sorry, was thinking that all wrong.  Appreciate the help

Something to keep in mind about the Restrictions payload (and others). As you surmised, you are acting upon ALL of those settings. You are setting them to either a true state or a false state, but you are setting them.

If you want to specifically target only those keys relating to software update, I feel your path of least resistance is to find or create a JSON schema which allows you to target only those settings surrounding software update without affecting any of the other settings in that preference domain.

This is a JSON schema I found for this - allowing me to target only software update keys and leave all other settings untouched. 

https://github.com/Jamf-Custom-Profile-Schemas/mscottblake-schemas/blob/master/com.apple.applicationaccess.json

Good luck.

I have a profile in my Jamf Pro server that we use for delaying macOS updates. I think the JSON you mentioned here will work better. Thanks for posting this.

Glad to help. 

Also. . .if you want to make your own JSON schemas, Managed App Schema Builder is a godsend. If you know the preference domain, the keys to be acted upon, and the type of value required for those keys (i.e. integer, boolean, etc), you can create your own JSON schemas.

iMazing Profile Editor will allow you to create a profile with only the preferences you want, whereas Jamf Pro requires that you set a bunch of other preferences (which you might already have set elsewhere).

Recommend you sign the profile before uploading to Jamf. A custom schema is also a great way to achieve the same result.

Indeed. I love me some iMazing, but generally prefer to use Jamf's built in UI when I can. I just find it to be cleaner. But as always, YMMV.

I know this is a little late to the party, but please upvote JN-I-27743 which would directly address this issue!