link fixes

Author: bwren

articles/azure-monitor/platform/agents-overview.md

@@ -50,12 +50,12 @@ The Azure Diagnostics agent should be used when you want to:
 ## Log Analytics agent
 For advanced monitoring where you need to do more than collect metrics and a subset of logs, the Log Analytics agent for Windows and Linux is required. The Log Analytics agent was developed for comprehensive management across on-premises physical and virtual machines, computers monitored by System Center Operations Manager, and VMs in hosted in other clouds. The Windows and Linux agents connect to a Log Analytics workspace to collect both monitoring solution-based data as well as custom data sources that you configure.
 
-[!INCLUDE [log-analytics-agent-note](../../../../includes/log-analytics-agent-note.md)]
+[!INCLUDE [log-analytics-agent-note](../../../includes/log-analytics-agent-note.md)]
 
 The Log Analytics agent should be used when you want to:
 
 * Collect data from a variety of sources both within Azure, other cloud providers, and on-premises resources. 
-* Using one of the Azure Monitor monitoring solutions such as [Azure Monitor for VMs](../../monitoring/../../azure-monitor/insights/vminsights-overview.md?toc=%2fazure%2fmonitoring%2ftoc.json), [Azure Monitor for containers](../../monitoring/../../azure-monitor/insights/container-insights-overview.md?toc=%2fazure%2fmonitoring%2ftoc.json), etc.  
+* Using one of the Azure Monitor monitoring solutions such as [Azure Monitor for VMs](../insights/vminsights-overview.md), [Azure Monitor for containers](../insights/container-insights-overview.md), etc.  
 * Use one of the other Azure management services such as [Azure Security Center](../../security-center/security-center-intro.md), [Azure Automation](../../automation/automation-intro.md), etc.
 
 Previously, several Azure services were bundled as the *Operations Management Suite*, and as a result the Log Analytics agent is shared across services including Azure Security Center and Azure Automation.  This includes the full set of features they offer, delivering comprehensive management of your Azure VMs through their lifecycle.  Some examples of this are:
@@ -66,7 +66,7 @@ Previously, several Azure services were bundled as the *Operations Management Su
 * Azure services such as [Application Insights](https://docs.microsoft.com/azure/application-insights/) and [Azure Security Center](https://docs.microsoft.com/azure/security-center/), which natively store their data directly in Log Analytics.  
 
 ## Dependency agent
-The Dependency agent was developed as part of the Service Map solution, which was originally developed externally from Microsoft. [Service Map](../../monitoring/service-map.md) and [Azure Monitor for VMs](../../azure-monitor/insights/vminsights-overview.md) requires a Dependency Agent on Windows and Linux virtual machines and it integrates with the Log Analytics agent to collects discovered data about processes running on the virtual machine and external process dependencies. It stores this data in Log Analytics and visualizes the discovered interconnected components.
+The Dependency agent was developed as part of the Service Map solution, which was originally developed externally from Microsoft. [Service Map](service-map.md) and [Azure Monitor for VMs](../../azure-monitor/insights/vminsights-overview.md) requires a Dependency Agent on Windows and Linux virtual machines and it integrates with the Log Analytics agent to collects discovered data about processes running on the virtual machine and external process dependencies. It stores this data in Log Analytics and visualizes the discovered interconnected components.
 
 You may need some combination of these agents to monitor your VM. The agents can be installed side by side as Azure extensions, however on Linux, the Log Analytics agent *must* be installed first or else installation will fail. 
 

articles/azure-monitor/platform/data-collection.md

@@ -137,7 +137,7 @@ Log Analytics can collect data from a variety of sources both within Azure and f
 - [Activity logs](../../log-analytics/log-analytics-activity.md) from Azure resources that include information on their configuration and health and [Diagnostic logs](../../monitoring-and-diagnostics/monitor-stream-diagnostic-logs-log-analytics.md) that provide insights into their operation.
 - Agents on [Windows](../../log-analytics/log-analytics-windows-agent.md) and [Linux](../../log-analytics/log-analytics-quick-collect-linux-computer.md) virtual machines that send telemetry from the guest operating system and applications to Log Analytics according to [Data Sources](../../log-analytics/log-analytics-data-sources.md) that you configure.
 - Application data collected by [Application Insights](https://docs.microsoft.com/azure/application-insights/).
-- Data providing insights into a particular application or service from [monitoring solutions](../../monitoring/../../azure-monitor/insights/solutions.md) or features such as Container Insights, VM Insights, or Resource Group Insights.
+- Data providing insights into a particular application or service from [monitoring solutions](../insights/solutions.md) or features such as Container Insights, VM Insights, or Resource Group Insights.
 - Security data collected by [Azure Security Center](https://docs.microsoft.com/azure/security-center/).
 - [Metrics](#metrics) from Azure resources. This allows you to store metrics for longer than 93 days and to analyze it with other log data.
 - Telemetry written to [Azure Storage](../../log-analytics/log-analytics-azure-storage-iis-table.md).

articles/azure-monitor/platform/data-sources.md

@@ -77,7 +77,7 @@ With the Azure Diagnostics extension, it provides a basic level of monitoring by
 Comprehensive monitoring and management of your Windows or Linux virtual machines or physical computer is delivered with the Log Analytics agent. The virtual machine can be running in Azure, another cloud, or on-premises and the agent connects to Log Analytics either directly or through System Center Operations Manager and allows you to collect data from [data sources](../../log-analytics/log-analytics-data-sources.md) that you configure or from [monitoring solutions](../../azure-monitor/insights/solutions.md) that provide additional insights into applications running on the virtual machine.
 
 ### Dependency agent
-[Service Map](../../monitoring/service-map.md) and [Azure Monitor for VMs](../../azure-monitor/insights/vminsights-overview.md) requires a Dependency Agent on Windows and Linux virtual machines. This integrates with the Log Analytics agent to collects discovered data about processes running on the virtual machine and external process dependencies. It stores this data in Log Analytics and visualizes the discovered interconnected components.  
+[Service Map](../insights/service-map.md) and [Azure Monitor for VMs](../../azure-monitor/insights/vminsights-overview.md) requires a Dependency Agent on Windows and Linux virtual machines. This integrates with the Log Analytics agent to collects discovered data about processes running on the virtual machine and external process dependencies. It stores this data in Log Analytics and visualizes the discovered interconnected components.  
 
 To further understand the differences between the agents and which to use depending on your monitoring requirements, see [monitoring agents overview](agents-overview.md).
 

articles/azure-monitor/platform/runbook-datacollect.md

@@ -52,7 +52,7 @@ The PowerShell Gallery though gives you a quick option to deploy a module direct
 
 
 ## 2. Create Automation variables
-[Automation variables](..\automation\automation-variables.md) hold values that can be used by all runbooks in your Automation account.  They make runbooks more flexible by allowing you to change these values without editing the actual runbook. Every request from the HTTP Data Collector API requires the ID and key of the Log Analytics workspace, and variable assets are ideal to store this information.  
+[Automation variables](../../automation/automation-variables.md) hold values that can be used by all runbooks in your Automation account.  They make runbooks more flexible by allowing you to change these values without editing the actual runbook. Every request from the HTTP Data Collector API requires the ID and key of the Log Analytics workspace, and variable assets are ideal to store this information.  
 
 ![Variables](media/runbook-datacollect/variables.png)
 

articles/operations-management-suite/TOC.md

@@ -65,7 +65,7 @@
 ### [Best practices](../azure-monitor/insights/solutions-best-practices.md)
 
 ## Management scenarios
-### [Collect analytics data from runbook](../azure-monitor/insights/runbook-datacollect.md?toc=%2fazure%2foperations-management-suite%2ftoc.json)
+### [Collect analytics data from runbook](../azure-monitor/platform/runbook-datacollect.md?toc=%2fazure%2foperations-management-suite%2ftoc.json)
 
 # Resources
 ## [Azure Roadmap](https://azure.microsoft.com/roadmap/)