Define Playbook Access Restrictions
In brief
The documentation now lists separate navigation paths for Microsoft Sentinel in the Defender portal and the ISOC main navigation menu, while retaining the Azure portal path.
What Defender admins need to know
Administrators can use the path matching their package to locate the Automation page.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Perform the following steps to define an access restriction policy for a Standard-plan playbook.
Note
To open the automation page in the Microsoft Defender portal, use the path for your package:
- In Microsoft Sentinel in the Defender portal: Microsoft Sentinel > Configuration > Automation.
- In ISOC main navigation menu: Automation.
For Microsoft Sentinel in the Azure portal, select the Configuration > Automation page.
For Microsoft Sentinel in the Defender portal, selectMicrosoft Sentinel>Configuration>Automation.On the Automation page, select the Active playbooks tab.
Filter the list for Standard-plan apps. Select the Plan filter and clear the Consumption checkbox, and then select OK. For example:
@@ -44,13 +44,13 @@ monikers: [] item_type: Content source_path: sentinel/automation/define-playbook-access-restrictions.md cmProducts:+- https://authoring-docs-microsoft.poolparty.biz/devrel/fcc3cd4a-59ea-47a2-9cc1-784142a5a25d - https://authoring-docs-microsoft.poolparty.biz/devrel/8a94907f-2511-4271-b5ca-ec7f2e75067c-- https://authoring-docs-microsoft.poolparty.biz/devrel/68ec7f3a-2bc6-459f-b959-19beb729907d-- https://authoring-docs-microsoft.poolparty.biz/devrel/e60d1924-c4ad-4104-bd1b-973758bbac7a+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/c671beaa-a830-4c9f-aceb-97379ee031ca spProducts:+- https://authoring-docs-microsoft.poolparty.biz/devrel/d7a55faf-a992-4e27-aa3a-eadc9830e778 - https://authoring-docs-microsoft.poolparty.biz/devrel/bffa8e88-f633-409d-a24d-083bdbc68872-- https://authoring-docs-microsoft.poolparty.biz/devrel/90370425-aca4-4a39-9533-d52e5e002a5d-- https://authoring-docs-microsoft.poolparty.biz/devrel/91d5f984-ee3d-43c4-9daf-bb09a6bc4e1a+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/8921374c-4dbe-4ed0-b011-a39e18bfbd98 platformId: 697da6bb-f033-f173-9956-ced01b41ce16 --- @@ -77,7 +77,14 @@ If you're still using Microsoft Sentinel in the Azure portal, we recommend that
Perform the following steps to define an access restriction policy for a Standard-plan playbook.
-1. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), select the **Configuration** > **Automation** page. For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Configuration** > **Automation**.
+1. Note
+
+ To open the automation page in the [Microsoft Defender portal](https://security.microsoft.com/), use the path for your package:
+
+ - In Microsoft Sentinel in the Defender portal: **Microsoft Sentinel** > **Configuration** > **Automation**.
+ - In ISOC main navigation menu: **Automation**.
+
+ For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), select the **Configuration** > **Automation** page.
2. On the **Automation** page, select the **Active playbooks** tab.
3. Filter the list for Standard-plan apps. Select the **Plan** filter and clear the **Consumption** checkbox, and then select **OK**. For example:
