Edit

Configure advanced security for Microsoft Sentinel playbooks

  • Article
  • Applies to:
    Microsoft Sentinel in the Azure portal, Microsoft Sentinel in the Microsoft Defender portal

This article shows how to define an access restriction policy for Microsoft Sentinel Standard-plan playbooks, so that they can support private endpoints. Defining this policy will ensure that only Microsoft Sentinel will have access to the Standard logic app containing your playbook workflows.

Learn more about using private endpoints to secure traffic between Standard logic apps and Azure virtual networks.

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.

    1. Select the Plan filter.

    2. Clear the Consumption checkbox.

    3. Select OK.

      Screenshot showing how to filter the list of apps for the standard plan type.

  4. Select a playbook to which you want to restrict access.

    Screenshot showing how to select playbook from the list of playbooks.

  5. Select the logic app link on the playbook screen.

    Screenshot showing how to select logic app from the playbook screen.

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

    Screenshot showing how to select networking settings from the logic app menu.

  7. In the Inbound traffic area, select Access restriction.

    Screenshot showing how to select access restriction policy for configuration.

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

  9. Under Site access and rules, select + Add. The Add rule panel will open to the right.

    Screenshot showing how to add a filter rule to your access restriction policy.

  10. Enter the following information in the Add rule panel. 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.

Your policy should now look like this:

Screenshot showing rules as they should appear in your access restriction policy.

For more information about configuring access restriction policies in logic apps, see Set up Azure App Service access restrictions.

Next steps

In this article, you learned how to define an access restriction policy to allow only Microsoft Sentinel to access Standard-plan playbooks, so that they can support private endpoints. Learn more about playbooks and automation in Microsoft Sentinel: