Merge pull request #10637 from MicrosoftDocs/main638761466316183772sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/ide/deploy-copilot-to-enterprise.md

@@ -1,7 +1,7 @@
 ---
 title: Deploy GitHub Copilot within your enterprise
 description: Configure and deploy GitHub Copilot programmatically to existing Visual Studio instances on a client's machine within an enterprise.
-ms.date: 7/15/2024
+ms.date: 2/25/2025
 ms.topic: conceptual
 author: anandmeg
 ms.author: meghaanand
@@ -13,28 +13,29 @@ ms.custom: ai-learning-hub
 ---
 # Deploy GitHub Copilot to existing Visual Studio instances
 
-Administrators of Visual Studio 2022 version 17.8 or above can deploy GitHub Copilot onto client workstations programmatically with an installation script, just like you deploy other [Visual Studio components](../install/workload-and-component-ids.md). 
+Administrators of Visual Studio 2022 version 17.8 or above can deploy GitHub Copilot to client workstations programmatically using an installation script, similar to deploying other [Visual Studio components](../install/workload-and-component-ids.md). 
 
-This method does NOT install the GitHub Copilot chat extension.
+This method does NOT install the GitHub Copilot Chat extension.
 
 ## Prerequisites
 
 To get started, you need:
 
-- This section assumes that Visual Studio 2022 [version 17.8 or later](/visualstudio/releases/2022/release-history) is already installed on the client machines. If it's not, refer to the guidance in the [Visual Studio Administrators Guide](https://aka.ms/vs/admin/guide) for how to deploy Visual Studio throughout your organization.
-- A valid and active GitHub Copilot for Business subscription is required for the end user whose Visual Studio 2022 instance you're installing the GitHub Copilot component for. 
-[See: Managing access for GitHub Copilot for Business in your organization.](https://docs.github.com/en/copilot/managing-copilot-business/managing-access-for-copilot-business-in-your-organization)
+- Visual Studio 2022 [version 17.8 or later](/visualstudio/releases/2022/release-history) installed on the client machines.
+  Refer to the [Visual Studio Administrators Guide](https://aka.ms/vs/admin/guide) for deployment guidance.
+- A valid and active GitHub Copilot for Business subscription for the end user installing the GitHub Copilot component in Visual Studio. 
+  [Learn more: Managing access for GitHub Copilot for Business in your organization.](https://docs.github.com/en/copilot/managing-copilot-business/managing-access-for-copilot-business-in-your-organization)
 
-Options for deploying GitHub Copilot onto client machines depend on how Visual Studio is currently installed on these machines.
+Options for deploying GitHub Copilot depend on how Visual Studio is currently installed on client machines.
 
 ## Modify an existing installation to add the GitHub Copilot component
 
-Most of the time, users would either acquire Visual Studio themselves, or run a development environment setup script on their machine.
-To add the GitHub Copilot component to an existing installation of Visual Studio, use the installer's `modify` command from either a command line or PowerShell window.
+In most cases, users either install Visual Studio themselves, or set it up using a development environment setup script on their machine.
+To add the GitHub Copilot component to an existing Visual Studio installation, use the installer's `modify` command from either a Command Prompt or PowerShell window.
 
-### Sample install instructions
+### Sample installation instructions
 
-Make sure you're in the Visual Studio Installer directory in the command line or PowerShell window: `C:\Program Files (x86)\Microsoft Visual Studio\Installer`
+Ensure you're in the Visual Studio Installer directory (`C:\Program Files (x86)\Microsoft Visual Studio\Installer`) before running the command.
 
 ```
 $installDir = .\vswhere.exe -products * -version 17.8 -requires Microsoft.VisualStudio.Component.CoreEditor -property installationPath
@@ -46,23 +47,27 @@ foreach ($i in $installDir) {
 
 ## Deploy using a layout
 
-If you're using a layout to deploy Visual Studio across your organization, you first need to add the `Component.GitHub.Copilot` component to the layout.  Then, assuming the client is configured to [receive updates from the layout](../install/update-visual-studio.md#configure-source-location-of-updates), you can run a `modify` command as in the previous example to add it to the client.
+If you're using a layout to deploy Visual Studio across your organization, follow these steps:
 
-For more information, see the [layout documentation](../install/create-a-network-installation-of-visual-studio.md#modify-the-contents-of-a-layout). 
+1. Add the `Component.GitHub.Copilot` component to the layout.
+1. Ensure the client is configured to [receive updates from the layout](../install/update-visual-studio.md#configure-source-location-of-updates)
+1. Run a `modify` command (as shown in the previous example) to install GitHub Copilot on the client machine.
+
+For more information, refer to the [layout documentation](../install/create-a-network-installation-of-visual-studio.md#modify-the-contents-of-a-layout). 
 
 ## End user action required
 
-After installing the GitHub Copilot component to the client machines, the end user will need to take the following steps to enable GitHub Copilot:
+After installing the GitHub Copilot component on client machines, the end user must complete the following steps to enable GitHub Copilot:
 
-1. Log into the [GitHub web interface](https://github.com/settings/copilot) with the GitHub account associated with their Copilot subscription.
+1. Log in to the [GitHub web interface](https://github.com/settings/copilot) using the GitHub account associated with their Copilot subscription.
 1. Activate access by launching Visual Studio 2022 and [adding their GitHub account to the Visual Studio keychain](work-with-github-accounts.md).
 
 ## Related content
 
 To learn more, consider exploring the following resources:
 
-- [GitHub Copilot extension: Getting started](visual-studio-github-copilot-extension.md)
-- [GitHub Copilot Chat extension: Getting started](visual-studio-github-copilot-chat.md)
-- [GitHub Copilot: Compare plans](https://github.com/features/copilot)
+- [GitHub Copilot Completions: Getting started](visual-studio-github-copilot-extension.md)
+- [GitHub Copilot Chat: Getting started](visual-studio-github-copilot-chat.md)
+- [GitHub Copilot: Compare plans](https://github.com/features/copilot/plans)
 - [GitHub Copilot Trust Center](https://resources.github.com/copilot-trust-center/)
-- [Use command-line parameters to install, update, and manage Visual Studio](../install/use-command-line-parameters-to-install-visual-studio.md)
+- [Use command-line parameters to install, update, and manage Visual Studio](../install/use-command-line-parameters-to-install-visual-studio.md)

docs/ide/managing-project-and-solution-properties.md

@@ -1,7 +1,7 @@
 ---
 title: Manage project and solution properties
 description: Manage both the project properties and the solution properties in Visual Studio for C#, Visual Basic, F#, C++, and JavaScript projects.
-ms.date: 09/10/2024
+ms.date: 02/25/2025
 ms.topic: conceptual
 author: anandmeg
 ms.author: meghaanand
@@ -15,6 +15,8 @@ Projects have properties that govern many aspects of compilation, debugging, tes
 
 You access project properties by right-clicking the [project node](use-solution-explorer.md#solution-explorer-ui) in **Solution Explorer** and selecting **Properties**, or by typing **properties** into the search box on the menu bar and selecting **Properties Window** from the results.
 
+Most project properties are not dependent on the configuration or the platform, but some are. Learn more about [setting properties based on configurations](how-to-create-and-edit-configurations.md#set-properties-based-on-configurations).
+
 ::: moniker range="vs-2022"
 
 :::image type="content" source="media/vs-2022/properties-from-solution-explorer-context-menu.png" alt-text="Screenshot of the Solution Explorer context menu with the Properties option highlighted.":::
@@ -105,3 +107,6 @@ Solution properties are stored in a Solution User Options (*.suo*) file. For mor
 ## Related content
 
 - [What are solutions and projects in Visual Studio?](../ide/solutions-and-projects-in-visual-studio.md)
+- [MSBuild Properties](../msbuild/msbuild-properties.md)
+- [Use properties to control build settings](../msbuild/how-to-build-the-same-source-files-with-different-options.md#use-properties-to-control-build-settings)
+- [Understand build configurations](understanding-build-configurations.md)

docs/ide/visual-studio-github-copilot-admin.md

@@ -1,7 +1,7 @@
 ---
 title: Admin controls for GitHub Copilot in Visual Studio
 description: Learn about the new features for administrators in GitHub Copilot for Visual Studio that enable admins to manage Copilot effectively. 
-ms.date: 9/12/2024
+ms.date: 2/25/2025
 ms.topic: how-to 
 author: anandmeg
 ms.author: meghaanand
@@ -14,47 +14,51 @@ ms.custom: ai-learning-hub
 
 # Admin controls for GitHub Copilot
 
-Visual Studio 2022 introduces new features for administrators to configure and manage GitHub Copilot for their enterprise effectively. These features provide administrators greater control over the use of Copilot within their organization. Admins can disable Copilot for individual accounts or disable it altogether, and configure content exclusion to prevent certain files from being available to Copilot in Visual Studio.
+Visual Studio 2022 introduces new features that enable administrators to configure and manage GitHub Copilot more effectively within their enterprise. These features provide administrators greater control over the use of Copilot within their organization. Admins can disable Copilot for individual accounts, disable it entirely, and configure content exclusion to prevent certain files from being available to Copilot in Visual Studio.
 
 In this article, you learn how to:
-- [Disable Copilot](#disabling-copilot-for-individual-enterprise-visual-studio-accounts)
+- [Disable Copilot](#disabling-copilot-skus)
 - [Configure content exclusion](#configure-content-exclusion)
 
-## Disabling Copilot for individual Enterprise Visual Studio accounts
+## Disabling Copilot SKUs
 
-With Visual Studio version 17.10, project administrators can disable Copilot for individual accounts or disable Copilot altogether via the [Visual Studio Administrative Templates (ADMX/ADML)](https://www.microsoft.com/en-us/download/details.aspx?id=104405), ensuring that your repository is protected.
+With Visual Studio 2022 version 17.10 or later, project administrators can disable Copilot for individual accounts or disable it entirely using the [Visual Studio Administrative Templates (ADMX/ADML)](https://www.microsoft.com/en-us/download/details.aspx?id=104405). This helps ensure that your repository remains protected.
 
-To configure and deploy these policies, you can use [Microsoft Intune](../install/administrative-templates.md#deploying-the-policies) or the [Local Group Policy Editor](#configure-copilot-group-policy) directly on the client machine.
+With Visual Studio 2022 version 17.13 or later, you can disable Copilot Free. 
+
+To configure and deploy these policies, you can use [Microsoft Intune](../install/administrative-templates.md#deploying-the-policies) or the [Local Group Policy Editor](#configure-copilot-group-policy) directly on the client machine. 
 
 ### Configure Copilot group policy
 
-1. Head over to the Microsoft Download Center and grab the Visual Studio [Group Policy Administrative Template files (ADMX/ADML)](https://www.microsoft.com/en-us/download/details.aspx?id=104405). It asks you where you want the files to be downloaded, ensure the location is `C:\Windows\PolicyDefinitions`.
+1. Visit the Microsoft Download Center to download the Visual Studio [Group Policy Administrative Template files (ADMX/ADML)](https://www.microsoft.com/en-us/download/details.aspx?id=104405). When prompted, ensure the files are saved to `C:\Windows\PolicyDefinitions`.
 
-2. Open the **Windows Local Group Policy Editor**, Navigate to Computer Configuration > Administrative Templates > Visual Studio > **Copilot Settings** and select a group policy.
+2. Open the **Windows Local Group Policy Editor** and navigate to **Computer Configuration > Administrative Templates > Visual Studio > Copilot Settings**. Select a group policy.
 
-   :::image type="content" source="media/vs-2022/copilot-inbox/intune-group-policy.png" alt-text="Screenshot of Group Policy to block Copilot for Individuals." lightbox="media/vs-2022/copilot-inbox/intune-group-policy.png":::
+   :::image type="content" source="media/vs-2022/copilot-inbox/intune-group-policy.png" alt-text="Screenshot of Group Policy Settings." lightbox="media/vs-2022/copilot-inbox/intune-group-policy.png":::
 
-3. Once you select your group policy, configure the policy to enable or disable.
+3. Once you select the group policy, configure it to enable or disable Copilot as needed.
 
-   :::image type="content" source="media/vs-2022/copilot-inbox/copilot-for-individuals-group-poilcy.png" alt-text="Screenshot of Group Policy to block copilot for individuals." lightbox="media/vs-2022/copilot-inbox/copilot-for-individuals-group-poilcy.png":::
+   :::image type="content" source="media/vs-2022/copilot-inbox/copilot-for-individuals-group-poilcy.png" alt-text="Screenshot of Group Policy to block Copilot for individuals." lightbox="media/vs-2022/copilot-inbox/copilot-for-individuals-group-poilcy.png":::
 
-4. Restart your Visual Studio instance to pick up the new policy changes
+4. Restart your Visual Studio instance to apply the new policy changes.
 
 ## Configure content exclusion
 
-Content exclusion for GitHub Copilot enables administrators to prevent certain files from being available to Copilot and keep sensitive content secure from Copilot use. You can use content exclusions to configure GitHub Copilot to ignore specific files in a [repository](https://docs.github.com/en/copilot/managing-github-copilot-in-your-organization/configuring-content-exclusions-for-github-copilot#configuring-content-exclusions-for-your-repository) or [organization](https://docs.github.com/en/copilot/managing-github-copilot-in-your-organization/configuring-content-exclusions-for-github-copilot#configuring-content-exclusions-for-your-organization). Content exclusion is only available with a GitHub Copilot Business or a GitHub Copilot Enterprise subscription. 
+Content exclusion for GitHub Copilot enables administrators to prevent certain files from being available to Copilot and keep sensitive content secure from Copilot use. You can use content exclusions to configure GitHub Copilot to ignore specific files in a [repository](https://docs.github.com/en/copilot/managing-github-copilot-in-your-organization/configuring-content-exclusions-for-github-copilot#configuring-content-exclusions-for-your-repository) or [organization](https://docs.github.com/en/copilot/managing-github-copilot-in-your-organization/configuring-content-exclusions-for-github-copilot#configuring-content-exclusions-for-your-organization).
+
+Content exclusion is available only with a GitHub Copilot Business or a GitHub Copilot Enterprise [subscriptions](https://docs.github.com/en/copilot/about-github-copilot/subscription-plans-for-github-copilot). 
 
-With [Visual Studio 2022 version 17.11](/visualstudio/releases/2022/release-notes), GitHub Copilot for Visual Studio will ignore excluded content. When you exclude content from Copilot, completions and chat aren't available on the affected files.
+With [Visual Studio 2022 version 17.11](/visualstudio/releases/2022/release-notes), GitHub Copilot for Visual Studio will ignore excluded content. When content is excluded, completions and chat aren't available for the affected files.
 
-Note that Visual Studio 2022 version 17.11 only respects rules in the root repository where your solution lives, and doesn't apply rules from git submodules or for files not under a git repo. 
+Note that Visual Studio 2022 version 17.11 respects rules only in the root repository where your solution lives, and doesn't apply rules from git submodules or for files not under a git repository. 
 
 ### GitHub Copilot Completions in Visual Studio and content exclusions
 
-- Code completions aren't available on excluded files.
+- Code completions aren't available for excluded files.
 
    :::image type="content" source="media/vs-2022/visual-studio-github-copilot-admin/copilot-content-exclusions-completions.png" alt-text="Screenshot of Copilot completions on an excluded file." lightbox="media/vs-2022/visual-studio-github-copilot-admin/copilot-content-exclusions-completions.png":::
 
-- Excluded content isn't included in code completion suggestions in other files.
+- Excluded content isn't included in code completion suggestions for other files.
 
 ### GitHub Copilot Chat in Visual Studio and content exclusions
 
@@ -71,3 +75,9 @@ Note that Visual Studio 2022 version 17.11 only respects rules in the root repos
 - Excluded content isn't included in GitHub Copilot Chat's responses.
 
     :::image type="content" source="media/vs-2022/visual-studio-github-copilot-admin/copilot-content-exclusions-chat-response.png" alt-text="Screenshot of chat's responses on excluded content." lightbox="media/vs-2022/visual-studio-github-copilot-admin/copilot-content-exclusions-chat-response.png":::
+
+## Related content
+
+- [GitHub Copilot settings](https://github.com/settings/copilot)
+- [GitHub Copilot: Compare plans](https://github.com/features/copilot/plans)
+- [GitHub Copilot Trust Center](https://resources.github.com/copilot-trust-center/)