Skip to content

Commit 8323be8

Browse files
authored
Merge pull request #194347 from bmansheim/add-regions-solution-targeting
Add regions that support solution targeting
2 parents 8d7a059 + dd4f7ee commit 8323be8

File tree

1 file changed

+46
-3
lines changed

1 file changed

+46
-3
lines changed

articles/defender-for-cloud/enhanced-security-features-overview.md

Lines changed: 46 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22
title: Understand the enhanced security features of Microsoft Defender for Cloud
33
description: Learn about the benefits of enabling enhanced security in Microsoft Defender for Cloud
44
ms.topic: overview
5-
ms.author: elkrieger
6-
author: ElazarK
7-
ms.date: 02/24/2022
5+
ms.date: 04/11/2022
6+
ms.author: benmansheim
7+
ms.custom: references_regions
8+
author: bmansheim
89
---
910

1011
# Microsoft Defender for Cloud's enhanced security features
@@ -139,3 +140,45 @@ This article explained Defender for Cloud's pricing options. For related materia
139140
- [How to optimize your Azure workload costs](https://azure.microsoft.com/blog/how-to-optimize-your-azure-workload-costs/)
140141
- [Pricing details according to currency or region](https://azure.microsoft.com/pricing/details/defender-for-cloud/)
141142
- You may want to manage your costs and limit the amount of data collected for a solution by limiting it to a particular set of agents. Use [solution targeting](../azure-monitor/insights/solution-targeting.md) to apply a scope to the solution and target a subset of computers in the workspace. If you're using solution targeting, Defender for Cloud lists the workspace as not having a solution.
143+
> [!IMPORTANT]
144+
> Solution targeting has been deprecated because the Log Analytics agent is being replaced with the Azure Monitor agent and solutions in Azure Monitor are being replaced with insights. You can continue to use solution targeting if you already have it configured, but it is not available in new regions.
145+
> The feature will not be supported after August 31, 2024.
146+
> Regions that support solution targeting until the deprecation date are:
147+
>
148+
> | Region code | Region name |
149+
> | :--- | :---------- |
150+
> | CCAN | canadacentral |
151+
> | CHN | switzerlandnorth |
152+
> | CID | centralindia |
153+
> | CQ | brazilsouth |
154+
> | CUS | centralus |
155+
> | DEWC | germanywestcentral |
156+
> | DXB | UAENorth |
157+
> | EA | eastasia |
158+
> | EAU | australiaeast |
159+
> | EJP | japaneast |
160+
> | EUS | eastus |
161+
> | EUS2 | eastus2 |
162+
> | NCUS | northcentralus |
163+
> | NEU | NorthEurope |
164+
> | NOE | norwayeast |
165+
> | PAR | FranceCentral |
166+
> | SCUS | southcentralus |
167+
> | SE | KoreaCentral |
168+
> | SEA | southeastasia |
169+
> | SEAU | australiasoutheast |
170+
> | SUK | uksouth |
171+
> | WCUS | westcentralus |
172+
> | WEU | westeurope |
173+
> | WUS | westus |
174+
> | WUS2 | westus2 |
175+
>
176+
> | Air-gapped clouds | Region code | Region name |
177+
> | :---- | :---- | :---- |
178+
> | UsNat | EXE | usnateast |
179+
> | UsNat | EXW | usnatwest |
180+
> | UsGov | FF | usgovvirginia |
181+
> | China | MC | ChinaEast2 |
182+
> | UsGov | PHX | usgovarizona |
183+
> | UsSec | RXE | usseceast |
184+
> | UsSec | RXW | ussecwest |

0 commit comments

Comments
 (0)