A specific data loss prevention capability inside Microsoft Defender for Cloud Apps is being retired on a fixed date, and organisations relying on it have a genuine, time-bound migration decision ahead of them rather than an optional consideration. DLP file policies in Defender for Cloud Apps retire on 6 January 2027, and organisations should identify affected customers now and begin planning a transition to Microsoft Purview well ahead of that date.
Why This Retirement Is Easy to Miss
This kind of announcement is precisely the sort of change that gets lost inside a longer list of routine Microsoft product updates, since it affects one specific policy type inside one specific product rather than an entire licence tier or a headline pricing change. There is no dramatic price increase attached to it, no renewal notice forcing immediate attention, and no single visible moment where the retirement becomes impossible to ignore until the actual cutover date arrives and the policies simply stop functioning as configured.
That quietness is exactly why it deserves deliberate attention now, well ahead of January, rather than being left to surface only once security or compliance teams notice that data loss prevention coverage has silently gapped.
What Actually Needs to Move, and Where It Goes
Organisations currently using Defender for Cloud Apps DLP file policies to control how sensitive data moves through cloud application usage need to migrate that specific policy configuration into Microsoft Purview before the retirement date, since Purview is the platform Microsoft has designated as the ongoing home for this capability. Microsoft’s own documentation on Defender for Cloud Apps confirms the platform’s broader role has continued shifting toward unified extended detection and response scenarios, with individual point capabilities like file-based DLP policies increasingly consolidated into purpose-built platforms elsewhere in the Microsoft security portfolio rather than maintained as standalone features indefinitely.
That migration is not a simple like-for-like toggle. Purview’s own data loss prevention framework, while covering broadly similar ground, structures policies, conditions, and enforcement actions differently enough that existing Defender for Cloud Apps configurations need to be reviewed and rebuilt inside Purview’s own policy model, rather than assumed to transfer automatically without any reconfiguration effort.
How This Fits a Broader Microsoft Security Consolidation Pattern
This retirement sits inside a wider pattern of Microsoft folding standalone security capability into unified platforms, a direction visible across several other recent product changes and worth watching for the next capability likely to follow the same path. Microsoft has continued expanding what functionality sits inside Purview specifically, positioning it as the durable home for compliance and data protection capability that previously lived scattered across separate, individually licensed security products, and any organisation with a meaningful investment in a separate, narrower Microsoft security product should treat this pattern as a reasonable signal to ask directly about that product’s own long-term roadmap.
The Licensing Question Worth Confirming Before Migrating
Before beginning the actual policy migration work, it is worth confirming directly whether the organisation’s current Purview licensing already covers the specific data loss prevention capability required to replicate the retiring Defender for Cloud Apps policies. Microsoft’s own Purview licensing documentation sets out data loss prevention as one of several distinct capabilities spanning multiple licensing tiers and standalone add-on components, rather than a single universally included feature, which means the specific entitlement required depends on exactly which Microsoft 365 or Purview plan an organisation currently holds, rather than assuming coverage carries across automatically simply because both products sit under the broader Microsoft security and compliance umbrella.
Purview’s own licensing spans several distinct tiers and add-on components, and an organisation whose existing entitlement was scoped narrowly around a different Purview capability may find it needs to expand that licensing specifically to fully replace the DLP file policy coverage it is about to lose.
Building a Realistic Migration Timeline
Given the January 2027 retirement date, the practical planning window is genuinely narrow once ordinary internal approval and testing cycles are accounted for. A realistic migration timeline should include time to inventory every existing Defender for Cloud Apps DLP file policy currently in production, time to rebuild the equivalent protection inside Purview’s own policy framework, and a genuine testing period confirming the rebuilt policies actually enforce the same protection before the original policies are retired and no longer available as a fallback. Starting that process now, rather than treating January as a distant deadline, is what keeps this transition a planned migration rather than a scramble once the retirement date has already passed.
Conclusion
The retirement of Defender for Cloud Apps DLP file policies on 6 January 2027 is a genuine, dated deadline that requires migrating existing data loss prevention configuration into Microsoft Purview well before that date, and its quiet framing as a routine product update should not be mistaken for a low-priority change.
Confirming existing Purview licensing actually covers the required replacement capability, inventorying every current policy that needs rebuilding, and starting that migration work now rather than waiting for the deadline to approach are the practical steps that keep this transition a deliberate, tested migration rather than a gap in coverage discovered only after the retirement has already taken effect.
