The behavior is explained by how Microsoft Purview DLP handles policy and rule renames versus existing records.
In preview, when the display name of a DLP policy or rule is changed in Purview, only new records (new activity explorer events, new alerts, new audit records) will show the updated name. Existing records keep the old name until they age out of the system:
“You can change the display name of DLP policies and rules. Once you rename a policy or a rule, any existing records retain their previous name in activity explorer events, in alerts and in audit records. New records will reflect the new name in activity explorer events, in alerts and in audit records. These names will remain until the items age out of the system.” (Create and deploy data loss prevention policies)
Because DLP alerts are surfaced both in the Purview DLP Alerts dashboard and in the Microsoft Defender portal, this rename behavior applies to what is seen in Defender as well:
- Alerts generated before the rename continue to show the old policy/rule name.
- Alerts generated after the rename show the new policy/rule name.
This can look like “automatic renaming” in the Defender Alerts experience when, in fact, it is the result of a manual rename in Purview combined with the record-retention behavior across the two systems.
There is no indication in the provided documentation of any separate, automatic renaming mechanism that would change policy names only in Defender; the visible change is driven by the Purview-side rename and the fact that existing alert records are immutable with respect to their stored policy name.
References: