Cannot edit API connection -- Paloaltoconnector-PaloAlto-PAN-OS-BlockIP

Frank Adams 0 Reputation points
2025-04-17T09:31:52.7266667+00:00

We are using the Palo Alto PAN-OS Solution for Microsoft Sentinel. The solution includes Playbooks which have API connections. The API connections facilitate automation and connect to the Palo Alto Networks security appliance via REST.

Our issue is we cannot edit the API connections to include the necessary credentials to authenticate the REST API connection.

When we attempt to edit the API connection we receive the error: 'Failed to edit API connection Paloaltoconnector-PaloAlto-PAN-OS-BlockIP'

We have verified the Access control (IAM) of the API connection grants us access to the API connection with the roles assigned as 'Owner' and 'Logic App Contributor'. Both roles permit write permission, specifically for category Microsoft.Web permission 'Add or Update Custom API' and globally 'Create API or Update API'

Can anyone help or provide guidance regarding this issue?

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,470 questions
{count} votes

1 answer

Sort by: Most helpful
  1. LeelaRajeshSayana-MSFT 17,676 Reputation points
    2025-04-24T22:16:40.1133333+00:00

    Hi @Frank Adams I have reached out to you through the private comments with next steps on this issue. Please respond to the requested information in the private comments.

    Update

    Sharing the findings here to help the broader community understand the issue.

    We have done some additional investigation on this issue. The Custom Connector could most likely be imported into the instance following the steps outlines in this GitHub repository - Azure-Sentinel/Playbooks/PaloAlto-PAN-OS/readme.md at master · Azure/Azure-Sentinel The authentication method for the connector only works with API Key based authentication. Please find this limitation in the Authentication section The guidance per the customer connector documentation states that the API key connection does not work on on-premises data gateway. Since the connector imported on work with API key authentication and this cannot be changed, enabling the on-premises data gateway operation is throwing an error because of the conflicting authentication support.  

     

    See if you create a new custom connector for this by following the steps in Create a custom connector from scratch | Microsoft Learn. This way, you can define your desired way of authentication. 

    We will continue to work with you through the offline case to help address this issue.  

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.