Within this series (well just two posts) I want to cover some of the available configuration options of the Azure API SQL Server connector. The connector simply enables you to connect with a SQL Server (as well as on-premises instances) or Azure SQL Database and perform various actions. This includes; executing stored Procedures, Poll data (triggers) and the option to retrieve, create, update and delete database table entries without having to write SQL.
This is just a very short post explaining how to add conditions within your Azure Logic App. The most common case would probably handle a scenario where it’s required to execute different follow-up actions based on the execution status of the preceding action (success or failure). And therefore I will be using this case as an example. But let’s go over some of the details first.
As can be seen from my previous postings, I’m still spending my evening hours researching and playing around with the Azure App Service offering. And to be honest, the more you know, the more interesting it gets. However from time to time you will run into simple challenges like how to iterate over a collection of items?
I’ve been playing around with Azure App Service for a couple of days now and decided to address some aspects that haven’t been covered very well within the knowledge sessions I’ve seen so far. Many only include the cool parts, creating new Logic Apps with everything already installed and configured. Also, I haven’t seen any covering topics like scaling and configuration recommendations. In real environments, things require a bit more care and attention. Therefore I will cover some of the basic needed when getting up and running with Azure App Service within upcoming blog posts.
When it comes to Azure App Service, I haven’t followed what was going on to be 100% honest. Based on the first details released in March, it sounded like a cloud-based version of Visual Studio LightSwitch. Able to manage different types of Azure abstractions by click-building and publishing applications into Azure. However, this isn’t the case.
In this post, I want to cover Azure Search from a different perspective and share some details that might help people getting starting in the exciting world of search. The main focus will be on pointing out the underlying technology, helping you to understand better and build search solutions.
The Microsoft Azure Search team recently released a new preview version, which includes some exciting new features. I’ve briefly covered them in my previous Azure Search Services post but wanted to dive a bit deeper into the Indexers.
An indexer is a content crawler written for a specific data source eliminating the need for writing code responsible for extract data from your data source and feed this data within the index. The Indexer runs within the Azure context, and it’s therefore not required to create a service for hosting this process (billing details are not available yet).
Recent Comments