14.3.1 Did not fix my issue. But after working with Jamf support we
found that for me, upgrading our jamf connect policy to the most current
version fixed the issue.
We did and was told it's an MDM issue. I have not found this issue on
any of our non enrolled devices. I have seen some others on here say
they have but that has not been my experience and that's all I can go
by.