Azure Insights: Logic App best practices; Azure Policy; Capacity shortages; Firewall Premium

Microsoft Azure pros discuss Logic App best practices, controlling a network with Azure Policy, managing Azure capacity shortages, and deploying Firewall Premium with Azure Bicep.

Logic App best practices

Writing on the Serverless360 blog, Sandro Pereira explored best practices for fixing connectors. The Logic Apps Designer carries out design-time checks against Logic App flows to spot design problems. Common examples include adding an invalid expression or issues with rendering JSON. Problems are often flagged with an exclamation point in the Logic App editor, and Pereira explained how to login and fix the connector.

In a separate blog on the same theme, Pereira discussed connector naming conventions. He argues that users should provide descriptive names and use the more flexible naming capabilities of Visual Studio rather than Azure portal. Naming API connections is important but can involve manual work. According to Pereira, users can go to connections in the Azure portal, export and download a template, change parameters, create a new Template deployment resource in Azure portal, and build a new template in the editor.

Controlling a network with Azure Policy

Joe Carlyle, writing on WeDoAzure, took a look at how to control a network with Azure Policy. Building a reliable network is important and Policy allows users to set standards and enforce compliance. He showed how to create policy definitions grouped as an initiative. Users may want to rely on build in definitions or create custom definitions.

He demoed an initiative with multiple built-in policies and defined connection resources like VNet peerings, Local Network Gateway, and public IP addresses. Users can layer complexity and do tasks like aligning subnets with a Route Table.

The idea…aligns with the purpose of Azure Policy, restrict and define the platform. This core initiative obviously has a focus on network type resources, but the same basic principal applies. Similar again in approach is the ability to allow exclusions where necessary. For example, allowing VNET peering in a network resource group. However, don’t forget/ignore RBAC, this should at minimum compliment your policy requirements.

Managing Azure capacity shortages

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

Get full access

or login