{"id":110846,"date":"2017-07-27T10:00:45","date_gmt":"2017-07-27T17:00:45","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/grow-up-to-logic-apps\/"},"modified":"2017-07-27T10:00:45","modified_gmt":"2017-07-27T17:00:45","slug":"grow-up-to-logic-apps","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/grow-up-to-logic-apps\/","title":{"rendered":"Grow up to Azure Logic Apps"},"content":{"rendered":"
Azure Logic Apps offers develops even richer capabilities than what\u2019s included in Microsoft Flow. Starting this week, it is possible for Flow users to save any flow they have as a Logic App resource template. This template can be managed like any other Logic App resource — and deployed through Visual Studio or directly in the Azure portal to a subscription of the user\u2019s choice.<\/p>\n
How to get your Flow definition<\/h2>\n
Converting a flow to an Azure Logic app starts by exporting the Logic App definition from the Microsoft Flow web portal. Navigate to the flow that you would like to convert and open the … More<\/strong> menu. In this menu, there are two options:<\/p>\n
\n
Export as Logic app template (.json)<\/li>\n
Export as Package (.zip)<\/li>\n<\/ul>\n
For this feature, you will want to select the first menu item. Packages are used to export flows to move them along with other resources such as PowerApps and Common Data Service entities – you can read more about that here<\/a>.<\/p>\n