Skip to content

Commit 6725eb9

Browse files
Update defender-for-apis-deploy.md
1 parent 75f2e41 commit 6725eb9

File tree

1 file changed

+27
-27
lines changed

1 file changed

+27
-27
lines changed

articles/defender-for-cloud/defender-for-apis-deploy.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,33 @@ To select the best plan for your subscription from the Microsoft Defender for Cl
6060
1. Select the plan that is suitable for your subscription.
6161
1. Select **Save**.
6262

63+
## Selecting the optimal plan based on historical Azure API Management API traffic usage
64+
65+
You must select a plan that grants entitlement appropriate for the API traffic volume in your subscription to receive the most optimal pricing. By default, subscriptions are opted into **Plan 1**, which can lead to unexpected overages if your subscription has API traffic higher than the [one million API calls entitlement](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/18).
66+
67+
**To estimate the monthly API traffic in Azure API Management:**
68+
69+
1. Navigate to the Azure API Management portal and select **Metrics** under the Monitoring menu bar item.
70+
71+
:::image type="content" source="media/defender-for-apis-entitlement-plans/select-metrics.png" alt-text="Screenshot that shows where to select metrics." lightbox="media/defender-for-apis-entitlement-plans/select-metrics.png":::
72+
73+
1. Select the time range as **Last 30 days**.
74+
1. Select and set the following parameters:
75+
76+
1. Scope: **Azure API Management Service Name**
77+
1. Metric Namespace: **API Management service standard metrics**
78+
1. Metric = **Requests**
79+
1. Aggregation = **Sum**
80+
81+
1. After setting the above parameters, the query will automatically run, and the total number of requests for the past 30 days appears at the bottom of the screen. Iin the screenshot example, the query results in 414 total number of requests.
82+
83+
:::image type="content" source="media/defender-for-apis-entitlement-plans/metrics-results.png" alt-text="Screenshot that shows metrics results." lightbox="media/defender-for-apis-entitlement-plans/metrics-results.png":::
84+
85+
> [!NOTE]
86+
> These instructions are for calculating the usage per Azure API management service. To calculate the estimated traffic usage for *all* API management services within the Azure subscription, change the **Scope** parameter to each Azure API management service within the Azure subscription, re-run the query, and sum the query results.
87+
88+
If you don't have access to run the metrics query, reach out to your internal Azure API Management administrator or your Microsoft account manager.
89+
6390
> [!NOTE]
6491
> After enabling Defender for APIs, onboarded APIs take up to 50 minutes to appear in the **Recommendations** tab. Security insights are available in the **Workload protections** > **API security** dashboard within 40 minutes of onboarding.
6592
@@ -90,33 +117,6 @@ To select the best plan for your subscription from the Microsoft Defender for Cl
90117

91118
:::image type="content" source="media/defender-for-apis-deploy/fix-resources-confirm.png" alt-text="Screenshot that confirms that remediation was successful." lightbox="media/defender-for-apis-deploy/fix-resources-confirm.png":::
92119

93-
## Selecting the optimal plan based on historical Azure API Management API traffic usage
94-
95-
You must select a plan that grants entitlement appropriate for the API traffic volume in your subscription to receive the most optimal pricing. By default, subscriptions are opted into **Plan 1**, which can lead to unexpected overages if your subscription has API traffic higher than the [one million API calls entitlement](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/18).
96-
97-
**To estimate the monthly API traffic in Azure API Management:**
98-
99-
1. Navigate to the Azure API Management portal and select **Metrics** under the Monitoring menu bar item.
100-
101-
:::image type="content" source="media/defender-for-apis-entitlement-plans/select-metrics.png" alt-text="Screenshot that shows where to select metrics." lightbox="media/defender-for-apis-entitlement-plans/select-metrics.png":::
102-
103-
1. Select the time range as **Last 30 days**.
104-
1. Select and set the following parameters:
105-
106-
1. Scope: **Azure API Management Service Name**
107-
1. Metric Namespace: **API Management service standard metrics**
108-
1. Metric = **Requests**
109-
1. Aggregation = **Sum**
110-
111-
1. After setting the above parameters, the query will automatically run, and the total number of requests for the past 30 days appears at the bottom of the screen. Iin the screenshot example, the query results in 414 total number of requests.
112-
113-
:::image type="content" source="media/defender-for-apis-entitlement-plans/metrics-results.png" alt-text="Screenshot that shows metrics results." lightbox="media/defender-for-apis-entitlement-plans/metrics-results.png":::
114-
115-
> [!NOTE]
116-
> These instructions are for calculating the usage per Azure API management service. To calculate the estimated traffic usage for *all* API management services within the Azure subscription, change the **Scope** parameter to each Azure API management service within the Azure subscription, re-run the query, and sum the query results.
117-
118-
If you don't have access to run the metrics query, reach out to your internal Azure API Management administrator or your Microsoft account manager.
119-
120120
## Track onboarded API resources
121121

122122
After onboarding the API resources, you can track their status in the Defender for Cloud portal > **Workload protections** > **API security**:

0 commit comments

Comments
 (0)