Defender for Endpoint is now available on Android corporate-owned personally enabled devices


With an increasing number of users choosing to access company resources from mobile devices to improve productivity, organizations are tasked with balancing more employee flexibility with where and how they work while maintaining effective security practices. To do this, organizations are implementing mobile threat defense (MTD) solutions that give IT and security teams greater visibility into the threats directed at their diverse mobile fleet.  

We are excited to announce that Microsoft for Endpoint is now available on Android Enterprise (AE) corporate-owned personally enabled (COPE) devices. This release adds to the already existing support for installation on enrolled devices for AE bring your own device (BYOD) and AE fully managed modes, the legacy Device Administrator mode, and the unenrolled mobile application management (MAM) devices. 

Corporate-owned personally enabled devices are owned by an organization and issued to their employees. Both the enterprise and the employee can install applications onto the device. Cope architecture uses containerization tools like a work profile to maintain separation between personal and work data, and the applications used for each. This provides admins full management control within the work profile while only limited visibility into the personal profile. This practice helps admins continue to enforce policies while maintaining employee privacy.  

This release gives Android Enterprise COPE devices all the capabilities our for Endpoint for Android devices offering has available today including and web protection, malware scanning, protection (preview) and additional breach prevention through integration with Microsoft Endpoint Manager and Conditional Access.

We are excited to share this new release with you. For more details, please refer to the documentation here. We look forward to hearing your feedback. 


This article was originally published by Microsoft's Defender for Endpoint Blog. You can find the original article here.