Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Moving resources

We have already started to cover this in the preceding exercise. Once created, resources can be renamed, or a clone of the resource can be created, but it must exist within the same resource group. If you want to do this, the new copy will need to have a different name.

To move a resource between resource groups, you need to manually create a new instance in the new resource group and then copy the code across to the new version in the new resource group.

When creating a copy of an existing logic app for a new resource group (such as adding it to the test resource group), you might consider using the Clone button located on the Overview page for that resource. However, cloning will create a second copy within the same resource group, which is not what you are trying to achieve. The name of the clone will also need to be different as you cannot have two copies of a resource with the same name in a resource group.

The better option is to create a new blank logic...