I am new to azure logic apps.
Can any one help me how to implement sequential convoys in azure logic apps.
For the benefit of others coming across this, you can refer to this document as shared by #Hury in the comment on how you can implement sequential convoys in azure logic apps
Related
Are these two the same:
https://portal.azure.com/#create/Microsoft.EmptyWorkflow and
https://portal.azure.com/#create/Microsoft.LogicApp
I followed two different tutorials to create logic apps and I get there. Is that the workflows are renamed to logic apps?
https://portal.azure.com/#create/Microsoft.EmptyWorkflow seems to be an outdated link for consumption Logic Apps.
https://portal.azure.com/#create/Microsoft.LogicApp can be used to create both consumption and standard Logic Apps.
Different types are reviewed in this article: Single-tenant versus multi-tenant and integration service environment for Azure Logic Apps
The #create links are normally not used directly. They are opened when + Create a resource or + Add links are clicked in Azure Portal.
I have requirement to implement a solution for extracting files from share point to adls gen2 or blob storage.
I know we can do by using logic apps.
But looking for other some other possiblities.
The docs have a small mention about how you can use the Copy Activity with HTTP Connector for SharePoint Online that you could explore.
If this doesn't work out for you, Logic Apps are indeed a great to implement this. You could also trigger the Logic App from your Data Factory pipeline when needed.
You could use the Web Activity or Webhook Activity to trigger your Logic App.
Is there anyway to ameliorate the Logic App limit on managed identity in a subscription?
Microsoft docs have the limit as 250
Number of logic apps that have a managed identity in an Azure subscription per region 250
Is there anyway to handle this? ... as we're already getting close to that limit, and we're now doing all our integration with logic apps
I think you have to contact Microsoft support to see for possible ways to circumvent these limits.
The way I manage this is by creating reusable logic apps which work with managed identities and call these logic apps in parent workflows
The response we got from the Logic App team is the limit is "soft", so it's possible to increase on a case-by-case basis
I am trying to Process AAS tabular model using Azure logic app and trying to read status back. I can do this using refreshId manually.
https://learn.microsoft.com/en-us/azure/analysis-services/analysis-services-async-refresh
Any Idea How would i retrieve last refreshId dynamically in azure logic app?
enter image description here
My recommendation would be to simplify your architecture and eliminate the Logic App if you aren't already heavily using Logic Apps. It's not because we don't like Logic Apps. It is just good to simplify the moving parts in an architecture.
It is possible to processing Azure Analysis Services models via ADFv2 with native components. There's no need to use Logic Apps or Azure Batch for custom .NET activities. You can use native activities like Web Activity and Lookup Activity.
You are correct that looking up the refreshID is a bit more complex than it should be. The API to start a refresh asynchronously should return the refreshID in the body of the response and I've provided this feedback here. Please vote for it. In the interim, it's possible to get all the refreshes in the last 30 days and then filter down to the one which started most recently.
I have published an ADFv2 pipeline which uses native activities here. Please give this a try and see if it meets your needs without a Logic App.
I am in process of designing a SaaS application over PaaS (Google App Engine).
My SaaS will have two user interfaces:
Web Based
Mobile App based
Web based would be feature-rich whereas Mobile app would have essential and/or frequently used features.
Mobile app would invoke RESTful services to perform business logic.
This SaaS would target mainly individuals using Mobile Apps; however, there could a use-case wherein these individuals could form a group and operate as a company.
So with that in mind, I am considering two entities: Account (Tenant) and User.
I am considering having many-to-many relationship between these two entities as one user could be part of multiple Accounts (unlikely but can’t be ruled out) and of course, one account can have multiple users.
I would like to know the best practices for authentication under such scenario:
Should I use Google's provided Authentication or should I implement my own authentication? (I am still exploring OAuth and Google's authentication offering.)
I think, for web-based interface, username/password over SSL would suffice. But, not sure, can this be applied to mobile app?
Can I avoid a situation wherein I have to store credentials in mobile app?
Thanks in advance for any help you can provide on this.
A
Having just completed my first project using Google App Engine, I can say that I ran into alot of the questions that you have. I'll try to explain my approach to each point and also approach it from your perspective as well.
Authentication - Generally using Google's auth would be the easiest route, but you would still have to implement a custom adaptation in order to work with the "company"/"group" concept. Implement in the datastore/whatever database you prefer to use an entity called "Groups" which have a list of google users... this way users can belong to many groups.. then you just search by property (user) to get all groups they belong to. I implemented my own authentication system for unrelated reasons.
Google App Engine comes with SSL/HTTPS support for its own domains. You can add in your own custom domain with SSL support as well. You can use SSL through native apps or mobile web apps additionally. I simply used the native support that came with it.
Yes and no. You will always have to store the credentials somewhere. Maybe it wont be in your apps code/directly connected to your app (Google auth would be an example). But somewhere, on your phone, the credentials WILL reside. They may be encrypted/obfuscated, but they will be there. So either have your user enter them in everytime, or save them/use the ones provided by the phone. For myself, .NET provided a nice way of storing credentials in a secure fashion (non-plain-text) for each user's machine.