Remove playbook GetProofpointTAPEvents for TAP connector

[shubhangipagar-gh]

Based on confirmation from Microsfot team, Remove playbook GetProofpointTAPEvents for TAP connector.
The playbook appears to be the initial implementation of getting data into Sentinel. The solution has since evolved into ingestion with Azure Function and now CCF that uses different custom table names. This playbook ingests clicks blocked events into sentinel using HTTP data collector API which will be deprecated in September 2026.
Now CCF Poller is ingesting the same clicks blocked events in ProofPointTAPClicksBlockedV2_CL table.

Required items, please complete

Change(s):

• See guidance below

Reason for Change(s):

• See guidance below

Version Updated:

• Required only for Detections/Analytic Rule templates
• See guidance below

Testing Completed:
**- I tested TAP connector, it is working fine, but i am unable to validate if playbook is removed, it seems it is getting referred from content hub, I have modifed content hub files as well but looks like it will reflect post deployment.

• Please confirm before merging the PR.**

Checked that the validations are passing and have addressed any issues that are present:

• See guidance below

Guidance <- remove section before submitting

---

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:

Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

• Updated syntax for XYZ.yaml

Reason for Change(s):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

Version updated:

• Yes
• Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

• Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

• Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---