
Intune MAM and MDM policies
I started looking at MAM policies and how they could better protect our company data if we go the BYOD direction. Reading through the documentataion it sounds like I have to pay attention to were I apply the policy either MDM or MAM
Is it possible to have both MDM and MAM policies applied to the same user at the same time, for different devices? For example, if a user could be able to access their work resources from their own MAM-enabled machine, but also come to work and use an Intune MDM-managed device. Are there any caveats to this idea?
If you apply a MAM policy to the user without setting the device state, the user will get the MAM policy on both the BYOD device and the Intune-managed device. You can also apply a MAM policy based on the managed state. So when you create an app protection policy, next to Target to all app types, you’d select No. Then do any of the following:
Apply a less strict MAM policy to Intune managed devices, and apply a more restrictive MAM policy to non MDM-enrolled devices.
Apply an equally strict MAM policy to Intune managed devices as to 3rd party managed devices.
Apply a MAM policy to unenrolled devices only.
https://docs.microsoft.com/en-us/mem/intune/apps/mam-faq
More Stories
Micrsoft Defender for Endpoints
We use Microsoft Defender for endpoints on our physical workstations. I'm now looking at it for our servers. The servers...
Sync Active directory user data with SharePoint
If you want to sync standard common attributes from active directory to sharepoint. Its easy, AD sync to Azure AD...
Microsoft graph API to access sharepoint
Recently I've had to setup a few different app registration using Azure AD to access sharepoint sites. Once you get...
SQL upgrades
We have a few SQL servers that need to be upgraded before they go end of life. We are looking...
How to manage the local administrators group on Azure AD joined devices
After a device is deployed likely using autopilot, sometime you have a need to add an AzureAD user to the...
Azure AD and Windows hello for business, SSO for on-premises resources
We disabled WFB when we first rolled out autopilot because we are not ready to deploy and support passwordless at...