Skip to content

Commit ba2a618

Browse files
fixing last issues
1 parent 1c88fc4 commit ba2a618

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article describes how to deploy the [Microsoft Defender for APIs](defender-
1818
- Ensure that APIs you want to secure are published in [Azure API management](/azure/api-management/api-management-key-concepts). Follow [these instructions](/azure/api-management/get-started-create-service-instance) to set up Azure API Management.
1919

2020
> [!NOTE]
21-
> This article describes how to enable and onboard the Defender for APIs plan in the Defender for Cloud portal. Alternately, you can enable Defender for APIs within an API Management instance in the Azure portal.
21+
> This article describes how to enable and onboard the Defender for APIs plan in the Defender for Cloud portal. Alternately, you can [enable Defender for APIs within an API Management instance](../api-management/protect-with-defender-for-apis.md) in the Azure portal.
2222
2323
## Enable the plan
2424

@@ -29,7 +29,7 @@ This article describes how to deploy the [Microsoft Defender for APIs](defender-
2929
:::image type="content" source="media/defender-for-apis-deploy/enable-plan.png" alt-text="Shows how to turn on the Defender for APIs plan in the portal" lightbox="media/defender-for-apis-deploy/enable-plan.png":::
3030

3131
> [!NOTE]
32-
> After enabling Defender for APIs, onboarded APIs take up to 45 minutes to appear in the **Recommendations** tab. Security insights are available in the **Workload protections** > **API security** dashboard within 30 minutes of onboarding.
32+
> 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.
3333
3434
## Onboard APIs
3535

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,15 +41,16 @@ Multi-region support | In multi-region Azure API Management instances, some ML-b
4141
To explore API security risks using Cloud Security Explorer, the Defender Cloud Security Posture Management (CSPM) plan must be enabled. [Learn more](concept-cloud-security-posture-management.md).
4242

4343

44-
## Deployment requirement
44+
## Onboarding requirements
4545

46-
Deployment requirements for Defender for APIs are as follows.
46+
Onboarding requirements for Defender for APIs are as follows.
4747

4848
**Requirement** | **Details**
4949
--- | ---
5050
API Management instance | At least one API Management instance in an Azure subscription. Defender for APIs is enabled at the level of a subscription.<br/><br/> One or more supported APIs must be imported to the API Management instance.
5151
Azure account | You need an Azure account to sign into the Azure portal.
5252
Onboarding permissions | To enable and onboard Defender for APIs, you need the Owner or Contributor role on the Azure subscriptions, resource groups, or Azure API Management instance that you want to secure. If you don't have the Contributor role, you need to enable these roles:<br/><br/> - Security Admin role for full access in Defender for Cloud.<br/> - Security Reader role to view inventory and recommendations in Defender for Cloud.
53+
Onboarding location | You can [enable Defender for APIs in the Defender for Cloud portal](defenderf-for-apis-deploy.md), or in the [Azure API Management portal](../api-management/protect-with-defender-for-apis.md).
5354

5455
## Next steps
5556

0 commit comments

Comments
 (0)