m365_defender: rebrand Microsoft 365 Defender integration to Microsoft Defender XDR

[navnit-elastic]

Proposed commit message

m365_defender: rebrand Microsoft 365 Defender integration to Microsoft Defender XDR

This is a superficial branding update only and does not affect
existing functionalities. The changes include display names, 
reference links, documentation and dashboards to align
with the new brand name.

Note: The dashboard screenshot has not been updated with the latest changes because I don’t have enough data to fully populate the dashboards.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [Microsoft 365 Defender] Rebrand Microsoft 365 Defender integration to Microsoft Defender XDR #14155

Screenshots

Integration Display

Before:

After:

Integration Details
Before:

After:

Integration Assets
Before:

After:

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
99.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b710a6f

History

• 💚 Build #27761 succeeded 85d2b4a

cc @navnit-elastic

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[chrisberkhout]

Looks good.

I've sometimes made manual tweaks in dashboard screenshots to work around the data issue you mentioned, but it's only worth doing if it looks good and still matches reality. In this case I think it's fine to leave it.

[navnit-elastic]

Thanks for confirming @chrisberkhout, Would you mind taking a look at a similar PR for Abnormal Security?
PR Link: #14357

[elastic-vault-github-plugin-prod]

Package m365_defender - 3.11.0 containing this change is available at https://epr.elastic.co/package/m365_defender/3.11.0/