edits

Author: Mikejo5000

docs/debugger/remote-debugging-azure.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debug ASP.NET Core on IIS and Azure | Microsoft Docs"
 ms.custom: "remotedebugging"
-ms.date: "05/21/2018"
+ms.date: "04/14/2020"
 ms.topic: "conceptual"
 ms.assetid: a6c04b53-d1b9-4552-a8fd-3ed6f4902ce6
 author: "mikejo5000"
@@ -81,6 +81,8 @@ From Visual Studio, you can quickly publish and debug your app to a fully provis
 
 1. Open **Server Explorer** (**View** > **Server Explorer**), right-click on the App Service instance and choose **Attach Debugger**.
 
+   If you see a message instructing your to install Cloud Explorer, install it. Then, right-click on the App Service instance in Cloud Explorer and choose **Attach Debugger**.
+
 1. In the running ASP.NET application, click the link to the **About** page.
 
     The breakpoint should be hit in Visual Studio.

docs/debugger/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md

@@ -1,6 +1,6 @@
 ---
 title: "Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor | Microsoft Docs"
-ms.date: "08/24/2017"
+ms.date: "04/14/2020"
 ms.topic: "reference"
 f1_keywords:
   - "vs.debug.error.remote_debug"
@@ -63,7 +63,7 @@ If these values are correct and the message mentions **Windows Authentication**
 
 ## <a name="connection_terminated"></a> The connection with the remote endpoint was terminated
 
-If you are debugging an Azure App Service app, try using the [Attach Debugger](../debugger/remote-debugging-azure.md#remote_debug_azure_app_service) command from Server Explorer instead of **Attach to Process**.
+If you are debugging an Azure App Service app, try using the [Attach Debugger](../debugger/remote-debugging-azure.md#remote_debug_azure_app_service) command from Cloud Explorer or Server Explorer instead of **Attach to Process**.
 
 If you are using **Attach to Process** to debug: