Merge pull request #109642 from memildin/asc-melvyn-anh

Replaced "Microsoft Monitoring Agent" and "MMA" with updated names

Author: ShannonLeavitt

articles/security-center/faq-azure-monitor-logs.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Security Center FAQ - questions about existing MMAs
-description: This FAQ answers questions for customers already using the Microsoft Monitoring Agent and considering Azure Security Center, a product that helps you prevent, detect, and respond to threats.
+title: Azure Security Center FAQ - questions about existing Log Analytics agents
+description: This FAQ answers questions for customers already using the Log Analytics agent and considering Azure Security Center, a product that helps you prevent, detect, and respond to threats.
 services: security-center
 documentationcenter: na
 author: memildin
@@ -20,12 +20,12 @@ ms.author: memildin
 
 ## Does Security Center override any existing connections between VMs and workspaces?
 
-If a VM already has the Microsoft Monitoring Agent installed as an Azure extension, Security Center does not override the existing workspace connection. Instead, Security Center uses the existing workspace. The VM will be protected provided that the "Security" or "SecurityCenterFree" solution has been installed on the workspace to which it is reporting. 
+If a VM already has the Log Analytics agent installed as an Azure extension, Security Center does not override the existing workspace connection. Instead, Security Center uses the existing workspace. The VM will be protected provided that the "Security" or "SecurityCenterFree" solution has been installed on the workspace to which it is reporting. 
 
 A Security Center solution is installed on the workspace selected in the Data Collection screen if not present already, and the solution is applied only to the relevant VMs. When you add a solution, it's automatically deployed by default to all Windows and Linux agents connected to your Log Analytics workspace. [Solution Targeting](../operations-management-suite/operations-management-suite-solution-targeting.md) allows you to apply a scope to your solutions.
 
 > [!TIP]
-> If the Microsoft Monitoring Agent is installed directly on the VM (not as an Azure extension), Security Center does not install the Microsoft Monitoring Agent, and security monitoring is limited.
+> If the Log Analytics agent is installed directly on the VM (not as an Azure extension), Security Center does not install the Log Analytics agent, and security monitoring is limited.
 
 ## Does Security Center install solutions on my existing Log Analytics workspaces? What are the billing implications?
 When Security Center identifies that a VM is already connected to a workspace you created, Security Center enables solutions on this workspace according to your pricing tier. The solutions are applied only to the relevant Azure VMs, via [solution targeting](../operations-management-suite/operations-management-suite-solution-targeting.md), so the billing remains the same.
@@ -36,9 +36,9 @@ When Security Center identifies that a VM is already connected to a workspace yo
    ![Solutions on default workspace](./media/security-center-platform-migration-faq/solutions.png)
 
 ## I already have workspaces in my environment, can I use them to collect security data?
-If a VM already has the Microsoft Monitoring Agent installed as an Azure extension, Security Center uses the existing connected workspace. A Security Center solution is installed on the workspace if not present already, and the solution is applied only to the relevant VMs via [solution targeting](../operations-management-suite/operations-management-suite-solution-targeting.md).
+If a VM already has the Log Analytics agent installed as an Azure extension, Security Center uses the existing connected workspace. A Security Center solution is installed on the workspace if not present already, and the solution is applied only to the relevant VMs via [solution targeting](../operations-management-suite/operations-management-suite-solution-targeting.md).
 
-When Security Center installs the Microsoft Monitoring Agent on VMs, it uses the default workspace(s) created by Security Center.
+When Security Center installs the Log Analytics agent on VMs, it uses the default workspace(s) created by Security Center.
 
 ## I already have security solution on my workspaces. What are the billing implications?
 The Security & Audit solution is used to enable Security Center standard tier features for Azure VMs. If the Security & Audit solution is already installed on a workspace, Security Center uses the existing solution. There is no change in billing.

articles/security-center/faq-data-collection-agents.md

@@ -21,7 +21,7 @@ ms.author: memildin
 ## What is Azure Security Center?
 Azure Security Center helps you prevent, detect, and respond to threats with increased visibility into and control over the security of your resources. It provides integrated security monitoring and policy management across your subscriptions, helps detect threats that might otherwise go unnoticed, and works with a broad ecosystem of security solutions.
 
-Security Center uses the Microsoft Monitoring Agent to collect and store data. For in-depth details, see [Data collection in Azure Security Center](security-center-enable-data-collection.md).
+Security Center uses the Log Analytics agent to collect and store data. For in-depth details, see [Data collection in Azure Security Center](security-center-enable-data-collection.md).
 
 
 ## How do I get Azure Security Center?

articles/security-center/faq-general.md

@@ -48,7 +48,7 @@ Below are the latency times for Security Center scans of vulnerabilities, update
 Security Center typically scans for new data every hour, and refreshes the recommendations accordingly. 
 
 > [!NOTE]
-> Security Center uses the Microsoft Monitoring Agent to collect and store data. To learn more, see [Azure Security Center Platform Migration](security-center-platform-migration.md).
+> Security Center uses the Log Analytics agent to collect and store data. To learn more, see [Azure Security Center Platform Migration](security-center-platform-migration.md).
 
 
 ## Why do I get the message "VM Agent is Missing?"

articles/security-center/faq-vms.md

@@ -18,14 +18,14 @@ ms.author: memildin
 
 ---
 # Quickstart: Onboard Linux computers to Azure Security Center
-After you onboard your Azure subscriptions, you can enable Security Center for Linux resources running outside of Azure, for example on-premises or in other clouds, by provisioning an Agent. The Agent is called the Microsoft Monitoring Agent (MMA), but it is also known as the OMS agent.
+After you onboard your Azure subscriptions, you can enable Security Center for Linux resources running outside of Azure, for example on-premises or in other clouds, by provisioning an Agent. The Agent is called the Log Analytics agent, but it is also known as the OMS agent.
 
 This quickstart shows you how to install the Agent on a Linux computer.
 
 ## Prerequisites
 To get started with Security Center, you must have a subscription to Microsoft Azure. If you do not have a subscription, you can sign up for a [free account](https://azure.microsoft.com/pricing/free-trial/).
 
-You must be on Security Center’s Standard pricing tier before starting this quickstart. See [Onboard your Azure subscription to Security Center Standard](security-center-get-started.md) for upgrade instructions. You can try Security Center’s Standard at no cost. To learn more, see the [pricing page](https://azure.microsoft.com/pricing/details/security-center/).
+You must be on Security Center's Standard pricing tier before starting this quickstart. See [Onboard your Azure subscription to Security Center Standard](security-center-get-started.md) for upgrade instructions. You can try Security Center's Standard at no cost. To learn more, see the [pricing page](https://azure.microsoft.com/pricing/details/security-center/).
 
 ## Add new Linux computer
 

articles/security-center/quick-onboard-linux-computer.md

@@ -1,6 +1,6 @@
 ---
 title: Onboard Windows computers to Azure Security Center
-description: This quickstart shows you how to provision the Microsoft Monitoring Agent on a Windows computer.
+description: This quickstart shows you how to provision the Log Analytics agent on a Windows computer.
 services: security-center
 documentationcenter: na
 author: memildin
@@ -18,9 +18,9 @@ ms.author: memildin
 
 ---
 # Quickstart: Onboard Windows computers to Azure Security Center
-After you onboard your Azure subscriptions, you can enable Security Center for resources running outside of Azure, for example on-premises or in other clouds, by provisioning the Microsoft Monitoring Agent.
+After you onboard your Azure subscriptions, you can enable Security Center for resources running outside of Azure, for example on-premises or in other clouds, by provisioning the Log Analytics agent.
 
-This quickstart shows you how to install the Microsoft Monitoring Agent on a Windows computer.
+This quickstart shows you how to install the Log Analytics agent on a Windows computer.
 
 ## Prerequisites
 To get started with Security Center, you must have a subscription to Microsoft Azure. If you do not have a subscription, you can sign up for a [free account](https://azure.microsoft.com/pricing/free-trial/).
@@ -68,7 +68,7 @@ You must now install the downloaded file on the target computer.
 9. On the **Ready to Install** page, review your choices and then select **Install**.
 10. On the **Configuration completed successfully** page, select **Finish**
 
-When complete, the **Microsoft Monitoring Agent** appears in **Control Panel**. You can review your configuration there and verify that the agent is connected.
+When complete, the **Log Analytics agent** appears in **Control Panel**. You can review your configuration there and verify that the agent is connected.
 
 For further information on installing and configuring the agent, see [Connect Windows computers](../azure-monitor/platform/agent-windows.md#install-the-agent-using-setup-wizard).
 
@@ -89,10 +89,10 @@ To remove the agent:
 
 1. Open **Control Panel**.
 2. Open **Programs and Features**.
-3. In **Programs and Features**, select **Microsoft Monitoring Agent** and click **Uninstall**.
+3. In **Programs and Features**, select **Log Analytics agent** and click **Uninstall**.
 
 ## Next steps
-In this quickstart, you provisioned the Microsoft Monitoring Agent on a Windows computer. To learn more about how to use Security Center, continue to the tutorial for configuring a security policy and assessing the security of your resources.
+In this quickstart, you provisioned the Log Analytics agent on a Windows computer. To learn more about how to use Security Center, continue to the tutorial for configuring a security policy and assessing the security of your resources.
 
 > [!div class="nextstepaction"]
 > [Tutorial: Define and assess security policies](tutorial-security-policy.md)

articles/security-center/quick-onboard-windows-computer.md

@@ -66,8 +66,8 @@ Machine artifacts are stored centrally in the same region as the VM.
 
 ## Managing data collection from virtual machines
 
-When you enable Security Center in Azure, data collection is turned on for each of your Azure subscriptions. You can also turn on data collection for your subscriptions in the Security Policy section of Azure Security Center. When Data collection is turned on, Azure Security Center provisions the Microsoft Monitoring Agent on all existing supported Azure virtual machines and any new ones that are created.
-The Microsoft Monitoring agent scans for various security-related configurations and events it into [Event Tracing for Windows](https://msdn.microsoft.com/library/windows/desktop/bb968803.aspx) (ETW) traces. In addition, the operating system will raise event log events during the course of running the machine. Examples of such data are: operating system type and version, operating system logs (Windows event logs), running processes, machine name, IP addresses, logged in user, and tenant ID. The Microsoft Monitoring Agent reads event log entries and ETW traces and copies them to your workspace(s) for analysis. The Microsoft Monitoring Agent also copies crash dump files to your workspace(s), enable process creation events, and enable command line auditing.
+When you enable Security Center in Azure, data collection is turned on for each of your Azure subscriptions. You can also turn on data collection for your subscriptions in the Security Policy section of Azure Security Center. When Data collection is turned on, Azure Security Center provisions the Log Analytics agent on all existing supported Azure virtual machines and any new ones that are created.
+The Log Analytics agent scans for various security-related configurations and events it into [Event Tracing for Windows](https://msdn.microsoft.com/library/windows/desktop/bb968803.aspx) (ETW) traces. In addition, the operating system will raise event log events during the course of running the machine. Examples of such data are: operating system type and version, operating system logs (Windows event logs), running processes, machine name, IP addresses, logged in user, and tenant ID. The Log Analytics agent reads event log entries and ETW traces and copies them to your workspace(s) for analysis. The Log Analytics agent also copies crash dump files to your workspace(s), enable process creation events, and enable command line auditing.
 
 If you are using Azure Security Center Free, you can also disable data collection from virtual machines in the Security Policy. Data Collection is required for subscriptions on the Standard tier. VM disk snapshots and artifact collection will still be enabled even if data collection has been disabled.
 

articles/security-center/security-center-data-security.md

@@ -304,7 +304,7 @@ You can manually install the Log Analytics Agent, so Security Center can collect
 
 - To identify Unmonitored VMs and computers issues:
 
-    A VM or computer is unmonitored by Security Center if the machine is not running the Microsoft Monitoring Agent extension. A machine may have a local agent already installed, for example the OMS direct agent or the System Center Operations Manager agent. Machines with these agents are identified as unmonitored because these agents are not fully supported in Security Center. To fully benefit from all of Security Center’s capabilities, the Microsoft Monitoring Agent extension is required.
+    A VM or computer is unmonitored by Security Center if the machine is not running the Log Analytics agent extension. A machine may have a local agent already installed, for example the OMS direct agent or the System Center Operations Manager agent. Machines with these agents are identified as unmonitored because these agents are not fully supported in Security Center. To fully benefit from all of Security Center’s capabilities, the Log Analytics agent extension is required.
 
     For more information about the reasons Security Center is unable to successfully monitor VMs and computers initialized for automatic provisioning, see [Monitoring agent health issues](security-center-troubleshooting-guide.md#mon-agent).
 

articles/security-center/security-center-enable-data-collection.md

@@ -39,7 +39,7 @@ This article provides detailed information for each retired feature and the step
 
 ## Events dashboard<a name="menu_events"></a>
 
-Security Center uses Microsoft Monitoring Agent to collect various security-related configurations and events from your machines. It stores these events in your workspaces. The [events dashboard](https://docs.microsoft.com/azure/security-center/security-center-events-dashboard) lets you view this data and gives you an entry point to Log Analytics.
+Security Center uses Log Analytics agent to collect various security-related configurations and events from your machines. It stores these events in your workspaces. The [events dashboard](https://docs.microsoft.com/azure/security-center/security-center-events-dashboard) lets you view this data and gives you an entry point to Log Analytics.
 
 We retired the events dashboard that appeared when you selected a workspace: