Microsoft.Logic integrationAccounts 2016-06-01
Bicep resource definition
The integrationAccounts resource type can be deployed with operations that target:
- Resource groups - See resource group deployment commands
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.Logic/integrationAccounts resource, add the following Bicep to your template.
resource symbolicname 'Microsoft.Logic/integrationAccounts@2016-06-01' = {
location: 'string'
name: 'string'
properties: any(Azure.Bicep.Types.Concrete.AnyType)
sku: {
name: 'string'
}
tags: {
{customized property}: 'string'
}
}
Property values
IntegrationAccountSku
Name | Description | Value |
---|---|---|
name | The sku name. | 'Free' 'NotSpecified' 'Standard' (required) |
Microsoft.Logic/integrationAccounts
Name | Description | Value |
---|---|---|
location | The resource location. | string |
name | The resource name | string (required) |
properties | The integration account properties. | any |
sku | The sku. | IntegrationAccountSku |
tags | Resource tags | Dictionary of tag names and values. See Tags in templates |
ResourceTags
Name | Description | Value |
---|
Quickstart samples
The following quickstart samples deploy this resource type.
Bicep File | Description |
---|---|
Azure Logic Apps - AS2 Send Receive | Creates integration accounts for two partners, Contoso and Fabrikam, including the artifacts for partners and agreements. The template also creates logic apps between Fabrikam Sales and Contoso to demonstrate synchronous AS2 Send Receive. The template also creates logic apps between Fabrikam Finance and Contoso, which demonstrate asynchronous AS2 Send Receive. |
ARM template resource definition
The integrationAccounts resource type can be deployed with operations that target:
- Resource groups - See resource group deployment commands
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.Logic/integrationAccounts resource, add the following JSON to your template.
{
"type": "Microsoft.Logic/integrationAccounts",
"apiVersion": "2016-06-01",
"name": "string",
"location": "string",
"properties": {},
"sku": {
"name": "string"
},
"tags": {
"{customized property}": "string"
}
}
Property values
IntegrationAccountSku
Name | Description | Value |
---|---|---|
name | The sku name. | 'Free' 'NotSpecified' 'Standard' (required) |
Microsoft.Logic/integrationAccounts
Name | Description | Value |
---|---|---|
apiVersion | The api version | '2016-06-01' |
location | The resource location. | string |
name | The resource name | string (required) |
properties | The integration account properties. | any |
sku | The sku. | IntegrationAccountSku |
tags | Resource tags | Dictionary of tag names and values. See Tags in templates |
type | The resource type | 'Microsoft.Logic/integrationAccounts' |
ResourceTags
Name | Description | Value |
---|
Quickstart templates
The following quickstart templates deploy this resource type.
Template | Description |
---|---|
Azure Logic Apps - AS2 Send Receive |
Creates integration accounts for two partners, Contoso and Fabrikam, including the artifacts for partners and agreements. The template also creates logic apps between Fabrikam Sales and Contoso to demonstrate synchronous AS2 Send Receive. The template also creates logic apps between Fabrikam Finance and Contoso, which demonstrate asynchronous AS2 Send Receive. |
Azure Logic Apps - B2B Disaster Recovery replication |
Creates replication Logic Apps for AS2 MIC, generated and received X12 control numbers. Each Logic App's trigger points to a primary site integration account. Each Logic App's action points to a secondary site integration account. |
Azure Logic Apps - VETER Pipeline |
Creates an integration account, adds schema/map into it, creates a logic app and associates it with the integration account. The logic app implements a VETER pipeline using Xml Validation, XPath Extract and Transform Xml operations. |
Azure Logic Apps - XSLT with parameters |
Creates a request-response Logic App which performs XSLT based transformation. The XSLT map takes primitives (integer, string etc.) as input parameters as uses them during XML transformation. |
Terraform (AzAPI provider) resource definition
The integrationAccounts resource type can be deployed with operations that target:
- Resource groups
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.Logic/integrationAccounts resource, add the following Terraform to your template.
resource "azapi_resource" "symbolicname" {
type = "Microsoft.Logic/integrationAccounts@2016-06-01"
name = "string"
location = "string"
sku = {
name = "string"
}
tags = {
{customized property} = "string"
}
body = jsonencode({
properties = ?
})
}
Property values
IntegrationAccountSku
Name | Description | Value |
---|---|---|
name | The sku name. | 'Free' 'NotSpecified' 'Standard' (required) |
Microsoft.Logic/integrationAccounts
Name | Description | Value |
---|---|---|
location | The resource location. | string |
name | The resource name | string (required) |
properties | The integration account properties. | any |
sku | The sku. | IntegrationAccountSku |
tags | Resource tags | Dictionary of tag names and values. |
type | The resource type | "Microsoft.Logic/integrationAccounts@2016-06-01" |
ResourceTags
Name | Description | Value |
---|