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.