Microsoft.Logic integrationAccounts/maps 2019-05-01

• Latest
• 2019-05-01
• 2018-07-01-preview
• 2016-06-01
• 2015-08-01-preview

Bicep resource definition

The integrationAccounts/maps 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/maps resource, add the following Bicep to your template.

resource symbolicname 'Microsoft.Logic/integrationAccounts/maps@2019-05-01' = {
  parent: resourceSymbolicName
  location: 'string'
  name: 'string'
  properties: {
    content: 'string'
    contentType: 'string'
    mapType: 'string'
    metadata: any(Azure.Bicep.Types.Concrete.AnyType)
    parametersSchema: {
      ref: 'string'
    }
  }
  tags: {
    {customized property}: 'string'
  }
}

Property values

IntegrationAccountMapProperties

Name	Description	Value
content	The content.	string
contentType	The content type.	string
mapType	The map type.	'Liquid' 'NotSpecified' 'Xslt' 'Xslt20' 'Xslt30' (required)
metadata	The metadata.	any
parametersSchema	The parameters schema of integration account map.	IntegrationAccountMapPropertiesParametersSchema

IntegrationAccountMapPropertiesParametersSchema

Name	Description	Value
ref	The reference name.	string

Microsoft.Logic/integrationAccounts/maps

Name	Description	Value
location	The resource location.	string
name	The resource name	string (required)
parent	In Bicep, you can specify the parent resource for a child resource. You only need to add this property when the child resource is declared outside of the parent resource. For more information, see Child resource outside parent resource.	Symbolic name for resource of type: integrationAccounts
properties	The integration account map properties.	IntegrationAccountMapProperties (required)
tags	Resource tags	Dictionary of tag names and values. See Tags in templates

ResourceTags

Name	Description	Value

ARM template resource definition

The integrationAccounts/maps 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/maps resource, add the following JSON to your template.

{
  "type": "Microsoft.Logic/integrationAccounts/maps",
  "apiVersion": "2019-05-01",
  "name": "string",
  "location": "string",
  "properties": {
    "content": "string",
    "contentType": "string",
    "mapType": "string",
    "metadata": {},
    "parametersSchema": {
      "ref": "string"
    }
  },
  "tags": {
    "{customized property}": "string"
  }
}

Property values

IntegrationAccountMapProperties

Name	Description	Value
content	The content.	string
contentType	The content type.	string
mapType	The map type.	'Liquid' 'NotSpecified' 'Xslt' 'Xslt20' 'Xslt30' (required)
metadata	The metadata.	any
parametersSchema	The parameters schema of integration account map.	IntegrationAccountMapPropertiesParametersSchema

IntegrationAccountMapPropertiesParametersSchema

Name	Description	Value
ref	The reference name.	string

Microsoft.Logic/integrationAccounts/maps

Name	Description	Value
apiVersion	The api version	'2019-05-01'
location	The resource location.	string
name	The resource name	string (required)
properties	The integration account map properties.	IntegrationAccountMapProperties (required)
tags	Resource tags	Dictionary of tag names and values. See Tags in templates
type	The resource type	'Microsoft.Logic/integrationAccounts/maps'

ResourceTags

Name	Description	Value

Quickstart templates

The following quickstart templates deploy this resource type.

Template	Description
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/maps 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/maps resource, add the following Terraform to your template.

resource "azapi_resource" "symbolicname" {
  type = "Microsoft.Logic/integrationAccounts/maps@2019-05-01"
  name = "string"
  location = "string"
  tags = {
    {customized property} = "string"
  }
  body = jsonencode({
    properties = {
      content = "string"
      contentType = "string"
      mapType = "string"
      metadata = ?
      parametersSchema = {
        ref = "string"
      }
    }
  })
}

Property values

IntegrationAccountMapProperties

Name	Description	Value
content	The content.	string
contentType	The content type.	string
mapType	The map type.	'Liquid' 'NotSpecified' 'Xslt' 'Xslt20' 'Xslt30' (required)
metadata	The metadata.	any
parametersSchema	The parameters schema of integration account map.	IntegrationAccountMapPropertiesParametersSchema

IntegrationAccountMapPropertiesParametersSchema

Name	Description	Value
ref	The reference name.	string

Microsoft.Logic/integrationAccounts/maps

Name	Description	Value
location	The resource location.	string
name	The resource name	string (required)
parent_id	The ID of the resource that is the parent for this resource.	ID for resource of type: integrationAccounts
properties	The integration account map properties.	IntegrationAccountMapProperties (required)
tags	Resource tags	Dictionary of tag names and values.
type	The resource type	"Microsoft.Logic/integrationAccounts/maps@2019-05-01"

ResourceTags

Name	Description	Value