How to trace Exchange Actionable Message Action.Execute

Hi @Barak Zehavi --CNTR 

Thanks for reaching out to the Microsoft Q&A forum! 
Based on your description, I understand that with Action.Execute, you don't have control over the URL and receive no indication when a call is made to the server. 
As forum moderators, we have access to a dedicated testing environment that allows us to replicate scenarios like yours and investigate further. However, our primary goal is to support you in working toward a solution by providing meaningful insights based on the resources available to us. 

From my research, your understanding of Action.Http is accurate. However, starting from Adaptive Card schema version 1.4, Action.Http has been deprecated in favor of Action.Execute. 

To use Action.Execute, you must register a provider in the Actionable Messages Developer Dashboard. This registration is essential because the originator of the actionable message must be associated with a verified provider, as illustrated in the documentation.  

You could refer to the following document to see how Action.Execute is used: Overview of Universal Action Model - Outlook Developer | Microsoft Learn 
There’s no direct way to inspect the internal Exchange call to the target URL. However, you can still capture key details of the request sent by Microsoft to your endpoint, such as such as timestamp, HTTP method, header, source IP address, … 
These logs can help you understand and debug the behavior of Action.Execute in your environment. 
I hope the information above helps to partially clarify your situation. If you have any updates, please don’t hesitate to share. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.