diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
index a469a035..3120036c 100644
--- a/.openpublishing.publish.config.json
+++ b/.openpublishing.publish.config.json
@@ -18,10 +18,7 @@
}
],
"notification_subscribers": [
- "mikejo@microsoft.com",
- " clantz@microsoft.com",
- " mschulz@microsoft.com",
- "joncart@microsoft.com"
+ "mikejo@microsoft.com"
],
"sync_notification_subscribers": null,
"branches_to_filter": [],
diff --git a/docs/docfx.json b/docs/docfx.json
index bf8531fb..f04a928f 100644
--- a/docs/docfx.json
+++ b/docs/docfx.json
@@ -31,6 +31,8 @@
"overwrite": [],
"externalReference": [],
"globalMetadata": {
+ "ms.subservice": "live-share",
+ "ms.service": "visual-studio-family",
"feedback_system": "GitHub",
"feedback_github_repo": "MicrosoftDocs/live-share",
"feedback_product_url": "https://aka.ms/vsls-issues/",
@@ -38,8 +40,6 @@
"breadcrumb_path": "breadcrumb/toc.yml",
"extendBreadcrumb": true,
"audience": "developer",
- "ms.prod": "visual-studio-family",
- "ms.technology": "live-share",
"searchScope": ["Live Share"],
"uhfHeaderId": "MSDocsHeader-VisualStudio"
},
diff --git a/docs/includes/installation.md b/docs/includes/installation.md
index a778db1a..35c2f571 100644
--- a/docs/includes/installation.md
+++ b/docs/includes/installation.md
@@ -1,6 +1,6 @@
|Product|Installation steps|
|:-------------:|------------|
-||**Visual Studio Code (1.22.0+)**
1. Install [Visual Studio Code](https://code.visualstudio.com/) for Windows (7, 8.1, or 10), macOS **(High Sierra 10.13+)**, 64-bit Linux ([details](../use/install-live-share-visual-studio-code.md))
2. Download and install the Visual Studio Live Share extension from the marketplace.
3. Reload and wait for dependencies to download and install (see status bar).
4. **Linux**: If prompted to [install libraries](../reference/linux.md#install-linux-prerequisites), click install, enter password, restart VS Code when done.
|
+||**Visual Studio Code (1.22.0+)**
1. Install [Visual Studio Code](https://code.visualstudio.com/) for Windows (7, 8.1, or 10), macOS **(High Sierra 10.13+)**, 64-bit Linux ([details](../use/install-live-share-visual-studio-code.md))
2. Download and install the Visual Studio Live Share extension from the marketplace.
|
||**Visual Studio 2019**
1. Install [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/).
2. Install a [supported workload](../reference/platform-support.md) (e.g. ASP.NET, .NET Core, C++, Python, and/or Node.js).
3. Visual Studio Live Share is installed by default with these workloads.
|
||**Visual Studio 2017 15.6 or higher**
1. Install the latest version of [Visual Studio 2017](https://visualstudio.microsoft.com/vs/older-downloads/) (15.6+) on Windows (7, 8.1, or 10).
2. Install a [supported workload](../reference/platform-support.md) (e.g. ASP.NET, .NET Core, C++, and/or Node.js).
3. Download and install the Visual Studio Live Share extension from the marketplace.

|
diff --git a/docs/media/policies-visual-studio/live-share-policies.png b/docs/media/policies-visual-studio/live-share-policies.png
index f8909eb3..4a346ea3 100644
Binary files a/docs/media/policies-visual-studio/live-share-policies.png and b/docs/media/policies-visual-studio/live-share-policies.png differ
diff --git a/docs/media/vscode-guest-command-control.png b/docs/media/vscode-guest-command-control.png
new file mode 100644
index 00000000..b6f41b5b
Binary files /dev/null and b/docs/media/vscode-guest-command-control.png differ
diff --git a/docs/reference/linux.md b/docs/reference/linux.md
index f51e61b9..746f0e3e 100644
--- a/docs/reference/linux.md
+++ b/docs/reference/linux.md
@@ -20,107 +20,6 @@ Creative Commons Attribution 4.0 License (International): https://creativecommon
Linux is a highly variable environment and with the sheer number of desktop environments and distributions can be complicated to get working. If you stick to supported versions of **Ubuntu Desktop** (16.04+), **CentOS 7**, or **Fedora Workstation** (27+) and only use **official distributions of VS Code**, you should find the process straight forward. However, in the event that you are using a non-standard configuration or downstream distribution, you may or may not run into some hiccups. This document provides some information on requirements and some troubleshooting details that might help you get up and running even if your configuration is only community supported. Note that Live Share only supports **64-bit Linux**.
-## Install Linux prerequisites
-
-Some distributions of Linux are missing libraries Live Share needs to function. By default, Live Share attempts to detect and install Linux prerequisites for you. You'll see a toast notification when Live Share encounters a problem that can originate from missing libraries asking you for permission to install them.
-
-
-
-When you click "Install", a terminal window will appear where your OS will ask you to enter your admin / root (sudo) password to continue. Assuming the script completes successfully, reload Visual Studio Code when prompted you should be all set! You may also want to check out **[tips by distribution](#tips-by-distribution)** for other hints and workarounds if any exist.
-
-If you see a message indicating the script does not support your distribution, see **[tips for community supported distributions](#tips-for-unsupported-distros)** for information the community has shared with us.
-
-If you **prefer not to have VS Code run the command for you**, you can also opt to re-run the very latest version of this script at any time manually by using the following command in a Terminal window:
-
-```
-wget -O ~/vsls-reqs https://aka.ms/vsls-linux-prereq-script && chmod +x ~/vsls-reqs && ~/vsls-reqs
-```
-
-## Tips by distribution
-
-While the prerequisite install script above covers a variety of distributions, you may be wondering what is typically missing from vanilla installations. The following list shows the key libraries that were missing in a fresh install of a given distribution. The list also provides some tips that can help you get up and running if you hit a problem.
-
-| Distribution | Vanilla install missing libraries | Additional steps |
-|--------|-------------------|----|
-| Ubuntu Desktop 22.04 (64-bit) | `libssl1.1` | <none> |
-| Ubuntu Desktop 18.04 (64-bit) | <none> | <none> |
-| Ubuntu Desktop 16.04 (64-bit) | <none> | <none> |
-| Kubuntu 18.04 (64-bit) | `gnome-keyring desktop-file-utils` | <none> |
-| Kubuntu 16.04 (64-bit) | `gnome-keyring desktop-file-utils` | <none> |
-| Xubuntu 18.04 (64-bit) |<none> |
- Ensure "Launch GNOME services on startup" is checked in the "Advanced" tab of "Session and Startup".
- If you run into sign-in trouble, install `seahorse`, start "Passwords and Keys", verify you have "Login" keyring and that you can unlock it.
|
-| Xubuntu 16.04 (64-bit) | <none> | - Ensure "Launch GNOME services on startup" is checked in the "Advanced" tab of "Session and Startup".
- If you run into sign-in trouble, install `seahorse`, start "Passwords and Keys", verify you have "Login" keyring and that you can unlock it.
|
-| Mint 19 Cinnamon (64-bit) | <none> | <none> |
-| Mint 18.3 Cinnamon (64-bit) | <none> | <none> |
-| Debian 10 (Buster) Testing (64-bit) | Release not stable, so unknown. | - Debian Testing and Unstable (Sid) are not officially supported.
- There is a [known issue](https://github.com/dotnet/corefx/issues/33179) in .NET Core that affects Live Share.
- See [here for a workaround](https://github.com/dotnet/corefx/issues/33179#issuecomment-435118249).
- There is a [known issue](https://github.com/MicrosoftDocs/live-share/issues/4000) with WSL certificates.
|
-| Debian 9 GNOME Desktop (64-bit) | <none> | - You may need to install `sudo` and add your user to the sudo group to use the automated install script.
|
-| Fedora Workstation 29 (64-bit) | `openssl-libs` | <none> |
-| Fedora Workstation 28 (64-bit) | <none> | <none> |
-| Fedora Workstation 27 (64-bit) | <none> | <none> |
-| CentOS 7 GNOME Desktop (64-bit) | <none> | <none> |
-
-See **[tips for community supported distributions](#tips-for-community-supported-distros)** for information about other non-Debian / Ubuntu or RHL based distributions.
-
-Additional details can also be found [below](#detailed-library-requirements) on the specific libraries Live Share needs.
-
-
-
-## Tips for community supported distros
-
-Distributions outside of the Debian / Ubuntu or RHL trees are not officially supported by Visual Studio Code or .NET Core. Therefore, by extension, they are not officially supported by Visual Studio Live Share either. However, the community has contributed some useful information about getting Live Share up and running on a number of additional distributions.
-
-> **PRs welcome:** If you're interested in updating this information with your favorite distribution, submit a PR for [this file](https://github.com/MicrosoftDocs/live-share/tree/master/docs/reference/linux.md) in our docs GitHub repo. Even better, if you'd like to get the dependency installer supporting your favorite distribution, you can submit a PR [for this file](https://github.com/MicrosoftDocs/live-share/blob/master/scripts/linux-prereqs.sh).
-
-| Distribution | Working? | Vanilla install missing libraries | Additional Steps |
-|--------------|----------|-------------------|------------------|
-| Arch Linux (64-bit) | Yes | Varies. Possible libraries: `gcr liburcu openssl-1.0 krb5 zlib icu gnome-keyring libsecret desktop-file-utils xorg-xprop icu69` | - Supported by the [prerequisite install script](#install-linux-prerequisites).
- Use the [visual-studio-code-bin](https://aur.archlinux.org/packages/visual-studio-code-bin) AUR package for VS Code.
- `sudo` will need to be installed to use the automated prerequisite install script.
- `gnome-keyring` may require additional [setup steps](https://wiki.archlinux.org/index.php/GNOME/Keyring) in some desktop environments.
|
-| Manjaro 17.1 (64-bit) | Yes | `xorg-xprop liburcu icu69` | - Supported by the [prerequisite install script](#install-linux-prerequisites).
- Use the [visual-studio-code-bin](https://aur.archlinux.org/packages/visual-studio-code-bin) AUR package for VS Code.
|
-| openSuSE LEAP 15 KDE (64-bit) | Yes | `libopenssl1_0_0 gnome-keyring` | - Supported by the prerequisite install script.
|
-| Solus 3 (64-bit) | Yes | `xprop` | - Supported by the [prerequisite install script](#install-linux-prerequisites).
- Versions of the `vscode` package prior to release 57 were missing required product.json values ([see below](#vs-code-oss-issues)). Upgrade the `vscode` package to resolve this issue.
|
-| Gentoo (64-bit) | Yes | Highly variable. Possible missing packages: `dev-libs/openssl-1.0.2 net-libs/libgsasl dev-libs/icu sys-libs/zlib sys-apps/util-linux app-crypt/libsecret gnome-base/gnome-keyring x11-apps/xprop`| - The `visual-studio-code` package in the **jorgicio** overlay is known to work.
-
-## Install prerequisites manually
-
- While we recommend using Live Share's **dependency install script**, this section provides further details on library requirements in the event you want perform these steps yourself or are using a distribution not supported by the script.
-
-Typical missing libraries in vanilla installations can be found in the [tips by distribution](#tips-by-distribution) and [tips for community supported distributions](#tips-for-unsupported-distros) sections.
-
-### Detailed library requirements
-
-Visual Studio Live Share's native library requirements come from its use of .NET Core 2.1, libsecret to persist credentials, and its browser integration. The following table summarizes these requirements for distributions officially supported by .NET Core.
-
-| Distribution | .NET Core Reqs | Credential Storage Reqs| Browser Integration Reqs |
-|--------------|-----------|--------------------|------------|
-| Ubuntu and downstream distributions | `libssl1.0.0 libkrb5-3 zlib1g libicu55` (for Ubuntu 16.04, Mint 18.3) or `libicu57` (for Ubuntu 17.10) or `libicu60` (for Ubuntu 18.04, Mint 19) | `libsecret-1-0 gnome-keyring` (or libsecret supported keyring - Kwallet does not support libsecret) | `desktop-file-utils x11-utils` |
-| Debian 9 and downstream distributions | `libssl1.0.2 libkrb5-3 zlib1g libicu57` | `libsecret-1-0 gnome-keyring` (or libsecret supported keyring - Kwallet does not support libsecret) | `desktop-file-utils x11-utils` |
-| RHL / CentOS/ Fedora | `openssl-libs krb5-libs zlib libicu` Fedora also requires `openssl-libs`| `libsecret gnome-keyring` (or libsecret supported keyring - Kwallet does not support libsecret) | `desktop-file-utils xprop` |
-| Alpine Linux | `openssl1.1 icu krb5 zlib` | `libsecret gnome-keyring` (or libsecret supported keyring - Kwallet does not support libsecret) | `desktop-file-utils xprop`
-
-While other distributions require the same libraries, their package names may vary. You can find some of these in the [tips for community supported distributions](#tips-for-unsupported-distros) section.
-
-### Debian / Ubuntu
-
-Libraries may be installed on Debian/Ubuntu based distributions by running `sudo apt install ` in a terminal.
-
-For Ubuntu based distributions including Mint, run:
-
-```
-sudo apt install libssl1.1 libkrb5-3 zlib1g libicu[0-9][0-9] gnome-keyring libsecret-1-0 desktop-file-utils x11-utils
-```
-
-For Debian 9 and non-Ubuntu downstream distributions, run:
-
-```
-sudo apt install libssl1.0.2 libkrb5-3 zlib1g libicu57 gnome-keyring libsecret-1-0 desktop-file-utils x11-utils
-```
-
-### Fedora / CentOS / RHL
-
-Libraries may be installed on Fedora/CentOS/RHL based distributions by running `sudo yum install ` in a terminal. For example, this will install everything:
-
-```
- sudo yum install openssl-libs krb5-libs zlib libicu libsecret gnome-keyring desktop-file-utils xprop
-```
-
## VS Code OSS Issues
> **Arch Linux/Manjaro Users:** Use the [visual-studio-bin](https://aur.archlinux.org/packages/visual-studio-code-bin) AUR package to avoid this problem.
@@ -146,8 +45,6 @@ As a **workaround**, you can add the following into the product.json:
]
```
-See [above](#tips-for-community-supported-distros) for additional details on whether the distribution you are using is known to work.
-
## Linux browser integration
Visual Studio Live Share typically **does not require additional installation steps** to enable browser integration on Linux.
diff --git a/docs/reference/notebooks.md b/docs/reference/notebooks.md
index 04625161..dc6d466d 100644
--- a/docs/reference/notebooks.md
+++ b/docs/reference/notebooks.md
@@ -16,7 +16,7 @@ ms.workload:
Notebooks have become a key part of many developer's and data scientist's workflow. With Visual Studio Code offering a rich, native notebook-editor, we're excited to enable a real-time collaboration experience, that will allow teams and classrooms to use notebooks and Live Share together.
-The Live Share notebook experience is currently in preview, and therefore, has some [pre-requisitions](#pre-requisites) and [known issues](#known-issues) to be aware of. We'll be iterating rapidly on this initial preview release, and therefore, please don't hesitate to [send us any questions/feedback](http://github.com/microsoftdocs/live-share)) as you're evaluating it đ
+The Live Share notebook experience is currently in preview, and therefore, has some [pre-requisitions](#pre-requisites) and [known issues](#known-issues) to be aware of. We'll be iterating rapidly on this initial preview release, and therefore, please don't hesitate to [send us any questions/feedback](https://github.com/microsoftdocs/live-share)) as you're evaluating it đ
diff --git a/docs/reference/security.md b/docs/reference/security.md
index cf8eaa00..06934884 100644
--- a/docs/reference/security.md
+++ b/docs/reference/security.md
@@ -100,6 +100,15 @@ You can **always reject** (disable anonymous guests) or **always accept** anonym
**Regardless, remember that you should only send Live Share invitation links to people you trust.**
+### Allowing guest command control
+
+
+
+To allow guests to run arbitrary commands via Code Actions (âQuick Fixesâ) and CodeLens set the following setting:
+
+* In **VS Code**, set `liveshare.languages.allowGuestCommandControl` in settings.json (File > Preferences > Settings) to `true` or `false` (the default).
+
+
## Controlling file access and visibility
As a guest, Live Share's remote model gives you quick read/write access to files and folders the host has shared with you without having to sync the entire contents of a project. You can therefore independently navigate and edit files in the entire shared file tree. **However, this freedom does pose some risks to the host.** In concept, a developer could opt to go in and modify source code without your knowledge or see sensitive source code or "secrets" located somewhere in the shared file tree. Consequently, as a host, you may not always want the guest to have access to the entirety of a project you are sharing. Thankfully, an added advantage of this remote model is that you can opt to "exclude" files you do not want to share with anyone without sacrificing on functionality. Your guests can still participate in things like debugging sessions that would normally require access to these files if they wanted to do so on their own.
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index b06db4ac..eb27fc5e 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -27,7 +27,6 @@ The following are troubleshooting tips related to installing Visual Studio Live
| VS | The extension installer cannot find a version of Visual Studio to use when trying to install the Visual Studio Live Share extension. | Visual Studio Live Share requires **Visual Studio 2017 version 15.6** or higher for both hosts and guests. Install the latest stable [update of Visual Studio 2017](https://visualstudio.com/vs/) and retry. |
| VS Code | A "**Dependencies could not be installed**" error appears the while extension is **finishing installation** on first start or you get errors about **missing or already present files**. | Verify you are on a **good network connection**. If you are, you could be running into a **proxy or firewall** issue. See [connectivity troubleshooting](#connectivity).
|
| VS Code | Installing the Visual Studio Live Share extension from the marketplace installs it in the stable/insiders version of VS Code instead of the version I want. | Start VS Code stable or insiders depending on your preference, click on the "extensions" tab, search for "Visual Studio Live Share" and install from there. |
-| VS Code (**Linux**) | The Live Share extension does not activate and **no status bar items appear** after installing the extension on **Linux**. | Visual Studio Live Share depends on .NET Core 2.0 which has a number of Linux prerequisites that may not be met on certain distributions of Linux by default. See [here for details](reference/linux.md#install-linux-prerequisites) on what should be installed. |
## Sign in
@@ -41,7 +40,6 @@ The following are troubleshooting tips for sign in problems.
| All | You are getting a timeout or connection error. | See [connectivity troubleshooting](#connectivity). |
| All | When signing in using a Microsoft backed **work or school email address** you see a message saying, **"Need admin approval"**. | Your Azure AD tenet is setup to require âadmin consentâ for new applications accessing the contents of the directory. See [here](reference/security.md) for more details. |
| VS Code (**macOS**) | When signing in you see an error stating **SecKeychainAddGenericPassword() failed**. | This is almost always due to a common problem with macOS where password changes are not reflected in the login keychain. Try going into "Keychain Access", locking the login keychain and then unlocking it again. This may be enough to resolve the problem, but if you are unable to unlock it with your current password, try your previous one. If that works, change the login keychain password to your current password. See [here](https://support.apple.com/guide/keychain-access/mac-keychain-password-kyca1242/mac) for details. |
-| VS Code (**Linux**) | When entering in the user code after signing in via the browser you see an error stating **secret_password_store_sync() failed with error code XX**. | This is typically due to `gnome-keyring` and/or `libsecret-1-0`/ `libsecret` not being installed. You can validate gnome-keyring is properly configured by installing `seahorse` and then using the "Passwords and Keys" application in your desktop environment. Read more about [Linux prerequisites here](reference/linux.md#install-linux-prerequisites). |
| VS Code (**Linux**) | You are prompted to enter a user code with Live Share v0.3.295 or below, but no browser appears to allow you to get one. | We are working to eliminate the user code requirement on Linux. In the mean time, a browser window should appear for you to use to sign in. If not, the browser window may be hidden under VS Code. See the next tip if this is not the case. |
| VS Code | After clicking "Sign in" (or using the "Live Share: Sign in" command), no browser window appears to allow you to enter your credentials. | 1. [Sign in here](https://insiders.liveshare.vsengsaas.visualstudio.com/auth/login)
2. After signing in, click "Having trouble?"
3. Follow the directions to enter a temporary user code into the tool. |
| All | You would like to join a collaboration session but have not / do not want to receive email updates. | Signing in to the Live Share extension in VS/VS Code does not opt you into receiving email updates.
Live Share requires guests to sign in as a security measure so the host has visibility to the identity of those that have joined. [Up vote this feature](https://github.com/MicrosoftDocs/live-share/issues/3) if you'd like the option to allow anonymous users to join (e.g. users with no name / a user defined name). |
diff --git a/docs/use/enable-accessibility-features-visual-studio-code.md b/docs/use/enable-accessibility-features-visual-studio-code.md
index 76fb9af7..ec2e8887 100644
--- a/docs/use/enable-accessibility-features-visual-studio-code.md
+++ b/docs/use/enable-accessibility-features-visual-studio-code.md
@@ -75,4 +75,4 @@ With the exception of cursor tethering, the accessibility features described abo
## Network Requirements
-Speech is generated by Azure Cognitive Services on demand. This means to receive speech feedback, you need to have an active internet connection and be able to reach the Cognitive Services endpoint - https://westus2.api.cognitive.microsoft.com.
\ No newline at end of file
+Speech is generated by Azure Cognitive Services on demand. This means to receive speech feedback, you need to have an active internet connection and be able to reach the Cognitive Services endpoint - `https://westus2.api.cognitive.microsoft.com`.
\ No newline at end of file
diff --git a/docs/use/install-live-share-visual-studio.md b/docs/use/install-live-share-visual-studio.md
index 31e65ac3..94669f51 100644
--- a/docs/use/install-live-share-visual-studio.md
+++ b/docs/use/install-live-share-visual-studio.md
@@ -73,7 +73,7 @@ If you run into trouble, check out [troubleshooting](../troubleshooting.md#sign-
## Guest limitations
-There are currently some shortcomings that guests will experience using the features described in these articles. But collaboration session hosts keep the complete functionality of their tool of choice. For more information, see:
+There are currently some shortcomings that guests will experience using the features described in these articles. But collaboration session hosts keep the complete functionality of their tool of choice. For more information, see the following:
- [Language and platform support](../reference/platform-support.md)
- [Extension support](../reference/extensions.md)
diff --git a/docs/use/policies-visual-studio.md b/docs/use/policies-visual-studio.md
index 4d1db065..5dd17e5d 100644
--- a/docs/use/policies-visual-studio.md
+++ b/docs/use/policies-visual-studio.md
@@ -2,7 +2,7 @@
title: Configure Visual Studio using Group Policy Administrative Templates
titleSuffix: Live Share
description: Learn how to get started with Group Policy Administrative Template files to ensure sessions are controlled the way you want.
-ms.date: 11/08/2022
+ms.date: 8/31/2023
ms.reviewer: mikejo5000
ms.topic: how-to
author: curib
@@ -19,10 +19,12 @@ Creative Commons Attribution 4.0 License (International): https://creativecommon
# Configure Visual Studio using Group Policy Administrative Templates
-To control certain aspects of Visual Studio Live Share behavior to achieve consistency or compliance across your organization, you can now configure Visual Studio using [Group Policy Administrative Templates (ADMX/ADML files)](https://aka.ms/vs/admx/details). The Visual Studio group policy settings contained in the ADMX file are machine wide for all users.
+To control certain aspects of Visual Studio Live Share behavior to achieve consistency or compliance across your organization, you can now use [Group Policy Administrative Templates (ADMX/ADML files)](https://aka.ms/vs/admx/details). To configure and deploy these policies, you can use [Microsoft Intune](/visualstudio/install/administrative-templates?view=vs-2022#deploying-the-policies&preserve-view=true) or the Local Group Policy Editor directly on the client machine.
With these policies, your organization will be able to add an extra layer of protection to prevent accidents on Visual Studio Live Share and increase productivity.
+To get started with enabling policies, youâll need to [download](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsls-vs-2022) the latest Visual Studio Live Share version from the Visual Studio Marketplace.
+
## Policies Supported

@@ -39,15 +41,21 @@ With these policies, your organization will be able to add an extra layer of pro
**Enforce accepting/rejecting a guest:** Requires the host to individually accept each guest that attempts to join a session. We already have the ["Live Share: Guest Approval Required"](../reference/security.md#requiring-guest-approval-for-signed-in-users) setting, so this policy is effectively just enforcing that to "true".
-## Step 1: Download the latest Visual Studio Live Share version
+**Disable chat:** Prevents the host and guest from using chat within the session.
-To get started with enabling policies, youâll need to [download](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsls-vs-2022) the latest Visual Studio Live Share version from the Visual Studio Marketplace.
+## Configure policies with Microsoft Endpoint Manager (Intune) settings
+
+Visual Studio global policies are included in the [Microsoft Endpoint Manager (Intune) settings](/mem/intune/configuration/settings-catalog). This makes it easier for administrators to configure their organization's devices now that the Visual Studio software policies are readily accessible in the Device Configuration Profile UI. Since Visual Studio will be keeping the policies up to date in Intune's settings catalog, administrators will be able to always access the most current Visual Studio Live Share configuration options without having to do manual imports.
+
+To take advantage of Visual Studio's built-in configuration policy settings in Intune, simply create a Device Configuration Profile, choose "Settings catalog", and then add the desired polices that you want configured on your devices.
+
+## Configure policies with Local Group Policy Editor
-## Step 2: Download the templates
+### Step 1: Download the templates
-Next, head over to the Microsoft Download Center and grab the [Visual Studio Group Policy Administrative Template files (ADMX/ADML)](https://aka.ms/vs/admx/details). Itâll ask you where you want the files to be downloaded, please ensure the location is âC:\Windows\PolicyDefinitions\'.
+Head over to the Microsoft Download Center and grab the [Visual Studio Group Policy Administrative Template files (ADMX/ADML)](https://aka.ms/vs/admx/details). Itâll ask you where you want the files to be downloaded, please ensure the location is âC:\Windows\PolicyDefinitions\'.
-## Step 3: Test using the Local Group Policy Editor
+### Step 2: Test using the Local Group Policy Editor
- Open the Windows Local Group Policy Editor
- Navigate to Computer Configuration > Administrative Templates > Visual Studio > Live Share Settings