AZDO.1013: Organization Owner should not be an individual.
| ID | AZDO.1013 |
| Severity | High |
| Suite | Mito |
| Product | Azure DevOps |
| Feature | Users and access |
| Security area | Privileged access |
| Resource type | User |
| User impact of fixing | Low |
| Effort to fix | Low |
| MITRE ATT&CK | T1078.004 |
| Reads from | Azure DevOps |
| Further reading | https://learn.microsoft.com/azure/devops/organizations/accounts/change-organization-ownership?view=azure-devops |
What this checks and how to fix it
Section titled “What this checks and how to fix it”Azure DevOps organization owner should not be assigned to a regular user.
Rationale: Owner has full administrative control over the organization, including the ability to manage users, projects, and settings. They can also configure security policies, access levels, and billing information. Ensure that the owner is aware of their responsibilities and has the necessary permissions to effectively manage the organization.
This query will check if the owner has any of the following words as part of their name to conclude that it is not a regular user: (adm|admin|btg|svc|service)
Remediation action
Section titled “Remediation action”Ensure that the owner is not a regular user.
- Sign in to your organization.
- Choose Organization settings.
- Select Overview > Change owner.
- Select an identity from the dropdown menu, or search for an identity by entering the identity’s name, and then select Change.
Related links
Section titled “Related links”Mito check. Author: SebastianClaesson. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.