I am using azure Standard service plan and developing Logic Apps Work flows. Now i want to deploy it to different environment like QA/UAT.
I have referred few MSDN blogs and found out We can do the logic apps deployment to different subscriptions via Visual studio with Azure SDK. However I am using API Apps in the logic apps work flows like SQL connector, Transformation service, BizTalk Xpath Extractor etc..
Can you please let me know how do we deploy API Apps to different Environment. Please suggest.
Thanks,
Vinoth
One way is to create the logic app with the connectors you want and then export that ARM template LogicApp -> Settings -> Export Template. Of course this template might not be the ideal approach since it will have lot of stuff hard coded specific to that LA.
The good approach will be to create a new Azure resource Group project which has
the logic app ARM template,
just copy the defn part from you existing logic apps int the template definition section
make sure you have the connection resources creation added as part of you template.
Some useful resources
1. Checkout this MSDN link.
2. There is a utility also to get the LA templates, read this
Related
I have several Power Platform components, such as a Power App and some Power Automate flows that are part of a larger application. This application also consists of a Python package, a SQL database and so on.
I am trying to deploy this application on a client's environment. Now, in terms of the Python package and SQL database, for instance, this would mean deploying it into their Azure subscription or tenant.
How would this work for the Power Platform components? How can I deploy it on their subscription?
Note: I am not sure if subscription is the correct term to use here. As far as I know, Power Platform is not a part of Azure, but it comes under an O365 or D365 subscription?
I know Power Apps and flows can be exported and imported into other environments/subscriptions. But, is there some way I can maybe set up a CI/CD solution in order to achieve this? Maybe using Azure DevOps?
I have come across this, but from what I understand, I believe this is about deploying these components in different environments within the same subscription?,
https://learn.microsoft.com/en-us/azure/architecture/solution-ideas/articles/azure-devops-continuous-integration-for-power-platform
When you use Azure as part of you Power Platform solution, the right term is "tenant". 1 tenant can have multiple power platform environments and azure subscriptions.
https://learn.microsoft.com/en-us/power-platform/admin/environments-overview#environment-scope
Devops for Power Platform is simpler. Best way to authenticate is using service principal:
https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tools#connection-to-environments
The Azure part is more complicated. if you want to fully automate you will need to write some infrastructure as code to create resources like an azure function or a database and after that the pipeline to deploy the code to those resources.
I'm creating a schedule-triggered Azure Function which will run tests once a day. If during the run any test fails, I want it to create a bug on a Azure DevOps project which includes a log of the failed tests.
I know I could create a PAT so that it can authenticates with the DevOps REST API but I don't like its downsides:
it can be valid for 1 year at maximum, I will need to remember to extend its expiration period
every bug created like this will have me as its creator
Edit:
I found out I could use a MS Flow - there's a DevOps connector that can create workitems, still it has a downside of having me as workitem's creator but it's not such a pain...
Still would much appreciate to learn about other options...
Is there any better way I can let my Azure Function to create bugs on my DevOps project?
An alternate option would be the use azure logic app along with azure function.
Here the azure function would directly call a azure logic app and the logic app would create a bug workitem .
Refer the following article by Stefan stranger
On how to create logic app which will create the bug. Here we will be using azure webhooks for the creating of bugs.
Now you can either send the data to a storage account where the logic app using some trigger to get the data and then use it to create bug, or you can directly connect to the logic app .
Refer the following article by Laura KokKarinen for this .
I created a Logic Apps Standard, a workflow, and a trigger of Request When a HTTP request is received, like below by following the link below:
https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-http-endpoint#create-a-callable-endpoint
However, I also want to create logic apps: Choose a Logic Apps workflow following the link below, but it is not available shown above.
https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-http-endpoint#create-nested-logic-apps
Image from the link above for comparison.
Questions
How to make it available under Logic Apps std or other versions apart from Consumption?
Why is it that many connectors that are available in Consumption are not available in the Standard plan?
Refs:
Why does Logic App Standard Plan have missing connection trigger?
I have tried to create an simple logic app in standard plan and unable to get this connector called Logic apps: Choose a Logic Apps workflow
And tried the same with consumption plan and its showing there .
So you can try with the same MS DOC that you are following with Logic app- Consumption
For more information please refer this MICROSOFT DOCUMENTATION: Single-tenant versus multi-tenant and integration service environment for Azure Logic Apps
Kindly note that we have something called managed connectors which are used in LA consumption and something called builtin connectors and can be used with standard logic apps.
The built in connectors are running in the LA standard process. While the managed are in a different process.
The list of actions which are available in managed connectors are not always available in the built in connectors.
Still you can use the managed connectors in the LA standard site.
I want to publish an web application on Azure market place.
I can create a Linux VM, install Java, Tomcat, SQL server and create an image of it. But instead of that, is it possible to create a tomcat instance along with database on Azure portal, add it to a resource group and publish this resource group on market place?
Would this approach be more advantageous?
thanks
As per the doc here:
https://learn.microsoft.com/en-us/azure/marketplace-publishing/marketplace-publishing-getting-started
Azure Marketplace offerings are based on Azure VM images or solution templates, your current solution would be the VM based route. It sounds like you may want to look at the solution template route to leverage other capabilities such as Azure SQL Server.
Neither route enable "publish this resource group to the market place". If that is the route you are aiming for that is essentially building out a multi-tenant application which is a bigger task and perhaps something like this link will help get you started:
https://azure.microsoft.com/en-gb/blog/with-newly-available-services-azure-continues-to-be-the-best-place-for-software-as-a-service-developers/
There are also other stackoverflow answers which may be of help:
Does a developer have to pay for publishing a SaaS app on Windows Azure Marketplace?
How can i publish my web solution to Marketplace
Right now in azure logic apps the third party connectors like twitter ,facebook ,salesforce etc requires multifactor authentication which can be done using workflow designer .We are looking forward do the same using PowerShell ARM Template for different environments. So please suggest the way forward ?
Here is the blog from Jeff Hollan for creating "connections" in logic app using ARM
http://i1.blogs.msdn.com/b/logicapps/archive/2016/02/23/deploying-in-the-logic-apps-preview-refresh.aspx