Any update to this ?... I'm seeing this issue now too and I really don't want to go through all my Profiles and change the ' Allow Removal' option (because we have over 700 Profiles across our Organization and around 2000 enrolled devices and the impact of that would be quite significant).
If we have iOS 12.x Users who were previously enrolled and they upgrade to iOS 13,. they seem to be fine. However brand new iOS 13 (never enrolled) seem to be encountering this problem.
Stephen - Yeah,. but Airwatch's ' Best Practice' recommendation has always been to make your Configuration Profiles as granular as possible. So for example, if I want to change Passcode Policy on ONLY the Forestry iPads,. I can do that without effecting anyone else. Or if I want to VPP a new App,. and only push it out to ' StreetSweeper' iPads.. I can do that without effecting anyone else. So yeah.. it's a lot of granularity.. but also offers a lot of precise control. I did open a ticket with Airwatch,. I see now digging into the ' Changes in iOS13' document where this was changed. But I'm not sure that's going to help me on modifying 700 to 800 profiles. (even if they can mass-change those,. the signature will change and mass-redeploy to my environment.. which we cannot do willy-nilly. Would have to be communicated and scheduled to help minimize impact).
EDIT - to be fair,. there's only maybe 5 to 10 Profiles (total) that being changed will directly impact Users (Password prompt popups).. so that # of Profiles is small, but the impact could be big (especially on a week when our Helpdesk is short people). ;/