MicrosoftHello,
I encountered an issue when trying to use the "Create Blob (V2)" trigger with private endpoints in Azure Logic Apps, where none of the configurations I attempted worked. After investigating, I suspected there might be a system glitch or an additional authentication check that was failing. As an alternative, I tried using the "Upload Blob" trigger instead, and it worked successfully.
It appears that the "Create Blob (V2)" trigger performs additional authentication checks that may fail when using private endpoints, whereas the "Upload Blob" trigger does not encounter the same issue. Both triggers essentially perform the same operation, so in scenarios involving private endpoints, I recommend using the "Upload Blob" trigger.
Additionally, I noticed that the solution mentioned above suggests that having both the Logic App and the storage account in the same region might cause issues. However, in my case, the "Upload Blob" trigger worked fine even when both were in the same region.
Therefore, if you're using private endpoints with a storage account and virtual network integration in a Logic App, I suggest opting for the "Upload Blob" trigger for a more reliable solution.
Please consider this the correct solution for the issue discussed.
