Secure access and data for workflows in Azure Logic Apps
Article
Azure Logic Apps relies on Azure Storage to store and automatically encrypt data at rest. This encryption protects your data and helps you meet your organizational security and compliance commitments. By default, Azure Storage uses Microsoft-managed keys to encrypt your data. For more information, review Azure Storage encryption for data at rest.
To further control access and protect sensitive data in Azure Logic Apps, you can set up more security in these areas:
For Consumption logic apps only, before you can create or manage logic apps and their connections, you need specific permissions, which are provided through roles using Azure role-based access control (Azure RBAC). You can also set up permissions so that only specific users or groups can run specific tasks, such as managing, editing, and viewing logic apps. To control their permissions, you can assign built-in or customized roles to members who have access to your Azure subscription. Azure Logic Apps has the following specific roles, based on whether you have a Consumption or Standard logic app workflow:
You have full access to manage all resources, but you can't assign roles in Azure RBAC, manage assignments in Azure Blueprints, or share image galleries.
For example, suppose you have to work with a logic app workflow that you didn't create and authenticate connections used by that logic app workflow. Your Azure subscription requires Contributor permissions for the resource group that contains that logic app resource. If you create a logic app resource, you automatically have Contributor access.
You have access to enable, resubmit, and disable workflows and to create connections to services, systems, and networks for a Standard logic app. The Operator role can perform administration and support tasks on the Azure Logic Apps platform, but doesn't have permissions to edit workflows or settings.
You have access to create and edit workflows, connections, and settings for a Standard logic app. The Developer role doesn't have permissions to make changes outside the scope of workflows, for example, application-wide changes such as configure virtual network integration. App Service Plans aren't supported.
You have access to manage all aspects of a Standard logic app, but you can't change access or ownership.
Access to run history data
During a logic app run, all the data is encrypted during transit by using Transport Layer Security (TLS) and at rest. When your logic app finishes running, you can view the history for that run, including the steps that ran along with the status, duration, inputs, and outputs for each action. This rich detail provides insight into how your logic app ran and where you might start troubleshooting any problems that arise.
When you view your logic app's run history, Azure Logic Apps authenticates your access and then provides links to the inputs and outputs for the requests and responses for each run. However, for actions that handle any passwords, secrets, keys, or other sensitive information, you want to prevent others from viewing and accessing that data. For example, if your logic app gets a secret from Azure Key Vault to use when authenticating an HTTP action, you want to hide that secret from view.
To control access to the inputs and outputs in your logic app's run history, you have these options:
In many triggers and actions, you can secure the inputs, outputs, or both in a logic app's run history.
Restrict access by IP address range
You can limit access to the inputs and outputs in the run history for your logic app workflows so that only requests from specific IP address ranges can view that data.
For example, to block anyone from accessing inputs and outputs, specify an IP address range such as 0.0.0.0-0.0.0.0. Only a person with administrator permissions can remove this restriction, which provides the possibility for "just-in-time" access to data in your logic app workflows. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
To specify the allowed IP ranges, follow these steps for your Consumption or Standard logic app in the Azure portal or your Azure Resource Manager template:
In the Azure portal, open your Consumption logic app workflow in the designer.
On the logic app menu, under Settings, select Workflow settings.
In the Access control configuration section, under Allowed inbound IP addresses, from the Trigger access option list, select Specific IP ranges.
In the IP ranges for contents box, specify the IP address ranges that can access content from inputs and outputs.
Standard workflows
In the Azure portal, open your Standard logic app resource.
On the logic app menu, under Settings, select Networking.
In the Inbound traffic configuration section, next to Public network access, select Enabled with no access restriction.
On the Access restrictions page, under App access, select Enabled from select virtual networks and IP addresses.
Under Site access and rules, on the Main site tab, add one or more rules to either Allow or Deny requests from specific IP ranges. You can also use the HTTP header filter settings and forwarding settings. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
In your ARM template, specify the IP ranges by using the accessControl section with the contents section in your logic app's resource definition, for example:
In your ARM template, specify the allowed inbound IP address ranges in your logic app's resource definition by using the Microsoft.Web/sites/config section. In this section, under properties, add the ipSecurityRestrictions section, and use the ipAddress, action="Deny" | "Allow", tag=Default, priority, and name="Ports" sections to define a rule and set the ipAddress to the allowed IP range in x.x.x.x/x or x.x.x.x-x.x.x.x format, for example:
Many triggers and actions have settings to secure inputs, outputs, or both from a logic app's run history. All managed connectors and custom connectors support these options. However, the following built-in operationsdon't support these options:
Secure Inputs - Unsupported
Secure Outputs - Unsupported
Append to array variable Append to string variable Decrement variable For each If Increment variable Initialize variable Recurrence Scope Set variable Switch Terminate Until
Append to array variable Append to string variable Compose Decrement variable For each If Increment variable Initialize variable Parse JSON Recurrence Response Scope Set variable Switch Terminate Until Wait
Considerations for securing inputs and outputs
Before using these settings to help you secure this data, review these considerations:
When you obscure the inputs or outputs on a trigger or action, Azure Logic Apps doesn't send the secured data to Azure Log Analytics. Also, you can't add tracked properties to that trigger or action for monitoring.
To secure outputs from an action that obscures inputs or explicitly obscures outputs, manually turn on Secure Outputs in that action.
Make sure that you turn on Secure Inputs or Secure Outputs in downstream actions where you expect the run history to obscure that data.
Secure Outputs setting
When you manually turn on Secure Outputs in a trigger or action, Azure Logic Apps hides these outputs in the run history. If a downstream action explicitly uses these secured outputs as inputs, Azure Logic Apps hides this action's inputs in the run history, but doesn't enable the action's Secure Inputs setting.
The Compose, Parse JSON, and Response actions has only the Secure Inputs setting. When turned on, the setting also hides these actions' outputs. If these actions explicitly use the upstream secured outputs as inputs, Azure Logic Apps hides these actions' inputs and outputs, but doesn't enable these actions' Secure Inputs setting. If a downstream action explicitly uses the hidden outputs from the Compose, Parse JSON, or Response actions as inputs, Azure Logic Apps doesn't hide this downstream action's inputs or outputs.
Secure Inputs setting
When you manually turn on Secure Inputs in a trigger or action, Azure Logic Apps hides these inputs in the run history. If a downstream action explicitly uses the visible outputs from that trigger or action as inputs, Azure Logic Apps hides this downstream action's inputs in the run history, but doesn't enableSecure Inputs in this action and doesn't hide this action's outputs.
If the Compose, Parse JSON, and Response actions explicitly use the visible outputs from the trigger or action that has the secured inputs, Azure Logic Apps hides these actions' inputs and outputs, but doesn't enable these action's Secure Inputs setting. If a downstream action explicitly uses the hidden outputs from the Compose, Parse JSON, or Response actions as inputs, Azure Logic Apps doesn't hide this downstream action's inputs or outputs.
Secure inputs and outputs in the designer
In the Azure portal, open your logic app workflow in the designer.
On the designer, select the trigger or action where you want to secure sensitive data.
On the information pane that opens, select Settings, and expand Security.
Turn on either Secure Inputs, Secure Outputs, or both.
The trigger or action now shows a lock icon in the title bar. Any tokens that represent secured outputs from previous actions also show lock icons. For example, in a subsequent action, after you select a token for a secured output from the dynamic content list, that token shows a lock icon.
After the workflow runs, you can view the history for that run.
Select Overview either on the Consumption logic app menu or on the Standard workflow menu.
Under Runs history, select the run that you want to view.
On the workflow run history pane, select the actions that you want to review.
If you chose to hide both inputs and outputs, those values now appear hidden.
Secure inputs and outputs in code view
In the underlying trigger or action definition, add or update the runtimeConfiguration.secureData.properties array with either or both of these values:
If you deploy across different environments, consider parameterizing the values in your workflow definition that vary based on those environments. That way, you can avoid hard-coded data by using an Azure Resource Manager template to deploy your logic app, protect sensitive data by defining secured parameters, and pass that data as separate inputs through the template's parameters by using a parameter file.
For example, if you authenticate HTTP actions with OAuth with Microsoft Entra ID, you can define and obscure the parameters that accept the client ID and client secret that are used for authentication. To define these parameters in your logic app workflow, use the parameters section in your logic app's workflow definition and Resource Manager template for deployment. To help secure parameter values that you don't want shown when editing your logic app or viewing run history, define the parameters by using the securestring or secureobject type and use encoding as necessary. Parameters that have this type aren't returned with the resource definition and aren't accessible when viewing the resource after deployment. To access these parameter values during runtime, use the @parameters('<parameter-name>') expression inside your workflow definition. This expression is evaluated only at runtime and is described by the Workflow Definition Language.
Note
If you use a parameter in a request header or body, that parameter might be visible
when you view your workflow's run history and outgoing HTTP request. Make sure that
you also set your content access policies accordingly. You can also use
obfuscation to hide inputs and outputs in your run history.
By default, Authorization headers aren't visible through inputs or outputs.
So if a secret is used there, that secret isn't retrievable.
For more information, review these sections in this topic:
If you automate deployment for logic apps by using Resource Manager templates, you can define secured template parameters, which are evaluated at deployment, by using the securestring and secureobject types. To define template parameters, use your template's top level parameters section, which is separate and different from your workflow definition's parameters section. To provide the values for template parameters, use a separate parameter file.
For example, if you use secrets, you can define and use secured template parameters that retrieve those secrets from Azure Key Vault at deployment. You can then reference the key vault and secret in your parameter file. For more information, review these topics:
Secure parameters in workflow definitions (Consumption workflow)
To protect sensitive information in your logic app's workflow definition, use secured parameters so this information isn't visible after you save your logic app workflow. For example, suppose you have an HTTP action requires basic authentication, which uses a username and password. In the workflow definition, the parameters section defines the basicAuthPasswordParam and basicAuthUsernameParam parameters by using the securestring type. The action definition then references these parameters in the authentication section.
Secure parameters in Azure Resource Manager templates (Consumption workflow)
A Resource Manager template for a logic app resource and workflow has multiple parameters sections. To protect passwords, keys, secrets, and other sensitive information, define secured parameters at the template level and workflow definition level by using the securestring or secureobject type. You can then store these values in Azure Key Vault and use the parameter file to reference the key vault and secret. Your template then retrieves that information at deployment. For more information, review Pass sensitive values at deployment by using Azure Key Vault.
This list includes more information about these parameters sections:
At the template's top level, a parameters section defines the parameters for the values that the template uses at deployment. For example, these values can include connection strings for a specific deployment environment. You can then store these values in a separate parameter file, which makes changing these values easier.
Inside your logic app's resource definition, but outside your workflow definition, a parameters section specifies the values for your workflow definition's parameters. In this section, you can assign these values by using template expressions that reference your template's parameters. These expressions are evaluated at deployment.
Inside your workflow definition, a parameters section defines the parameters that your logic app workflow uses at runtime. You can then reference these parameters inside your logic app's workflow by using workflow definition expressions, which are evaluated at runtime.
This example template that has multiple secured parameter definitions that use the securestring type:
Parameter name
Description
TemplatePasswordParam
A template parameter that accepts a password that is then passed to the workflow definition's basicAuthPasswordParam parameter
TemplateUsernameParam
A template parameter that accepts a username that is then passed to the workflow definition's basicAuthUserNameParam parameter
basicAuthPasswordParam
A workflow definition parameter that accepts the password for basic authentication in an HTTP action
basicAuthUserNameParam
A workflow definition parameter that accepts the username for basic authentication in an HTTP action
Access for inbound calls to request-based triggers
Inbound calls that a logic app receives through a request-based trigger, such as the Request trigger or HTTP Webhook trigger, support encryption and are secured with Transport Layer Security (TLS) 1.2 at minimum, previously known as Secure Sockets Layer (SSL). Azure Logic Apps enforces this version when receiving an inbound call to a Request trigger or a callback to the HTTP Webhook trigger or action.
Note
If you get TLS handshake errors, make sure that you use TLS 1.2. For more information, see Solving the TLS 1.0 problem.
For inbound calls, use the following cipher suites:
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Important
For backward compatibility, Azure Logic Apps currently supports some older cipher suites. However, don't use
older cipher suites when you develop new apps because such suites might not be supported in the future.
For example, you might find the following cipher suites if you inspect the TLS handshake messages in Azure
Logic Apps or by using a security tool on your logic app's URL. Again, don't use these older suites:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
The following list includes ways that you can limit access to triggers that receive inbound calls to your logic app workflow so that only authorized clients can call your workflow:
When your logic app workflow receives an inbound request that includes an OAuth access token, Azure Logic Apps compares the token's claims against the claims specified by each authorization policy. If a match exists between the token's claims and all the claims in at least one policy, authorization succeeds for the inbound request. The token can have more claims than the number specified by the authorization policy.
In a Standard workflow that starts with the Request trigger (but not a webhook trigger), you can use the Azure Functions provision for authenticating inbound calls sent to the endpoint created by the Request trigger by using a managed identity. This provision is also known as "Easy Auth". For more information, see Trigger workflows in Standard logic apps with Easy Auth.
Considerations before you enable OAuth 2.0 with Microsoft Entra ID
In Consumption workflows, inbound calls to the endpoint URL for a request-based trigger can use only one authorization scheme, either OAuth 2.0 with Microsoft Entra ID or Shared Access Signature (SAS). Although using one scheme doesn't disable the other scheme, if you use both schemes at the same time, Azure Logic Apps generates an error because the service doesn't know which scheme to choose. If your Consumption workflow starts with the Request trigger, you can disable SAS authentication as well as restrict authorization to use only OAuth 2.0 with Microsoft Entra ID. For Standard workflows, you can use other authentication types without disabling SAS.
Your Consumption logic app resource is limited to a maximum number of authorization policies. Each authorization policy also has a maximum number of claims. For more information, see Limits and configuration for Azure Logic Apps.
An authorization policy must include at least the Issuer claim, which has a value that starts with either https://sts.windows.net/ or https://login.microsoftonline.com/ (OAuth V2) as the issuer for Microsoft Entra ID.
For example, suppose that your logic app resource has an authorization policy that requires two claim types, Audience and Issuer. This sample payload section for a decoded access token includes both claim types where aud is the Audience value and iss is the Issuer value:
This step makes the Authorization header visible in the workflow's run history and in the trigger's outputs.
In the Azure portal, open your Consumption workflow in the designer.
On the designer, select the trigger. On the information pane that opens, select Settings.
Under General > Trigger conditions, select Add. In the trigger condition box, enter either of the following expressions, based on the token type that you want to use:
If you call the trigger endpoint without the correct authorization, the run history just shows the trigger as Skipped without any message that the trigger condition has failed.
Get a Proof-of-Possession (PoP) token
The Microsoft Authentication Library (MSAL) libraries provide PoP tokens for you to use. If the Consumption logic app workflow that you want to call requires a PoP token, you can get this token using the MSAL libraries. The following samples show how to acquire PoP tokens:
In the Azure portal, open your Consumption logic app and workflow in the designer.
On the logic app menu, under Settings, select Authorization.
On the Authorization page, select Add policy.
Provide information about the authorization policy by specifying the claim types and values that your logic app expects in the access token presented by each inbound call to the Request trigger:
Property
Required
Type
Description
Policy name
Yes
String
The name that you want to use for the authorization policy
Policy type
Yes
String
Either AAD for bearer type tokens or AADPOP for Proof-of-Possession type tokens.
Claims
Yes
String
A key-value pair that specifies the claim type and value that the workflow's Request trigger expects in the access token presented by each inbound call to the trigger. You can add any standard claim you want by selecting Add standard claim. To add a claim that's specific to a PoP token, select Add custom claim.
Available standard claim types:
- Issuer - Audience - Subject - JWT ID (JSON Web Token identifier)
Requirements:
- At a minimum, the Claims list must include the Issuer claim, which has a value that starts with https://sts.windows.net/ or https://login.microsoftonline.com/ as the Microsoft Entra issuer ID.
- Each claim must be a single string value, not an array of values. For example, you can have a claim with Role as the type and Developer as the value. You can't have a claim that has Role as the type and the values set to Developer and Program Manager.
The following example shows the information for a PoP token:
To add another claim, select from these options:
To add another claim type, select Add standard claim, select the claim type, and specify the claim value.
To add your own claim, select Add custom claim. For more information, review how to provide optional claims to your app. Your custom claim is then stored as a part of your JWT ID; for example, "tid": "aaaabbbb-0000-cccc-1111-dddd2222eeee".
To add another authorization policy, select Add policy. Repeat the previous steps to set up the policy.
Workflow properties such as policies don't appear in your workflow's code view in the Azure portal. To access your policies programmatically, call the following API through Azure Resource Manager: https://management.azure.com/subscriptions/{Azure-subscription-ID}/resourceGroups/{Azure-resource-group-name}/providers/Microsoft.Logic/workflows/{your-workflow-name}?api-version=2016-10-01&_=1612212851820. Make sure that you replace the placeholder values for your Azure subscription ID, resource group name, and workflow name.
In your ARM template, define an authorization policy following these steps and syntax below:
In the properties section for your logic app's resource definition, add an accessControl object, if none exists, that contains a triggers object.
In the triggers object, add an openAuthenticationPolicies object that contains the policies object where you define one or more authorization policies.
Provide a name for authorization policy, set the policy type to AAD, and include a claims array where you specify one or more claim types.
At a minimum, the claims array must include the Issuer claim type where you set the claim's name property to iss and set the value to start with https://sts.windows.net/ or https://login.microsoftonline.com/ as the Microsoft Entra issuer ID. For more information about these claim types, see Claims in Microsoft Entra security tokens. You can also specify your own claim type and value.
Include 'Authorization' header in Request or HTTP webhook trigger outputs
For logic apps that enable OAuth with Microsoft Entra ID for authorizing inbound calls to access request-based triggers, you can enable the Request trigger or HTTP Webhook trigger outputs to include the Authorization header from the OAuth access token. In the trigger's underlying JSON definition, add and set the operationOptions property to IncludeAuthorizationHeadersInOutputs. Here's an example for the Request trigger:
Generate a shared access signature (SAS) key or token
When a workflow starts with a request-based trigger, and you save that workflow for the first time, Azure Logic Apps creates a callable endpoint on that trigger. This endpoint has a URL that can receive inbound calls or requests to start the workflow. The URL includes a Shared Access Signature (SAS), which is a key or token that grants permissions, for example, to storage services. This endpoint URL uses the following format:
The SAS in the URL has query parameters, which the following table describes:
Query parameter
Description
sp
Specifies permissions for the allowed HTTP methods to use.
sv
Specifies the SAS version to use for generating the signature.
sig
Specifies the signature to use for authenticating access to the trigger. This signature is generated by using the SHA256 algorithm with a secret access key on all the URL paths and properties. This key is kept secret and encrypted, stored with the logic app, and is never exposed or published. Your logic app authorizes only those triggers that contain a valid signature created with the secret key.
Important
Make sure to protect your SAS key just as you protect an account key from unauthorized use. Set up or have a plan
for revoking a compromised access key. Use discretion when you distribute URIs that use access keys, and only
distribute such URIs over a secure connection such as HTTPS. Make sure to only perform operations that use an access
key over an HTTPS connection. Anyone that has a URI with valid key can access the associated resource. To maintain
security and protect access to your logic app workflow, regenerate access keys on a regular
schedule as they might need to comply with security policies or become compromised. This way, you can make sure that
only authorized requests can trigger your workflow, which protects your data and processes from unauthorized access.
Inbound calls to the endpoint on a request-based trigger can use only one authorization scheme, either SAS or OAuth 2.0 with Microsoft Entra ID. Although using one scheme doesn't disable the other, if you use both schemes at the same time, Azure Logic Apps generates an error because the service doesn't know which scheme to choose.
By default, a request-based trigger has SAS authentication enabled. The trigger's endpoint URL includes an SAS, starting with the query parameters, sp-<permissions>sv-<SAS-version>sig=<signature>, for example:
If your Consumption workflow starts with the Request trigger, and you want to use OAuth with Microsoft Entra ID, you can disable SAS authentication to avoid errors and problems running your workflow. You also add a security layer by removing the dependency on secrets, which reduces the risk in having secrets logged or leaked.
This action disables SAS authentication for incoming requests and blocks existing SAS keys or
signatures from working. However, your SAS keys or signatures remain valid and still work if you
enable SAS authentication again. To disable SAS keys and signatures by creating new versions, see
Regenerate access keys.
After you disable SAS authentication, the endpoint URL for the Request trigger no longer includes the SAS key, for example:
For scenarios where you have sensitive data, such as credentials, secrets, access tokens,
API keys, and other similar information, make sure to use a tool that protects your data
with the necessary security features, works offline or locally, doesn't sync your data to
the cloud, and doesn't require that you sign in to an online account. This way, you reduce
the risk around exposing sensitive data to the public.
Check for triggers with SAS enabled or disabled
When SAS authentication is disabled, the trigger's endpoint URL doesn't include the SAS key anymore. Also, the Consumption workflow definition includes the sasAuthenticationPolicy JSON object. This object has a state property that is set to Disabled, for example:
To find Consumption workflows where SAS is either enabled or disabled, check whether the workflow definition includes the sasAuthenticationPolicy object where the state property is set to Disabled.
With your tool that sends REST API calls, get information about your workflow by running the Workflows - Get operation using the following GET request, for example:
GET https://management.azure.com/subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/workflows/{workflow-name}?api-version=2016-06-01
Take the output from the Workflows - Get operation, and check whether the sasAuthenticationPolicy object exists where the state property is set to Disabled.
Add the sasAuthenticationPolicy property to your workflow definition
For Consumption workflows where you want to disable SAS authentication, follow these steps:
If you haven't done so already, get information about your workflow by running the Workflows - Get operation using the following GET request, for example:
GET https://management.azure.com/subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/workflows/{workflow-name}?api-version=2016-06-01
Take the output from the Workflows - Get operation, and manually add the following elements:
In the properties object, add an accessControl object that contains a triggers object, if none exists.
In the triggers object, add an sasAuthenticationPolicy object that contains the state property set to Disabled.
When you finish, the edited part looks like the following example:
Send another request to update your workflow with the edited output, which you use as input in the request body, by running the Workflows - Update operation using the following PUT request, for example:
PUT https://management.azure.com/subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/workflows/{workflow-name}?api-version=2016-06-01
In the Azure portal, go to your Consumption workflow in the designer, and confirm that the Request trigger's URL no longer includes the SAS.
To maintain security and protect access to your logic app workflow, regenerate access keys on a regular schedule as they might need to comply with security policies or become compromised. This way, you can make sure that only authorized requests can trigger your workflow, which protects your data and processes from unauthorized access.
To generate a new access key at any time, use the Azure REST API or Azure portal. All previously generated URIs or URLs that use the old key are invalidated and no longer have authorization to trigger your logic app workflow. The URIs that you retrieve after regeneration are signed with the new access key.
In the Azure portal, open the logic app resource that uses the key you want to regenerate.
On the logic app resource menu, under Settings, select Access Keys.
Select the key that you want to regenerate and finish the process.
Important
Make sure to protect your access key just as you protect an account key from unauthorized use. Set up or have a plan
for revoking a compromised access key. Use discretion when you distribute URIs that use access keys, and only
distribute such URIs over a secure connection such as HTTPS. Make sure to only perform operations that use an access
key over an HTTPS connection. Anyone that has a URI with valid key can access the associated resource.
If you share the endpoint URL for a request-based trigger with other parties, you can generate callback URLs that use specific keys and have expiration dates. That way, you can seamlessly roll keys or restrict access to triggering your logic app based on a specific timespan. To specify an expiration date for a URL, use the Azure Logic Apps REST API, for example:
POST /subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/workflows/{workflow-name}/triggers/{trigger-name}/listCallbackUrl?api-version=2016-06-01
In the body, include the NotAfter property by using a JSON date string. This property returns a callback URL that's valid only until the NotAfter date and time.
Create URLs with primary or secondary secret key
When you generate or list callback URLs for a request-based trigger, you can specify the key to use for signing the URL. To generate a URL that's signed by a specific key, use the Azure Logic Apps REST API, for example:
POST /subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/workflows/{workflow-name}/triggers/{trigger-name}/listCallbackUrl?api-version=2016-06-01
In the body, include the KeyType property as either Primary or Secondary. This property returns a URL that's signed by the specified security key.
Expose your logic app workflow with Azure API Management
For more authentication protocols and options, consider exposing your logic app workflow as an API by using Azure API Management. This service provides rich monitoring, security, policy, and documentation capabilities for any endpoint. API Management can expose a public or private endpoint for your logic app. To authorize access to this endpoint, you can use OAuth with Microsoft Entra ID, client certificate, or other security standards. When API Management receives a request, the service sends the request to your logic app and makes any necessary transformations or restrictions along the way. To let only API Management call your logic app workflow, you can restrict your logic app's inbound IP addresses.
For more information, see the following documentation:
Along with Shared Access Signature (SAS), you might want to specifically limit the clients that can call your logic app workflow. For example, if you manage your request endpoint by using Azure API Management, you can restrict your logic app workflow to accept requests only from the IP address for the API Management service instance that you create.
Regardless of any IP addresses that you specify, you can still run a logic app workflow that has a request-based trigger by using the Workflow Triggers - Run operation request or by using API Management. However, this scenario still requires authentication against the Azure REST API. All events appear in the Azure Audit Log. Make sure that you set access control policies accordingly.
To restrict the inbound IP addresses for your logic app workflow, follow the corresponding steps for either the Azure portal or your Azure Resource Manager template. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
In the Azure portal, IP address restriction affects both triggers and actions, contrary to the description in the portal under Allowed inbound IP addresses. To set up this filter separately for triggers and for actions, use the accessControl object in an Azure Resource Manager template for your logic app resource or the Workflow - Create Or Update operation in the Azure Logic Apps REST API.
Consumption workflows
In the Azure portal, open your Consumption logic app in the workflow designer.
On the logic app menu, under Settings, select Workflow settings.
In the Access control configuration section, under Allowed inbound IP addresses, choose the path for your scenario:
To make your workflow callable using the Azure Logic Apps built-in action, but only as a nested workflow, select Only other Logic Apps. This option works only when you use the Azure Logic Apps action to call the nested workflow.
This option writes an empty array to your logic app resource and requires that only calls from parent workflows that use the built-in Azure Logic Apps action can trigger the nested workflow.
To make your workflow callable using the HTTP action, but only as a nested workflow, select Specific IP ranges. When the IP ranges for triggers box appears, enter the parent workflow's outbound IP addresses. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
Note
If you use the Only other Logic Apps option and the HTTP action to call your nested workflow,
the call is blocked, and you get a "401 Unauthorized" error.
For scenarios where you want to restrict inbound calls from other IPs, when the IP ranges for triggers box appears, specify the IP address ranges that the trigger accepts. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
Optionally, under Restrict calls to get input and output messages from run history to the provided IP addresses, you can specify the IP address ranges for inbound calls that can access input and output messages in run history.
Standard workflows
In the Azure portal, open your Standard logic app resource.
On the logic app menu, under Settings, select Networking.
In the Inbound traffic configuration section, next to Public network access, select Enabled with no access restriction.
On the Access restrictions page, under App access, select Enabled from select virtual networks and IP addresses.
Under Site access and rules, on the Main site tab, add one or more rules to either Allow or Deny requests from specific IP ranges. A valid IP range uses these formats: x.x.x.x/x or x.x.x.x-x.x.x.x
In your ARM template, specify the allowed inbound IP address ranges in your logic app's resource definition by using the accessControl section. In this section, use the triggers, actions, and the optional contents sections as appropriate by including the allowedCallerIpAddresses section with the addressRange property and set the property value to the allowed IP range in x.x.x.x/x or x.x.x.x-x.x.x.x format.
If your nested logic app workflow uses the Only other Logic Apps option, which permits inbound calls only from other logic app workflows that use the built-in Azure Logic Apps action, set the allowedCallerIpAddresses property to an empty array ([]), and omit the addressRange property.
If your nested logic app workflow uses the Specific IP ranges option for other inbound calls, such as other logic app workflows that use the HTTP action, include the allowedCallerIpAddresses section, and set the addressRange property to the allowed IP range.
This example shows a logic app resource definition for a nested workflow that permits inbound calls only from other logic app workflows that use the built-in Azure Logic Apps action:
In your ARM template, specify the allowed inbound IP address ranges in your logic app's resource definition by using the Microsoft.Web/sites/config section. In this section, under properties, add the ipSecurityRestrictions section, and use the ipAddress, action="Deny" | "Allow", tag=Default, priority, and name="Ports" sections to define a rule and set the ipAddress to the allowed IP range in x.x.x.x/x or x.x.x.x-x.x.x.x format, for example:
Access for outbound calls to other services and systems
Based on the target endpoint's capability, outbound calls sent by the HTTP trigger or HTTP action, support encryption and are secured with Transport Layer Security (TLS) 1.0, 1.1, or 1.2, previously known as Secure Sockets Layer (SSL). Azure Logic Apps negotiates with the target endpoint over using the highest possible version that's supported. For example, if the target endpoint supports 1.2, the HTTP trigger or action uses 1.2 first. Otherwise, the connector uses the next highest supported version.
This list includes information about TLS/SSL self-signed certificates:
For Consumption logic app workflows in the multitenant Azure Logic Apps environment, HTTP operations don't permit self-signed TLS/SSL certificates. If your logic app makes an HTTP call to a server and presents a TLS/SSL self-signed certificate, the HTTP call fails with a TrustFailure error.
For Standard logic app workflows in the single-tenant Azure Logic Apps environment, HTTP operations support self-signed TLS/SSL certificates. However, you have to complete a few extra steps for this authentication type. Otherwise, the call fails. For more information, review TLS/SSL certificate authentication for single-tenant Azure Logic Apps.
When you use the HTTP trigger or action to send outbound calls, you can add authentication to the request that's sent by your logic app. For example, you can select these authentication types:
Restrict access from logic app workflow IP addresses.
All calls to endpoints from logic app workflows originate from specific designated IP addresses that are based on your logic apps' regions. You can add filtering that accepts requests only from those IP addresses. To get these IP addresses, review Limits and configuration for Azure Logic Apps.
Improve security for connections to on-premises systems.
Azure Logic Apps provides integration with these services to help provide more secure and reliable on-premises communication.
On-premises data gateway
Many managed connectors in Azure Logic Apps facilitate secured connections to on-premises systems, such as File System, SQL, SharePoint, and DB2. The gateway sends data from on-premises sources on encrypted channels through the Azure Service Bus. All traffic originates as secured outbound traffic from the gateway agent. Learn how the on-premises data gateway works.
Connect through Azure API Management
Azure API Management provides on-premises connection options, such as site-to-site virtual private network and ExpressRoute integration for secured proxy and communication to on-premises systems. If you have an API that provides access to your on-premises system, and you exposed that API by creating an API Management service instance, you can call that API from your logic app's workflow by selecting the corresponding API Management operation in the workflow designer.
Note
The connector shows only those API Management services where you have permissions to view and connect,
but doesn't show consumption-based API Management services.
Based on your logic app resource type, follow the corresponding steps:
Consumption workflows
Based on whether you're adding an API Management trigger or action, follow these steps:
Trigger:
On the workflow designer, select Add a trigger.
After the Add a trigger pane opens, in the search box, enter API Management.
From the trigger results list, select Choose an Azure API Management Trigger.
Action:
On the workflow designer, select the plus sign (+) where you want to add the action.
After the Add an action pane opens, in the search box, enter API Management.
From the action results list, select Choose an Azure API Management action.
The following example shows finding an Azure API Management trigger:
From the API Management service instance list, select your previously created API Management service instance.
From the API operations list, select the API operation to call, and then select Add Action.
Standard workflows
For Standard workflows, you can only add API Management actions, not triggers.
On the workflow designer, select the plus sign (+) where you want to add the action.
After the Add an action pane opens, in the search box, enter API Management.
From the action results list, select Call an Azure API Management API.
From the API Management service instance list, select your previously created API Management service instance.
From the API operations list, select the API operation to call, and then select Create New.
Add authentication to outbound calls
HTTP and HTTPS endpoints support various kinds of authentication. On some triggers and actions that you use for sending outbound calls or requests to these endpoints, you can specify an authentication type. In the workflow designer, triggers and actions that support choosing an authentication type have an Authentication property. However, this property might not always appear by default. In these cases, on the trigger or action, open the Advanced parameters list, and select Authentication.
Important
To protect sensitive information that your logic app workflow handles, use secured parameters and encode data as necessary.
For more information about using and securing parameters, review Access to parameter inputs.
For HTTP calls, basic authentication uses a base64-encoded string that contains a username and password to make a request. This method transmits credentials without encryption and poses increased security risks unless you use this option with the HTTPS/SSL protocol.
Client certificate authentication allows or requires users to authenticate directly with X.509 certificates against their Microsoft Entra ID for applications and browser sign-in. This capability helps you adopt a phishing resistant authentication and authenticate with an X.509 certificate against your Public Key Infrastructure (PKI).
If you have a Standard logic app resource in single-tenant Azure Logic Apps, and you want to use an HTTP
operation with a TSL/SSL certificate, client certificate, or Microsoft Entra ID Open Authentication
(Microsoft Entra ID OAuth) with the Certificate credential type, make sure to complete the extra setup
steps for this authentication type. Otherwise, the call fails. For more information, review
Authentication in single-tenant environment.
For more information about securing services by using client certificate authentication, review these topics:
On all other triggers and actions that support the Active Directory OAuth (OAuth 2.0 with Microsoft Entra ID) authentication type, specify these property values:
Property (designer)
Property (JSON)
Required
Value
Description
Authentication
type
Yes
Active Directory OAuth (OAuth 2.0 with Microsoft Entra ID) or ActiveDirectoryOAuth
The authentication type to use. Azure Logic Apps currently follows the OAuth 2.0 protocol.
The resource that you want to use for authorization, for example, https://management.core.windows.net/
Client ID
clientId
Yes
<client-ID>
The client ID for the app requesting authorization
Credential Type
credentialType
Yes
Certificate or Secret
The credential type that the client uses for requesting authorization. This property and value don't appear in your logic app's underlying definition, but determines the properties that appear for the selected credential type.
Secret
secret
Yes, but only for the "Secret" credential type
<client-secret>
The client secret for requesting authorization
Pfx
pfx
Yes, but only for the "Certificate" credential type
<encoded-pfx-file-content>
The base64-encoded content from a Personal Information Exchange (PFX) file
Password
password
Yes, but only for the "Certificate" credential type
<password-for-pfx-file>
The password for accessing the PFX file
When you use secured parameters to handle and secure sensitive information, for example, in an Azure Resource Manager template for automating deployment, you can use expressions to access these parameter values at runtime. This example HTTP action definition specifies the authentication type as ActiveDirectoryOAuth, the credential type as Secret, and uses the parameters() function to get the parameter values:
If you have a Standard logic app resource in single-tenant Azure Logic Apps, and you want to use an HTTP
operation with a TSL/SSL certificate, client certificate, or Microsoft Entra ID OAuth with the Certificate
credential type, make sure to complete the extra setup steps for this authentication type. Otherwise, the call
fails. For more information, see Authentication in single-tenant environment.
Raw authentication
If the Raw option is available, you can use this authentication type when you have to use authentication schemes that don't follow the OAuth 2.0 protocol. With this type, you manually create the authorization header value that you send with the outgoing request, and specify that header value in your trigger or action.
By default, the system-assigned identity is already enabled to authenticate connections at run time.
This identity differs from the authentication credentials or connection string that you use when you
create a connection. If you disable this identity, connections won't work at run time. To view
this setting, on your logic app menu, under Settings, select Identity.
In the trigger or action that supports using a managed identity, provide this information:
Built-in triggers and actions
Property (designer)
Property (JSON)
Required
Value
Description
Authentication
type
Yes
Managed Identity or ManagedServiceIdentity
The authentication type to use
Managed Identity
identity
No
<user-assigned-identity-ID>
The user-assigned managed identity to use. Note: Don't include this property when using the system-assigned managed identity.
Audience
audience
Yes
<target-resource-ID>
The resource ID for the target resource that you want to access.
For example, https://storage.azure.com/ makes the access tokens for authentication valid for all storage accounts. However, you can also specify a root service URL, such as https://fabrikamstorageaccount.blob.core.windows.net for a specific storage account.
Note: The Audience property might be hidden in some triggers or actions. To make this property visible, in the trigger or action, open the Advanced parameters list, and select Audience.
Important: Make sure that this target resource ID exactly matches the value that Microsoft Entra ID expects, including any required trailing slashes. So, the https://storage.azure.com/ resource ID for all Azure Blob Storage accounts requires a trailing slash. However, the resource ID for a specific storage account doesn't require a trailing slash. To find these resource IDs, review Azure services that support Microsoft Entra ID.
When you use secured parameters to handle and secure sensitive information, for example, in an Azure Resource Manager template for automating deployment, you can use expressions to access these parameter values at runtime. For example, this HTTP action definition specifies the authentication type as ManagedServiceIdentity and uses the parameters() function to get the parameter values:
You can use Azure Logic Apps in Azure Government supporting all impact levels in the regions described by the Azure Government Impact Level 5 Isolation Guidance. To meet these requirements, Azure Logic Apps supports the capability for you to create and run workflows in an environment with dedicated resources so that you can reduce the performance impact by other Azure tenants on your logic apps and avoid sharing computing resources with other tenants.
For example, to meet Impact Level 5 requirements, create your function app with the App Service plan using the Isolated pricing tier along with an App Service Environment (ASE) that also uses the Isolated pricing tier. In this environment, function apps run on dedicated Azure virtual machines and dedicated Azure virtual networks, which provide network isolation on top of compute isolation for your apps and maximum scale-out capabilities.
For more information, review the following documentation: