[Feature ] Group Microsoft 365

[basile-roux-bib]

Description

This PR adds a new node type called AZGroup365 that represents Microsoft 365 Groups.
A new relationship kind, AZGroup365MemberOf, was also created, but it ultimately appears as the usual MemberOf edge in the graph, as there is no behavioral difference between being a member of a security group or a Microsoft 365 group (note that a Microsoft 365 group can also be a security group).

In the UI, a Group365 is represented with the group icon and the color of a user.

A group that is both a security group and a Microsoft 365 group will appear as a Microsoft 365 group in the UI.

The new node type has been added to the data quality features, which required some changes to the database schema. As a result, a new migration called v7.4.0.sql has been created.

Motivation and Context

Resolves #1359

See the issue for more details about the motivation and implementation.

How Has This Been Tested?

Most of the code was already implemented for security groups and was simply replicated with minimal to no changes. Therefore, it is unlikely that anything was broken by these changes.

It requires changes to Azurehound code due to the addition of two kinds; the pull request for azurehound is also available here

AZGroup365 has been added to existing integration tests, and some new tests were implemented — all of which passed.

Additionally, the final implementation was tested on a complete dataset (~10–15 GB of data), including users, groups, and AZGroup365, without revealing any issues. Pathfinding, queries, and ingestion are working correctly.

Screenshots (optional):

Types of Changes

• New feature (non-breaking change which adds functionality)
• Database migration

Checklist:

• [] I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Feature: Add Microsoft 365 groups to Bloodhound/AzureHound #1359
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up to date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed