AirPlay restrictions payload doesn't seem to work?

[RobertMorningside]

I am not sure how to describe the issue other than to say I have not been able to get this to work. I am trying to set it as a config profile in my school to prevent student macbooks from airplaying. I believe I have everything set up correctly, and I entered AA:BB:CC:DD:EE:FF into both allow lists, but the test computer that has the config profile can still airplay to other devices. Can you offer any suggestions as to what might be going on?

[RobertMorningside]

I have tried setting a bogus mac address as the only entry in the config profile (AA:BB:CC:DD:EE:FF) as the only entry in both of the allow lists, but that didn't work. I then tried a real mac address from an iPad I have sitting on my desk as the only entry and that also did not work.

I have verified that the config profile is making it to the macbook in question by examining it in system preferences, so I know the config profile is being deployed.

Also, I see that there are two different allow lists and I am not sure of the difference between them!

[homebysix]

I would suggest removing some variables from the equation to see if you can isolate which one is causing the issue. Instead of using the ProfileManifestsMirror JSON schema manifest, try building a config profile manually with the desired payload. Does that work when deployed to your iPads?