Revision history [back]

There are a few possible reasons why a newly created permission group in Azure DevOps may not be appearing in the assignment of Repository security:

1. The group may not have been added to the appropriate security namespace.
2. The group may not have the necessary permissions to access the repository security settings.
3. The group may not have been saved properly after creation.
4. The group may not have been added to the project or organization where the repository is located.
5. There may be an issue with the Azure DevOps platform.

To resolve the issue, it is recommended to check the group's permissions, ensure it is saved properly, and verify that it is added to the correct security namespace, project, or organization. If the issue persists, contacting Azure DevOps support may be necessary.