[BrokenLinksH2]

docs/reference/connectivity.md

@@ -68,7 +68,7 @@ The connection mode you are in will dictate the specific ports and URLs that nee
 
 | Mode | Client Access Requirement | Troubleshooting |
 |------|--------------|-----------------|
-| Any | Outbound access to `*.liveshare.vsengsaas.visualstudio.com:443` | Ensure your corporate or personal network firewall allows you to connect to this domain. Enter https://insiders.liveshare.vsengsaas.visualstudio.com in a browser and verify you land at the Visual Studio Live Share home page. You may also be running into [proxy issues](#proxies) that need to be resolved.|
+| Any | Outbound access to `*.liveshare.vsengsaas.visualstudio.com:443` | Ensure your corporate or personal network firewall allows you to connect to this domain. Enter https://visualstudio.microsoft.com/services/live-share/ in a browser and verify you land at the Visual Studio Live Share home page. You may also be running into [proxy issues](#proxies) that need to be resolved.|
 | Any (VS Code) | Outbound access to `download.microsoft.com:443` | Ensure your corporate or personal network firewall allows you to connect to this domain. You may also be running into [proxy issues](#proxies) that need to be resolved. |
 | Auto | Auto-switches. See direct and relay modes. | Switch to direct or relay mode to troubleshoot. |
 | Direct | Hosts: A port in the range 5990 - 5999 needs to be opened to accept inbound local network connections.<br /><br />Guests: A network route and outbound access to the host on this same port. | Verify "vsls-agent" is not blocked by your desktop firewall software for this port range and that you can ping one another. While Windows and other desktop software should prompt you the first time the agent starts up, we have seen instances where group policies prevent this from happening and you will need to [manually add the entry](#manually-adding-a-firewall-entry). You may also be running into [proxy issues](#proxies) that need to be resolved. |

docs/reference/platform-support.md

@@ -32,7 +32,7 @@ All languages / platforms have same file intellisense (when the respective exten
 | C# | ✅ | ✅ |
 | Clojure | ✅ | *N/A* <sup>4</sup> |
 | [ColdFusion (CFML)](https://marketplace.visualstudio.com/items?itemName=KamasamaK.vscode-cfml) | ✅ | *N/A* <sup>4</sup> |
-| [Crystal](https://marketplace.visualstudio.com/items?itemName=faustinoaq.crystal-lang) | ✅ | *N/A* <sup>4</sup> |
+| Crystal | ✅ | *N/A* <sup>4</sup> |
 | CSHTML | *N/A* <sup>1</sup> | ✅ |
 | CSS | *N/A* | *N/A* |
 | Dart | ✅ | ✅ |
@@ -67,12 +67,12 @@ All languages / platforms have same file intellisense (when the respective exten
 | reStructuredText | ✅ | *N/A* |
 | Ruby | ✅ | ✅ |
 | Rust | ✅ | *N/A* <sup>4</sup> |
-| [Sass](https://marketplace.visualstudio.com/items?itemName=robinbentley.sass-indented) | ✅ | *N/A* |
+| Sass | ✅ | *N/A* |
 | Scala | ✅ | *N/A* <sup>4</sup> |
 | Solidity | ✅ | *N/A* <sup>4</sup> |
 | SQL / T-SQL | *N/A* | *N/A* <sup>4</sup> |
 | [Stylus](https://marketplace.visualstudio.com/items?itemName=sysoev.language-stylus) | ✅ | *N/A* |
-| [Svelte](https://marketplace.visualstudio.com/items?itemName=JamesBirtles.svelte-vscode) | ✅ | *N/A* <sup>4</sup> |
+| Svelte | ✅ | *N/A* <sup>4</sup> |
 | Swift | ✅ | *N/A* <sup>4</sup> |
 | Terraform | ✅ | *N/A* <sup>4</sup> |
 | XML | ✅ | *N/A* <sup>4</sup> |

docs/reference/security.md

@@ -251,7 +251,7 @@ Your AD admin would need to resolve this for you using the following information
 * **Application Type**: Web App
 * **Applications Status**: Production
 * **Delegated Permissions**: User.Read
-* **Application URL**: https://insiders.liveshare.vsengsaas.visualstudio.com/
+* **Application URL**: https://visualstudio.microsoft.com/services/live-share/
 * **Reply URL**: https://insiders.liveshare.vsengsaas.visualstudio.com/auth/redirect/windowslive/
 
 This would only need to be done once for anyone using Live Share. See [here](/azure/active-directory/develop/active-directory-v2-scopes#admin-restricted-scopes) and [here](https://stackoverflow.com/questions/39861830/azure-ad-admin-consent-from-the-azure-portal) for details.

docs/troubleshooting.md

@@ -40,7 +40,7 @@ The following are troubleshooting tips for sign in problems.
 | VS Code | While a browser window pops up during sign in and the process <strong>appears to succeed on the web page</strong>, the status bar <strong>still says, "Sign in"</strong> after closing the browser. | After signing in, click "Having trouble?" and follow the directions to enter a temporary user code into the tool.<br /><br />We would also love to see what might be happening, so please [log a bug](https://aka.ms/vsls-problem). |
 | All | You are getting a <strong>timeout or connection error</strong>. | 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/en-us/HT201609) for 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 <strong>prompted to enter a user code</strong> 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), <strong>no browser window appears to allow you to enter your credentials</strong>. | 1. [Sign in here](https://insiders.liveshare.vsengsaas.visualstudio.com/auth/login)<br />2. After signing in, click "Having trouble?"<br /> 3. Follow the directions to enter a temporary user code into the tool. |
@@ -70,7 +70,7 @@ As outlined in the [connectivity requirements for Live Share](reference/connecti
 |------|------|----------------|
 | All | You are using a <strong>proxy</strong> and are seeing a number of connectivity problems | Proxy settings can be tricky.  Try setting the **HTTP_PROXY** and **HTTPS_PROXY** environment variables **globally** and then restarting your tool. See [proxy settings](reference/connectivity.md#proxies) for more details. There are likely some configurations we do not yet support, so [let us know](https://github.com/MicrosoftDocs/live-share/issues/86) if this does not work for you. |
 | VS Code | After installing the extension and starting up VS Code for the first time you get an <strong>an error when "Finishing Installation" appears in the status bar</strong>. |  You cannot access the internet or access to download.visualstudio.microsoft.com and/or download.microsoft.com on port 443 is blocked by your personal or corporate firewall. See [here](https://github.com/MicrosoftDocs/live-share/issues/58) for information on why Live Share needs to download something at this point. |
-| All | You are <strong>unable to sign into Visual Studio Live Share</strong> | You cannot access the internet or access to *.liveshare.vsengsaas.visualstudio.com on port 80/443 is blocked by your personal or corporate firewall. Enter https://insiders.liveshare.vsengsaas.visualstudio.com in a browser and verify you land at the Visual Studio Live Share home page. |
+| All | You are <strong>unable to sign into Visual Studio Live Share</strong> | You cannot access the internet or access to *.liveshare.vsengsaas.visualstudio.com on port 80/443 is blocked by your personal or corporate firewall. Enter https://visualstudio.microsoft.com/services/live-share/ in a browser and verify you land at the Visual Studio Live Share home page. |
 | All | You are in <strong>auto mode</strong> (the default), are able to sign in, but see a <strong>timeout or connection error</strong> when either sharing or joining. | Either both direct and relay modes are failing to connect or there is a bug with auto mode. If you are able to connect after [switching to direct or relay mode](reference/connectivity.md#changing-the-connection-mode), please [raise a bug](https://aka.ms/vsls-problem). |
 | All | You are in <strong>direct mode</strong>, are able to sign in, but see a <strong>timeout or connection error</strong> when either sharing or joining. | The guest and host cannot directly connect. Try [auto or relay mode](reference/connectivity.md#changing-the-connection-mode) to see if the problem goes away. You may need to [manually allow Live Share through your personal firewall](reference/connectivity.md#manually-adding-a-firewall-entry) or simply use relay mode. |
 | All | You are in <strong>relay mode</strong>, are able to sign in, but are notified of a <strong>timeout or connection error</strong> when either sharing or joining. | Access to *.servicebus.windows.net on port 80/443 is blocked is blocked by your personal or corporate firewall. Try [direct mode](reference/connectivity.md#changing-the-connection-mode). |