Organization Owner should not be an individual.

Why This Matters

When an organization owner role in Azure DevOps is assigned to a single individual, it creates a single point of failure and a security risk. If that person leaves the company or their account is compromised, the entire organization could lose administrative control. Spreading ownership across multiple accounts, such as a service account or team, ensures continuity and reduces the blast radius of a credential breach.

What Aether365 Checks

Aether365 verifies whether the organization owner role in your Azure DevOps organization is held by an individual user account. This check appears in your Aether365 dashboard under the microsoft-365 checks category, flagged as a medium severity finding.