Corporate vs Personal Device Policies / segregation
Corporate vs Personal Device Policies / segregation - Today you can create policies for Corporate Owned and Personal Owned Devices. But if a user is part of both groups receiving Corporate Owned and Personal Owned Device policies, that user will receive most restrictive policies on his personal device as well. There needs to be a way to do this more effectively where a personal owned device should not be receiving corporate policies.
Is there any updates on this feature we have a requirement of completely segregating policies for users with both Corporate and Personal devices.
The biggest issue here is that everything is promoted to be targeted to users, but there needs to be a distinction between personal and corporate even when assigning to users. Don't really care how its done - whether user based with a filter or to devices targeting a user. This is required for app deployments as well - we want available apps in BYOD which we DO NOT want to be available on corporate. This should be simple enough to do, not sure why it is not already a feature
In addition to policies, this feature should exist for apps as well.
I'd like to make apps "available" to users. Some users have corporate and personal devices and we only want VPP apps to be available for corporate devices. We use a "dynamic device" group and the deviceOwnership attribute to differentiate the user's two devices. However, "dynamic device groups" do not work with Available apps, only Required app.
AirWatch accomplishes this with organizational units, and groups that scoped to devices in these organizational units, and it works very well.