Azure Logicapps Inside-Out with real-world use case

Explore Azure Logic Apps as a platform as a service that enables automated tasks and workflows with little to no code, using built-in connectors for fast integrations.

Discover connectors that enable integration with external systems in Azure Logic Apps without writing any code, using triggers, actions, and authenticated connections to SQL, Office 365, SharePoint, and SAP.

Explore how triggers start a Logic App workflow with polling or push triggers, and how actions follow to perform tasks using built-in, standard, enterprise, and custom connectors.

Access and explore Azure Logic Apps in the portal, browse Logic Apps workflows, view their properties, and create a new workflow by clicking add and providing the required options.

Explore the two versions of the Logic App Designer, noting the default switch to the new designer and how to toggle between legacy and new modes.

Create a consumption type logic app in the Azure Portal by selecting Logic Apps, choosing a subscription and resource group, applying naming conventions and tags, then create and open it.

Explore the Azure Logic Apps user interface, including run and refresh controls, editing and cloning options, designer and code views, run history, versioning, connections, security settings, and key management.

Create a schedule-triggered logic app that queries the Microsoft Graph API, stores in variables, uses key vault for credentials, parses JSON, iterates app registrations to detect expiry, and emails alerts.

Create a trigger in the Azure Logic Apps designer using recurrence or schedule, with optional time zone and start date. The trigger is the first step, followed by subsequent actions.

Learn how to create and initialize built-in variables in Azure Logic Apps, choosing types like array for expired apps and string for the email recipient.

Create a parameter with a name, type, and default value, then pull its value into a variable via right window; in this use case, use a variable instead of exporting.

Name variables for readability and organization in Azure Logic Apps. Define a days-to-look-ahead threshold, such as 15 days, as a configurable variable.

Explore the new and old Azure logic apps designers, noting similar functionality, a more convenient layout, and remember to save before switching to avoid losing changes.

Use basic variables to start building the logic in Azure Logic Apps, progressively adding more variables without overwhelming you, and move to the next step.

Learn to call a secure rest endpoint with an http get request to graph.microsoft.com/applications, enable Active Directory OAuth, and provide client id and client secret for authentication.

Create an Azure AD service principal by registering a new app, capturing tenant and client IDs, and generating a secret; then grant API permissions to access read data.

Select Microsoft Graph application permissions for the service principal, grant read all as an application permission, and obtain domain admin consent to enable access.

Test the workflow again, authorize, and wait for permissions to propagate, then successfully call the API endpoint and view the response.

Inspect the api output to view raw application details, including id, display name, and the password credentials secret. Identify single or multiple secrets for debugging in a test environment.

authenticate to the graph api with an http action in the new preview designer, configure active directory authentication using client id, tenant id, client secret, and graph audience.

Filter Graph API output to reduce clutter and aid debugging in Azure Logic Apps by selecting 999 results and fields: id, application id, display name, password, credentials, and key credentials.

Expose the risk of storing secrets in plain text when calling an http endpoint and demonstrate integrating Azure Key Vault to safely handle secrets.

Create a key vault in the same resource group as your logic app, name it, and store client id and client secret securely; then set access via role assignment.

Enable a system assigned managed identity in the logic app to securely access Azure Key Vault secrets, retrieving client ID and client secret for HTTP calls.

Enable managed identities in the logic app, assign the secrets user role via Azure role assignments to access the key vault, then use the identity in the workflow.

Parse json from the http response using the parse json action, generate a schema from a sample payload, and extract fields using a debug variable.

Learn how to copy the JSON body from a logic app workflow output to form the sample JSON used for schema creation, avoiding extraneous data above the brace.

Loop through each entry to check for expired secrets in the array of app registrations, using a for loop to process multiple entries after handling the http response.

Explore how to implement and optimize a for-each loop in Azure Logic Apps, including setting up debug variables, handling concurrent execution, and safely processing JSON and password credentials.

Parse password credentials in Azure Logic Apps using json parse and for each loop to access secret items, breaking down long json strings for usable display names and end dates.

Fixes a json type error by allowing string or null in the schema and removing required fields to handle missing or null values in http responses, enabling logic apps execution.

Learn to successfully extract the expiry date by aligning the time value, running a sample, and preparing for expiry time comparisons in real-world logic apps scenarios.

In Azure Logic Apps, define an expiry date by adding 15 days to the current date with UTC now and the add days function, then prepare for a date comparison.

Learn to use the condition control in azure logicapps to compare end dates with a 15-day expiry threshold and identify apps expiring soon.

Learn how to reliably format and compare dates in Azure Logic Apps by explicitly converting timestamps to a year-month-day format and handling old vs new designer behavior.

Identify expired apps via condition validation, append details to the expired apps array, and store app name, id, expiry date, and secret name for a readable, email-ready list.

Learn to send email with Office 365 in Azure Logic Apps by signing in with a service account, converting an array to a string for a neat email body.

Use the create HTML table action in the preview designer to convert an array into an HTML table for friendlier email output, comparing table versus string formats and improving readability.

Beautify HTML in Azure Logic Apps by formatting emails with variables, purified HTML, and workflow name to create a neater, more readable Outlook email.

This lecture completes a rudimentary Azure Logic Apps workflow by triggering, querying Microsoft Graph API, saving credentials in Keyvault, parsing apps and secrets, and emailing an expired items report.

Learn to filter upcoming expirations in Azure Logic Apps by excluding already expired apps and showing only those expiring within the next 15 days using current date and UTC formatting.

Track expiry of app credentials by adding parallel branches for key credentials alongside secrets, parsing JSON payloads and flagging items nearing expiry using a threshold days rule.

Learn how to restore a previous Azure logic app version by promoting a past version, overwriting the current one, and confirming the restored conditions.

Improve the final output by correcting HTML and cleaning the table rows for a neater presentation, then pick up this HTML from the resources section to experiment with it.