Endpoint sensitivityLabels - Inconsistent sensitivity label properties – displayName is null while name contains the display name

[mscc-sascha]

Describe the bug
When querying sensitivity labels via Microsoft Graph (in Graph Explorer), the returned properties for name and displayName are inconsistent. Specifically, for labels created in Microsoft Purview and published via a policy:

• name contains the human-readable label name (what is shown as Display name in Purview).
• displayName is null.
• id is returned as expected.

This makes it unclear which property is the intended canonical display name and breaks clients relying on displayName.

To Reproduce
Steps to reproduce the behavior:

1. Go to Graph Explorer.
2. Sign in with an account that has access to Microsoft Purview sensitivity labels.
3. Run the following queries:
   • GET https://graph.microsoft.com/v1.0/security/dataSecurityAndGovernance/sensitivityLabels
   • GET https://graph.microsoft.com/v1.0/security/dataSecurityAndGovernance/sensitivityLabels/{sensitivityLabel-id}
4. Observe the response payload: displayName is null while name contains the user-facing label text.

Expected behavior

• displayName should return the label’s display name as configured in Microsoft Purview.
• name should return the label’s technical/unique name (or at least a stable identifier distinct from the display name).
• Both name and displayName should be populated consistently, matching their documented semantics.

Screenshots
Example payload excerpt illustrating the issue:

{
  "id": "0eba62f0-2f7e-4a53-9eea-304c0bc2dac",
  "name": "My Test Label",       // <-- holds the display name
  "displayName": null                 // <-- unexpected null
}