Merge pull request #231014 from memildin/patch-68

Wrong names for our own products

Author: prmerger-automator[bot]

articles/defender-for-cloud/upcoming-changes.md

@@ -19,7 +19,7 @@ If you're looking for the latest release notes, you'll find them in the [What's
 | Planned change | Estimated date for change |
 |--|--|
 | [Changes in the recommendation "Machines should be configured securely"](#changes-in-the-recommendation-machines-should-be-configured-securely) | March 2023 |
-| [Three alerts in Defender for Azure Resource Manager plan will be deprecated](#three-alerts-in-defender-for-azure-resource-manager-plan-will-be-deprecated) | March 2023 |
+| [Three alerts in the Defender for Resource Manager plan will be deprecated](#three-alerts-in-the-defender-for-resource-manager-plan-will-be-deprecated) | March 2023 |
 | [Alerts automatic export to Log Analytics workspace will be deprecated](#alerts-automatic-export-to-log-analytics-workspace-will-be-deprecated) | March 2023 |
 | [Deprecation and improvement of selected alerts for Windows and Linux Servers](#deprecation-and-improvement-of-selected-alerts-for-windows-and-linux-servers) | April 2023 |
 | [Deprecation of App Service language monitoring policies](#deprecation-of-app-service-language-monitoring-policies) | April 2023 |
@@ -29,31 +29,31 @@ If you're looking for the latest release notes, you'll find them in the [What's
 
 **Estimated date for change: March 2023**
 
-The recommendation `Machines should be configured securely` is set to be updated. This update will improve the performance and stability of the recommendation and align its experience with the generic behavior of Defender for Cloud's recommendations.
+The recommendation `Machines should be configured securely` will be updated. The update will improve the performance and stability of the recommendation and align its experience with the generic behavior of Defender for Cloud's recommendations.
 
 As part of this update, the recommendation's ID will be changed from `181ac480-f7c4-544b-9865-11b8ffe87f47` to `c476dc48-8110-4139-91af-c8d940896b98`.
 
 No action is required on the customer side, and there's no expected downtime nor impact on the secure score.
 
 
-### Three alerts in Defender for Azure Resource Manager plan will be deprecated
+### Three alerts in the Defender for Resource Manager plan will be deprecated
 
 **Estimated date for change: March 2023**
 
-As we continue to improve the quality of our alerts, the following three alerts from the Defender for Azure Resource Manager plan will be deprecated:
+As we continue to improve the quality of our alerts, the following three alerts from the Defender for Resource Manager plan will be deprecated:
 1. `Activity from a risky IP address (ARM.MCAS_ActivityFromAnonymousIPAddresses)`
 1. `Activity from infrequent country (ARM.MCAS_ActivityFromInfrequentCountry)`
 1. `Impossible travel activity (ARM.MCAS_ImpossibleTravelActivity)`
 
 You can learn more details about each of these alerts from the [alerts reference list](alerts-reference.md#alerts-resourcemanager).
 
-In the scenario where an activity from a suspicious IP address is detected, one of the following Defenders for Azure Resource Manager plan alerts `Azure Resource Manager operation from suspicious IP address` or `Azure Resource Manager operation from suspicious proxy IP address` will be present.
+In the scenario where an activity from a suspicious IP address is detected, one of the following Defenders for Resource Manager plan alerts `Azure Resource Manager operation from suspicious IP address` or `Azure Resource Manager operation from suspicious proxy IP address` will be present.
 
 ### Alerts automatic export to Log Analytics workspace will be deprecated
 
 **Estimated date for change: March 2023**
 
-Currently, Defenders for Cloud security alerts are automatically exported to a default Log Analytics workspace on the resource level. This causes an indeterministic behavior and therefore, this feature is set to be deprecated.
+Currently, Defender for Cloud security alerts are automatically exported to a default Log Analytics workspace on the resource level. This causes an indeterministic behavior and therefore, this feature is set to be deprecated.
 
 You can export your security alerts to a dedicated Log Analytics workspace with the [Continuous Export](continuous-export.md#set-up-a-continuous-export) feature. 
 If you have already configured continuous export of your alerts to a Log Analytics workspace, no further action is required.
@@ -68,7 +68,7 @@ If you already have the Defender for Endpoint integration enabled, no further ac
 
 If you don't have the Defender for Endpoint integration enabled in Defender for Servers, you'll need to enable the Defender for Endpoint integration to maintain and improve your alert coverage. 
 
-All Defender for Server customers, have full access to the Defender for Endpoint’s integration as a part of the [Defender for Servers plan](plan-defender-for-servers-select-plan.md#plan-features).  
+All Defender for Servers customers, have full access to the Defender for Endpoint’s integration as a part of the [Defender for Servers plan](plan-defender-for-servers-select-plan.md#plan-features).  
 
 You can learn more about [Microsoft Defender for Endpoint onboarding options](integration-defender-for-endpoint.md#enable-the-microsoft-defender-for-endpoint-integration).
 
@@ -90,7 +90,7 @@ The following App Service language monitoring policies are set to be deprecated
 
 Customers can use alternative built-in policies to monitor any specified language version for their App Services. 
 
-Defender for Cloud won't include these recommendations as built-in recommendations. You can add them as custom recommendations to have Defender for Cloud monitor them.
+These will no longer be in Defender for Cloud's built-in recommendations. You can add them as custom recommendations to have Defender for Cloud monitor them.
 
 ### Multiple changes to identity recommendations