Step 2: Document your current configuration
It's important to document your current configuration to make sure that your configuration remains consistent after the migration. Note the information for each workspace in your environment from the Azure portal regarding the data that you're collecting.
Data collections configured in the workspace
To see which legacy data collections are configured in the Log Analytics workspace, follow these steps:
In the Azure portal, search for and select Log Analytics workspaces.
In the list of Log Analytics workspaces, select the name of your workspace.
In the menu pane of your Log Analytics workspace, select Classic > Legacy agents management. On the Legacy agents management page, you can see the different types of data sources that the workspace can collect.
Select one of the following tabs based on the type of legacy data collection that you want to check.
Windows event logs
Windows performance counters
Linux performance counters
Syslog
IIS Logs
On the corresponding tab, view the list of data sources that are currently enabled for the workspace. Now is an excellent time to review your data collection configuration and sample rate to optimize your configuration.
You can also add, remove, or edit the data sources as necessary.
Legacy solutions configured
To see which legacy solutions are added to your Log Analytics workspace:
- Navigate to the Azure portal
- View your Log Analytics workspaces
- Select your workspace, and then go to the Legacy Solutions section.
Some legacy solutions might require extra steps to enable data collection. Examples of these steps include the following actions:
- Installing agents
- Configuring diagnostics
- Enabling features
The following table describes the features that you might have to enable.
| Service or feature | Migration path |
|---|---|
| System Center Operations Manager | If you use Operations Manager to monitor your Windows or Linux virtual machines (VMs), continue to use Microsoft Monitoring Agent for Operations Manager agent management. However, you have to install Azure Monitor Agent separately to send data to Azure Monitor. You can run both agents side by side on the same VM if they're configured to use different ports. |
| Azure Automation Change Tracking and Inventory | If you use Change Tracking and Inventory to track configuration changes and software inventory on your VMs, you have to migrate to the current version of the solution. This version uses Azure Monitor Agent instead of Microsoft Monitoring Agent. To do this, remove the legacy solution from your workspace, install Azure Monitor Agent on your VMs, and then add the current solution to your workspace. |
| Azure Automation Update Management | If you use Update Management to manage updates on your VMs, you have to migrate to the current version of the solution. This version uses Azure Monitor Agent instead of Microsoft Monitoring Agent. To do this, remove the legacy solution from your workspace, install Azure Monitor Agent on your VMs, and then add the current solution to your workspace. |
| Azure Security Center | If you use Azure Security Center to protect your VMs from threats and vulnerabilities, you have to migrate to the current version of the service. This version uses Azure Monitor Agent instead of Microsoft Monitoring Agent. To do this, enable the Azure Monitor Agent data collection option in Azure Security Center, install Azure Monitor Agent on your VMs, and then disable the Microsoft Monitoring Agent data collection option. |
| Azure Automation Hybrid Runbook Worker | If you use Azure Automation Hybrid Runbook Worker to run automation runbooks on your VMs, you can continue to use Microsoft Monitoring Agent for this feature. However, you have to install Azure Monitor Agent separately to send data to Azure Monitor. You can run both agents side-by-side on the same VM if they're configured to use different ports. |
| Microsoft Sentinel | If you use Microsoft Sentinel to collect and analyze security data from your VMs, you have to migrate to the current version of the service. This version uses Azure Monitor Agent instead of Microsoft Monitoring Agent. To do this, you have to install Azure Monitor Agent on your VMs, configure the data sources and connectors for Microsoft Sentinel, and then remove Microsoft Monitoring Agent from your VMs. |
You can also use the Azure Monitor Agent Migration Helper workbook to analyze the added legacy solutions. To use the workbook, go to Monitor > Workbooks > AMA Migration Helper in the Azure portal, and then select the Workspaces tab. You can now select the workspace that you want to check. Then, check the Solutions tab:
The workbook displays a table that contains the following columns:
- Solution
- Last Data Received
- Recommendation
Next steps
Contact us for help
If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.