Owner is included in PCA group

Author: chcomley

Diff for: docs/marketplace/get-tfs-extensions.md

@@ -21,7 +21,7 @@ To add new features and capabilities to your Azure DevOps Server, install extens
 
 ## Prerequisites
 
-- To install an extension, you must be a member of the **Project Collection Administrators** group or have **Edit collection-level information** permissions. For more information, see [Change project collection-level permissions](../organizations/security/change-organization-collection-level-permissions.md).  
+- To install an extension, you must be a member of the **Project Collection Administrators** group or have **Edit collection-level information** permissions. Organization owners are automatically members of this group. For more information, see [Change project collection-level permissions](../organizations/security/change-organization-collection-level-permissions.md).  
 - If you don't have permissions, you can [request extensions](request-extensions.md) instead.
 
 > [!NOTE]

Diff for: docs/marketplace/install-extension.md

@@ -20,7 +20,7 @@ To learn about building your own Azure DevOps extensions, see [developing](../ex
 
 ## Prerequisites
 
-* Only [Project Collection Administrators or organization owners](faq-extensions.yml) can install extensions. If you don't have permissions, you can [request extensions](./request-extensions.md) instead.
+* Only [Project Collection Administrators](faq-extensions.yml) can install extensions. Organization owners are automatically members of this group. If you don't have permissions, you can [request extensions](./request-extensions.md) instead.
 * Private extensions must be shared with your organization to be installed. Check out the [publishing documentation](../extend/publish/overview.md#upload) for information on how to share private extensions.
 
 <a id="install-extension" /> 

Diff for: docs/marketplace/overview.md

@@ -44,7 +44,7 @@ You can quickly add extensions to your organization by doing the following steps
 1. Search and find extensions for your organization in the [Marketplace > Azure DevOps](https://marketplace.visualstudio.com/azuredevops).
 2. Install the extension from the Marketplace and start using it in Azure DevOps.
 
-To upload, install, or assign extensions you need [Project Collection Administrator or organization owner permissions](./faq-extensions.yml).
+To upload, install, or assign extensions you must be a member of the [Project Collection Administrators group](../organizations/security/change-organization-collection-level-permissions.md). Organization owners are automatically members of this group.
 
 #### [Azure DevOps CLI](#tab/azure-devops-cli/)
 

Diff for: docs/migrate/migration-import.md

@@ -18,7 +18,7 @@ ms.date: 08/18/2022
 This article walks you through the preparation that's required to get an import to Azure DevOps Services ready to run. If you encounter errors during the process, see [Troubleshoot import and migration errors](migration-troubleshooting.md).
 
 
-> [!Note]
+> [!NOTE]
 > * Visual Studio Team Services (VSTS) is now [Azure DevOps Services.](../user-guide/about-azure-devops-services-tfs.md#visual-studio-team-services-is-now-azure-devops-services)
 > * With the release of Azure DevOps Server 2019, the TFS Database Import Service has been rebranded as the data migration tool for Azure DevOps. This change includes TfsMigrator (Migrator) becoming the data migration tool. This service works exactly the same as the former import service. If you're running an older version of on-premises Azure DevOps Server with the TFS branding, you can still use this feature to migrate to Azure DevOps as long as you've upgraded to one of the supported server versions.
 > * Before you begin the import tasks, check to ensure that you're running a [supported version of Azure DevOps Server](migration-overview.md#supported-azure-devops-server-versions-for-import). 

Diff for: docs/organizations/accounts/add-privacy-policy-url.md

@@ -21,7 +21,7 @@ A privacy policy is a legal requirement for all websites and apps that collect o
 
 ## Prerequisites
 
-You must be [an organization owner](../security/look-up-organization-owner.md) or [a member of the Project Collection Administrators group](../security/look-up-project-collection-administrators.md) to add a privacy policy URL.
+You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 ## Add your privacy policy URL in Azure DevOps
 

Diff for: docs/organizations/accounts/change-application-access-policies.md

@@ -20,8 +20,7 @@ Learn how to manage your organization's security policies that determine how app
 
 ## Prerequisites
 
-To change a policy, you need at least Basic access and organization owner or Project Collection Administrator permissions.
-[How do I find the organization owner?](/azure/devops/organizations/security/request-changes-permissions)
+You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 [!INCLUDE [manage-policies](../../includes/manage-policies.md)]
 

Diff for: docs/organizations/accounts/change-organization-ownership.md

@@ -23,7 +23,7 @@ As roles and responsibilities change, you can change the owner for your organiza
 
 ## Prerequisites
 
-You must be a [member of the **Project Collection Administrators** group](../security/look-up-project-collection-administrators.md) or the [**organization owner**](../security/look-up-organization-owner.md). If no one in the organization has these permissions, contact [Azure DevOps Support](https://developercommunity.visualstudio.com/spaces/21/index.html). Make sure the owner has completed the following tasks:
+You must be a [member of the **Project Collection Administrators** group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group. If no one in the organization has these permissions, contact [Azure DevOps Support](https://developercommunity.visualstudio.com/spaces/21/index.html). Make sure the owner has completed the following tasks:
 
 - Sign in to your organization, create a profile, and agree to the Terms of Service
 - Access the organization at least once after creating your initial profile

Diff for: docs/organizations/accounts/disable-request-access-policy.md

@@ -22,8 +22,7 @@ When this policy is on, users can request access to a resource. A request result
 
 ## Prerequisites
 
-To change a policy, you need at least Basic access and organization owner or Project Collection Administrator permissions.
-[How do I find the organization owner?](../security/look-up-organization-owner.md)
+You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md) and have at least Basic access. Organization owners are automatically members of this group.
 
 ## Disable Request Access policy
 

Diff for: docs/organizations/accounts/manage-azure-active-directory-groups.md

@@ -29,7 +29,7 @@ and differences in how you [control organization access with Microsoft accounts
 ## Prerequisites
 
 * Your organization must be connected to Azure Active Directory. [My organization uses Microsoft accounts only. Can I switch to Azure AD?](faq-azure-access.yml#ChangeMSA). Learn how to [connect your organization to Azure AD](connect-organization-to-azure-ad.md).
-* You must be a Project Administrator, Project Collection Administrator, or organization owner. You must also have at least Basic access, not Stakeholder.
+* You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group. You must also have at least Basic access, not Stakeholder.
 * To create and manage Azure AD groups, you need Azure AD administrator permissions or have the directory administrator delegate those permissions to you in the [Azure portal](https://portal.azure.com).
 * Azure AD changes might take up to 1 hour to be visible in Azure DevOps.
 

Diff for: docs/organizations/audit/auditing-streaming.md

@@ -56,7 +56,7 @@ These permissions can be given to any users or groups you wish to have manage yo
    ![Select Auditing in Organization settings](media/auditing-streaming/select-auditing-organization-settings.png)
 
 > [!NOTE]
-> If you don't see *Auditing* in Organization Settings, then auditing is not currently enabled for your organization. Someone in the Organization owner or Project Collection Administrators (PCAs) group must [enable Auditing](azure-devops-auditing.md#enable-and-disable-auditing) in Organization Policies. You will then be able to see events on the Auditing page if you have the appropriate permissions.
+> If you don't see *Auditing* in Organization Settings, then auditing is not currently enabled for your organization. Someone in the organization owner or Project Collection Administrators (PCAs) group must [enable Auditing](azure-devops-auditing.md#enable-and-disable-auditing) in Organization Policies. You will then be able to see events on the Auditing page if you have the appropriate permissions.
 
 4. Go to the **Streams** tab, and then select **New stream**. 
 

Diff for: docs/organizations/audit/azure-devops-auditing.md

@@ -42,12 +42,12 @@ Auditing events can be accessed through two methods on the Auditing page in your
 
 ## Prerequisites
 
-Auditing is turned off by default for all Azure DevOps Services organizations and can be [toggled on and off](#enable-and-disable-auditing) by Organization owners and Project Collection Administrators in the *Organization Settings* page.
+Auditing is turned off by default for all Azure DevOps Services organizations and can be [toggled on and off](#enable-and-disable-auditing) by organization Owners and Project Collection Administrators in the *Organization Settings* page.
 By default, Project Collection Administrators are the only group that has full access to the Auditing feature.
 
 ### Audit permissions
 
-- By default, members of the **Organization owners** and **Project Collection Administrators** groups have full access to all Auditing features.
+- By default, members of the **organization Owners** and **Project Collection Administrators** groups have full access to all Auditing features.
 - Specific Audit permissions can be granted to any group via the Security Permissions page in Organization Settings. 
 
 > [!NOTE]  

Diff for: docs/organizations/billing/buy-basic-access-add-users.md

@@ -30,8 +30,8 @@ Visual Studio subscribers get access included with their subscription, and their
 
 Ensure you have the following items in place:
 
-* [Licensing is set up for your organization via Azure](https://azure.microsoft.com/pricing/details/devops/server/)
-* You have permissions allocated as [an organization Owner](../security/look-up-organization-owner.md) or [a member of the Project Collection Administrators group](../security/look-up-project-collection-administrators.md)
+* You must have [licensing set up for your organization via Azure](https://azure.microsoft.com/pricing/details/devops/server/)
+* You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 ## Pay via Azure
 

Diff for: docs/organizations/billing/change-azure-subscription.md

@@ -24,7 +24,7 @@ Learn how to change the Azure subscription that your Azure DevOps organization u
 
 To change or remove your billing subscription, you need the following permissions:
 
-- [Organization owner](../security/look-up-organization-owner.md) permissions or be a member of the [**Project Collection Administrators** group](../security/change-organization-collection-level-permissions.md).  
+- [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 - [Owner or Contributor permission for an Azure subscription](add-backup-billing-managers.md), which you can use to purchase.
 
 <a id="change-subscription" />

Diff for: docs/organizations/billing/set-up-billing-for-your-organization-vs.md

@@ -25,7 +25,7 @@ Set up billing in Azure DevOps before you make purchases, so it's already in pla
 ## Prerequisites
 
 * If you don't have an Azure subscription, [create one](https://azure.microsoft.com/pricing/purchase-options/) now.
-* To set up billing, you must be a member of the [**Project Collection Administrators** group](../security/look-up-project-collection-administrators.md) or be an [**organization Owner**](../security/look-up-organization-owner.md).
+* You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 > [!NOTE]
 > The [Azure Free Trial](https://azure.microsoft.com/offers/ms-azr-0044p/) isn't supported.

Diff for: docs/organizations/billing/try-additional-features-vs.md

@@ -22,7 +22,7 @@ Basic users have full access to Azure Test Plans during the 30-day trial. After
 
 ## Prerequisites
 
-To try Azure Test Plans, you must be the [**organization Owner**](../security/look-up-organization-owner.md) or a member of the [**Project Collection Administrators** group](../security/look-up-project-collection-administrators.md) group. If you created the organization or collection, you're automatically a member of this group.
+You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 ## Try Azure Test Plans
 

Diff for: docs/organizations/projects/delete-project.md

@@ -18,20 +18,20 @@ ms.date: 08/16/2021
 
 If you have a project that's no longer valid, you can delete it from your organization or collection in Azure DevOps. Or, if you are migrating from an on-premises Azure DevOps Server to Azure DevOps Services, you'll need to delete project(s). Deleting projects also helps to simplify navigating to only those projects that are in use. 
 
-> [!Caution]
+> [!CAUTION]
 > Deleting projects from the web portal generate a soft-delete where projects get permanently deleted if not restored within 28 days. Projects deleted from the on-premises Azure DevOps Administration Console undergo a hard delete and cannot be restored. For more information on restoring projects, see [Restore a project](restore-project.md). If you want to access project data while the project is deleted (without [restoring it](restore-project.md)) you should [save project data](save-project-data.md).
 
 ## Prerequisites
 
 ::: moniker range="azure-devops" 
 
-- You must be a member of the **Project Administrators** group or have the project-level **Delete team project** permission set to **Allow**. For more information, see  [Change project-level permissions](../security/change-project-level-permissions.md).
+- You must be a member of the **Project Administrators** group or have the project-level **Delete team project** permission set to **Allow**. Organization owners are automatically members of this group. For more information, see  [Change project-level permissions](../security/change-project-level-permissions.md).
 
 ::: moniker-end
 
 ::: moniker range=" < azure-devops"  
 
-- You must be a member of the **Project Administrators** group or have the **Delete team project** permission set to **Allow**. For more information, see  [Change project-level permissions](../security/change-project-level-permissions.md).
+- You must be a member of the **Project Administrators** group or have the **Delete team project** permission set to **Allow**. For more information, see [Change project-level permissions](../security/change-project-level-permissions.md).
 
 ::: moniker-end  
 

Diff for: docs/organizations/projects/restore-project.md

@@ -22,9 +22,9 @@ Sometimes we might delete a project in Azure DevOps by mistake. You can restore
 
 ::: moniker range="azure-devops"
 
-To restore a project, you must have Project Collection Administrator or organization owner permissions in Azure DevOps.
+* You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
-You must also have the "delete project" permission set to **Allow**. To learn how to check your permissions, see [View permissions](../security/view-permissions.md).
+* You must also have the "delete project" permission set to **Allow**. To learn how to check your permissions, see [View permissions](../security/view-permissions.md).
 
 ::: moniker-end
 

Diff for: docs/organizations/public/make-project-public.md

@@ -26,7 +26,7 @@ You can easily switch a private project to a public project, and vice-versa.  Be
 ## Prerequisites
 
 - You must have an organization created in Azure DevOps. If you don't have one, [do that now](../../user-guide/sign-up-invite-teammates.md).
-- As an organization owner, you can change policies and change project information. If you're not the owner, then you must be a member of the [**Project Collection Administrators** group](../security/change-organization-collection-level-permissions.md).
+- You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 ## Enable anonymous access to projects for your organization
 

Diff for: docs/organizations/security/restrict-invitations.md

@@ -30,7 +30,7 @@ can add users who are already in the organization to their team       |
 
 ## Prerequisites
 
-- You must be a member of the **Project Collection Administrator** group to manage this policy. To get added, see [Change project collection-level permissions](change-organization-collection-level-permissions.md). 
+You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
 
 ## Turn off policy
 

Diff for: docs/user-guide/roles.md

@@ -134,6 +134,7 @@ Responsible for configuring project-level resources, including:
 
 ### Organization owners and Project Collection Administrators
 
+Organization owners are automatically members of the Project Collection Administrators group.
 Responsible for configuring organization-level resources, including the following tasks:
 
 - Manage billing