Skip to content

Commit 2d37363

Browse files
Merge pull request #49239 from rakgurram-MSFT/patch-20
(AzureCXP)Update 3-how-azure-advisor-works.md
2 parents 5706d10 + 4283251 commit 2d37363

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/azure/intro-to-azure-advisor/includes/3-how-azure-advisor-works.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ You need to define a scope by selecting a subscription and, optionally, a resour
3737

3838
Alerts are driven by conditions. Here you have two mutually exclusive options:
3939

40-
* **Category and impact level**: In this option, you can choose between the categories of *Cost*, *Performance*, *Reliability*, and *Operational excellence*, with an impact level of (*High*, *Medium*, or *Low*). Both of these are optional configurations.
40+
* **Category and impact level**: In this option, you can choose between the categories of *Cost*, *Security*, *Performance*, *Reliability*, and *Operational excellence*, with an impact level of (*High*, *Medium*, or *Low*). Both of these are optional configurations.
4141
* **Recommendation Type**: If you select recommendation type, you can choose the most appropriate option for your needs from the dropdown list.
4242

4343
:::image type="content" source="../media/3-create-alerts-scope-condition.png" alt-text="Screenshot showing the scope and condition sections of the dialog for creating an Advisor alert." lightbox="../media/3-create-alerts-scope-condition.png":::

0 commit comments

Comments
 (0)