Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 15:46 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Android ending support for enrolled personal profiles

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

What the notice says

Microsoft’s text, safely structured

Introduction

By the end of March 2026, Microsoft Defender for Android will no longer support protection of personal profiles on enrolled devices. This change aligns with our enterprise-first security strategy, ensuring resources are focused on protecting corporate data while maintaining user privacy.

When will this happen

Rollout will begin in mid-March 2026 and complete by late March 2026.

How this affects your organization

Who is affected: Organizations using Microsoft Defender for Endpoint (MDE) on Android in personal profiles on enrolled devices that are managed through mobile device management (MDM) configuration policies.

What’s changing

We're ending support, monitoring, and feature development for protecting personal profiles on enrolled devices (personal profiles managed via MDM configuration policy). Our main objective is to safeguard corporate assets, with emphasis on identity and data contained within the work profile in enrolled environments. We rely on Android’s platform-level separation to ensure robust isolation. Current research indicates that the likelihood of cross-profile attacks compromising enterprise data remains minimal at present.

Current State

Defender can be enrolled in the personal profile and managed through MDM configuration policies along with controlling work profile configuration (App Configuration policies targeted to managed devices).

Reference link: Deploy Microsoft Defender for Endpoint on Android with Microsoft Intune

New State

Deploying and managing Defender in personal profile on enrolled devices via MDM policies will be retired by the end of March 2026. Defender in work profile on enrolled devices and unenrolled mobile application management (MAM)-enabled devices remains unchanged.

Reference link: Configure Microsoft Defender for Endpoint on Android risk signals using App Protection Policies (MAM)

Benefits of the Change

This update enhances our enterprise-focused strategy by providing more efficient and dependable protection for corporate data. It safeguards user privacy and ensures that Defender exclusively protects corporate assets, maintaining the integrity of personal information in accordance with privacy regulations and platform separation requirements.

What you can do to prepare

  • No action is required from admins or users.
  • These changes will be applied automatically in the back end and will not impact your work profile or unenrolled experience.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 15:46 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current