is Containerization of Standard logic app using service bus built in connector supported or not

Question

Hi

In Logicapp (standard), we were able to resolve the failure of Complete_Message and Dead-letter_the_message service bus actions by enabling Vnet Integration and setting the webapp configuration value vnetPrivatePortcount to 2, as suggested in the below blog. 
https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/enabling-service-bus-and-sap-built-in-connectors-for-stateful/ba-p/3820381

 But We have a requirement to containerize same standard logic app workflows which uses service bus built in connector . we were able to push the image and test, but Complete message action is failing with bad request error. As a solution suggested for Standard logic apps , we tried implementing the same solution for Container instance by adding vnet and subnet, apart from this we need to set vnetPrivatePortCount to 2 but this property is not available for the container instance. Any suggestions would be helpful.

https://techcommunity.microsoft.com/t5/azure-integration-services-blog/enabling-service-bus-and-sap-built-in-connectors-for-stateful/ba-p/3820381

Thanks

Answer 1

@Anonymous Thanks for reaching out.

As discussed here, I will share the update here.

This feature is not yet supported on containers, there are plans to have this feature supported eventually but there is no ETA right now.

Please "Accept Answer" if the answer is helpful so that it can help others in the community.