no you can use it with Logic App Standard, Data Factory, API Management, Functions and anything where you have custom logging to app insights or log analytics. We will have more videos coming out on this. I think Lex is already going to ping you following our message but for anyone else do drop us a line if you would like a personal demo

hi, im not sure i understand the question to be honest but you can have different power automate flows in different serverless360 business applications so it gives some context for the support user

@@mikestephenson8525 Thanks for your reply even if it was not clear enough to answer. In the video you used the example of order processing. What if I have many products and variations of requirements in each of those products and orders? The question was do I need different work flows for each or the same power bi can be individualized (customized) for all those order types?

no prob.. @@balasubr2252 I think from the Power Automate side of things you can do what you suggest above its a design implementation choice in power automate. Doing shared flows to reuse common functionality is a good idea From a serverless360 side when it comes to managing those flows then you can add the same flow to multiple business applications. That means if you wanted seperate apps to manage different flows doing different business features but you had one shared flow used by both business features you can just add the shared flow to both serverless360 applications

Please check this Microsoft doc:docs.microsoft.com/en-us/samples/azure/azure-sdk-for-net/dead-letter-queues/ At Enterprise, you can consider using tool like Serverless360 to get visibility on the Service Bus messages: docs.serverless360.com/docs/service-bus-queue#view-messages Serverless360 also supports processing the messages like resubmission, repair and resubmission and purging.