You should be using a Restrictions Profile to block the apps and settings you don’t want the students to have access to.

Using iMazing Profile Editor is my preferred way of creating these, so I can test them on a device before uploading them to the Jamf console.

Thank you for the tip ​@MusicCityMac, but I still have a tough time figuring out how to do this for native apps on macOS 26.xx. Could you point me to the exact place where this type of restriction is configured? 

Are you doing this through the console or using iMazing Profile Editor? 

Tried both.

Ok, I was thinking about this through the wrong lens, that’s my fault, sorry about that.

If you log in to Jamf School and click Computers, do you see Content Management?

If you do, look for Restricted Software, which should be the fourth item down, and click on it. There, you can add apps to block. Click on the New Button in the upper right side of the window and fill out your parameters, Name, Site, Process Name, and what actions you want to happen if the app is launched.

The great thing about using a Restricted Software Record is that you can delete the application in question, send a notification email if the restricted software is launched, and display a message to the user explaining why something is restricted.
 

Also, the apps you mentioned are tied to an Apple Account. You may want to block the use of personal Apple accounts on school-owned devices and only allow Managed Apple Accounts, which you can set up for Faculty, Staff, and Students in Apple Business.

Hope this helps!

Is this something you actually see in your Jamf School setup?!
I see only this, and no mention of what you’re referring to. Are you sure this isn’t a Pro function only?

I don’t have access to Jamf School, and you may be right; it may be a Pro-only function, but I do see that you have a separate category for Apps. Have you checked whether there is a restricted category under there?

Ok. I think what you’re referring to is Pro only. The apps section has no such functionality I’m afraid.

​@atomczynski11 do you use Jamf School, and if you do, could you jump in and offer some advice?

Bumping this. It’s the closest post I’ve found that is looking for the same thing I am. @vegard did you ever find anything else out? Been using Jamf School for a few years and this is something I’ve only skirted around. Currently our Mac Lab is being ran by a teacher who doesn’t have as good control as before, so locking down the computers more is our only real option.

No, I haven’t gotten any information on this yet. I’ll update this post if I get some new information regarding this.

I think I’ve found a way to do this without using the safe/blocklist in Jamf School. 

Under blueprints → Create blueprint → Componets library.

There is a blueprint call “App Settings” that works for mac and IOS 27+ versions, that allows you to mark allowed and denied apps. Try configering this and see if it works.

After some more experimentation, this blueprint does work to blocklist app on both mac and IOS 27+

I’ve written a guide on how to do so.

Apple is depreciating the safe/block list functions for Ipads, Iphone & Mac on OS 27+.

In Jamf school there is now a blueprint to use for safe/block list.

App bundles can be found on the apple Guides Site. URL:

Bundle IDs for iPhone and iPad Apple apps

Blueprint Setup

1. In Jamf school navigate blueprints.

2. Create a new blueprint.

3. In the components library click on “App Settings”

4. Navigate to “Denied binaries” → Add Item.

5. Under “Signing ID” pasted the Bundle ID of the app you wish to block.

6. Update & save.

7. Repeat set 4,5 & 6 for each app.

8. In your blueprint click on scope and add a device group.

9. Save

10. Once everything is done click delpoy. This should push the blueprint to the device similar to a profile.

Editing A Blueprint

1. In Jamf school navigate blueprints.

2. Click on your blueprint

3. Click on the App settings component.

4. Change as needed.

5. Update and save.

6. Deploy.