Define an access restriction policy for Standard-plan playbooks

• Applies to:

  Microsoft Sentinel in the Azure portal, Microsoft Sentinel in the Microsoft Defender portal

This article describes how to define an access restriction policy for Microsoft Sentinel Standard-plan playbooks, so that they can support private endpoints.

Define an access restriction policy to ensure that only Microsoft Sentinel has access to the Standard logic app containing your playbook workflows.

For more information, see:

• Secure traffic between Standard logic apps and Azure virtual networks using private endpoints
• Supported logic app types

Important

The new version of access restriction policies is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

Microsoft Sentinel is available as part of the public preview for the unified security operations platform in the Microsoft Defender portal. For more information, see Microsoft Sentinel in the Microsoft Defender portal.

Define an access restriction policy

1. For Microsoft Sentinel in the Azure portal, select the Configuration > Automation page. For Microsoft Sentinel in the Defender portal, select Microsoft Sentinel > Configuration > Automation.

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:

   

4. Select a playbook to which you want to restrict access. For example:

   

5. Select the logic app link on the playbook screen. For example:

   

6. From the navigation menu of your logic app, under Settings, select Networking. For example:

   

7. In the Inbound traffic area, select Access restriction. For example:

   

8. In the Access Restrictions page, leave the Allow public access checkbox selected.

9. Under Site access and rules, select + Add. The Add rule panel opens on the side. For example:

   

10. In the Add rule pane, enter the following details.

    The name and optional description should reflect that this rule allows only Microsoft Sentinel to access the logic app. Leave the fields not mentioned below as they are.

    Field	Enter or select
    Name	Enter SentinelAccess or another name of your choosing.
    Action	Allow
    Priority	Enter 1
    Description	Optional. Add a description of your choosing.
    Type	Select Service Tag.
    Service Tag (will appear only after you select Service Tag above.)	Search for and select AzureSentinel.

11. Select Add rule.

Sample policy

After following the procedure in this article, your policy should look as follows:

Related content

For more information, see:

• Automate threat response with Microsoft Sentinel playbooks
• Use playbooks with automation rules in Microsoft Sentinel
• Set up Azure App Service access restrictions