Merge pull request #93391 from bwren/am-video

Azure Monitor video tutorial

Author: PRMerger16

articles/azure-monitor/log-query/get-started-portal.md

@@ -3,7 +3,7 @@ title: Get started with Azure Monitor Log Analytics | Microsoft Docs
 description: This article provides a tutorial for using Log Analytics in the Azure portal to write queries.
 ms.service:  azure-monitor
 ms.subservice: logs
-ms.topic: conceptual
+ms.topic: tutorial
 author: bwren
 ms.author: bwren
 ms.date: 07/19/2019

articles/azure-monitor/log-query/get-started-queries.md

@@ -3,23 +3,18 @@ title: Get started with log queries in Azure Monitor | Microsoft Docs
 description: This article provides a tutorial for getting started writing log queries in Azure Monitor.
 ms.service:  azure-monitor
 ms.subservice: logs
-ms.topic: conceptual
+ms.topic: tutorial
 author: bwren
 ms.author: bwren
-ms.date: 05/09/2019
+ms.date: 10/24/2019
 
 ---
 
 # Get started with log queries in Azure Monitor
 
-
-> [!NOTE]
-> You should complete [Get started with Azure Monitor Log Analytics](get-started-portal.md) before completing this tutorial.
-
 > [!NOTE]
 > You can work through this exercise in your own environment if you are collecting data from at least one virtual machine. If not then use our [Demo environment](https://portal.loganalytics.io/demo), which includes plenty of sample data.
 
-
 In this tutorial you will learn to write log queries in Azure Monitor. It will teach you how to:
 
 - Understand query structure
@@ -33,6 +28,10 @@ In this tutorial you will learn to write log queries in Azure Monitor. It will t
 For a tutorial on using Log Analytics in the Azure portal, see [Get started with Azure Monitor Log Analytics](get-started-portal.md).<br>
 For more details on log queries in Azure Monitor, see [Overview of log queries in Azure Monitor](log-query-overview.md).
 
+Follow along with a video version of this tutorial below:
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE42pGX]
+
 ## Writing a new query
 Queries can start with either a table name or the *search* command. You should start with a table name, since it defines a clear scope for the query and improves both query performance and relevance of the results.