Microsoft has announces a bunch of updates to Azure Logic Apps. If you’re note familiar with Azure Logic Apps, they provide a “no-code” solution for using a WYSIWYG (or visual) designer that allows you to build and configure business process workflow automation via drag-n-drop actions. You can also drop down to edit the JSON definition directly, but you don’t need to be a programmer to use the “no-code”, visual designer. There are many amazing features in Azure Logic Apps, and with this latest update release Azure Logic Apps is getting even better and more powerful!
Here’s a simple list of the updates in this January 2017 update:
- New connector search experience to search by service and then view all triggers and actions
- Use the new Switch Condition to implement branch logic using switch and cases
- New authentication options have been added to HTTP actions
- Many actions have newly updated Icons and brand colors
- New Dynamic outputs in dynamic fields support in the Designer.
Here are some bug fixes released:
- OAuth fixes for IE11
- Fix occasional errors when switching to code-view before finishing configuring actions
- Correctly surface XML errors / exceptions from use of @xml()
- zoom fixes in IE11
- Correctly reload Compose card when inputs and outputs are empty
There are also a few new Azure Logic App Connectors. Here’s the list of connectors that have been added:
- OneNote (Business)
- Power BI Steaming Dataset
- Outlook Tasks
It’s really nice to see some more recent updates to Azure Logic Apps. It’s a really great service, and as with most software it can always be improved and made more powerful. However, it’s really pretty great as it already stands today. Great job Azure Logic Apps team!
This article is based off a recent 2017-01-10 release update announcement from Microsoft.
In the early days of Microsoft Azure the Portal was the primary tool to go in and configure your cloud components. After some time the Azure Service Manager API’s were introduced as a set of both PowerShell and Command-Line tools (X-Plat CLI). These tools allowed for Azure Automation to be scripted, however they were still a bit cumbersome as they were procedural based. More recently Microsoft overhauled the entire Azure Portal that exists today as well as a brand new set of Azure Resource Manager API’s. The purpose of Azure Resource Manager is more than just replacing Azure Service Manager. It’s real purpose is a story about automation and DevOps. Read More
The latest release of Azure PowerShell includes the new “Export-AzureRMResourceGroup” cmdlet. This cmdlet allows you to specify the name of a Resource Group and it will export the resources for that group into an ARM Template json file. This new cmdlet is part of the new Azure PowerShell release that was just released today! Read More
As DevOps has been taking hold within the software industry there’s been a strong push towards automating everything. This include automating build, testing, deployments, as well as server and infrastructure configurations. Server and Infrastructure configuration automation was not a trivial task in the old days of on-premises datacenter where each server was on its own dedicated hardware. However, with the adoption of the cloud and Microsoft Azure along with the use of Virtualization, the automation of server and infrastructure configuration is now fairly easily done. In fact the automation of deploying servers and infrastructure is now possible through the scriptability of modern virtualization technology; such as what makes up the Microsoft Azure platform.
Automation scripts have been run for decades, this is not a new concept. However, the term Infrastructure as Code (IaC) is fairly new in the industry. As with any new term there’s starting to get a buzz around it, and with buzz comes misconceptions and misinterpretations. The purpose of this article is to describe some context surrounding the Why, What, and How surrounding Infrastructure as Code. Read More
The book “Microsoft Azure Essentials: Azure Automation” written by Michael McKeown is written to target IT Pros and PowerShell developers to help them understand the core concepts of Azure Automation. This includes using runbooks based on PowerShell Workflow, and orchestrating frequent deployment (ala DevOps) and life cycle management through the use of automating Azure resource setup and maintenance. Read More