{"id":4687,"date":"2020-05-27T10:20:55","date_gmt":"2020-05-27T10:20:55","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=4687"},"modified":"2020-05-27T10:20:55","modified_gmt":"2020-05-27T10:20:55","slug":"file-ownership-not-showing-up-after-enabling-mam-policy","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/intune\/file-ownership-not-showing-up-after-enabling-mam-policy","title":{"rendered":"“File Ownership” not showing up after enabling MAM policy"},"content":{"rendered":"

Recently working on a Proof Of Concept enabling a MAM policy to lockdown and protect an application (Teams) on a device that not enrolled in Intune, and the File Ownership prompt in guides was not appearing.<\/p>

The Intune License was applied to the user and the user was enabled for\u00a0 MAM User Scope , and the MAM policy was applied to the User\u00a0\u00a0<\/p>

\"\"<\/p>

However no file ownership still and no encryption of files. Turns out the device has to be joined to the companys Azure AD ( or Local AD and Hybrid ) for this to happen and display the info box<\/p>

\"\"<\/p>

This will show you its enrolled in MAM ( not MDM )\u00a0<\/p>

\"\"<\/p>

After this File Ownership is displayed !<\/p>

\"\"<\/p>","protected":false},"excerpt":{"rendered":"

Recently working on a Proof Of Concept enabling a MAM policy to lockdown and protect an application (Teams) on a device that not enrolled in Intune, and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2836],"tags":[2375,3278,3279,1410,3280],"class_list":["post-4687","post","type-post","status-publish","format-standard","hentry","category-intune","tag-azure-ad","tag-file-ownership","tag-mam","tag-policy","tag-wip"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t