Share via

Microsoft.Logic integrationAccounts/schemas

  • Article

Bicep resource definition

The integrationAccounts/schemas resource type can be deployed with operations that target:

For a list of changed properties in each API version, see change log.

Resource format

To create a Microsoft.Logic/integrationAccounts/schemas resource, add the following Bicep to your template.

resource symbolicname 'Microsoft.Logic/integrationAccounts/schemas@2019-05-01' = {
  parent: resourceSymbolicName
  ___location: 'string'
  name: 'string'
  properties: {
    content: 'string'
    contentType: 'string'
    documentName: 'string'
    fileName: 'string'
    metadata: any(...)
    schemaType: 'string'
    targetNamespace: 'string'
  }
  tags: {
    {customized property}: 'string'
  }
}

Property Values

IntegrationAccountSchemaProperties

Name Description Value
content The content. string
contentType The content type. string
documentName The document name. string
fileName The file name. string
metadata The metadata. any
schemaType The schema type. 'NotSpecified'
'Xml' (required)
targetNamespace The target namespace of the schema. string

Microsoft.Logic/integrationAccounts/schemas

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 schema properties. IntegrationAccountSchemaProperties (required)
tags Resource tags Dictionary of tag names and values. See Tags in templates

ResourceTags

Name Description Value

ARM template resource definition

The integrationAccounts/schemas resource type can be deployed with operations that target:

For a list of changed properties in each API version, see change log.

Resource format

To create a Microsoft.Logic/integrationAccounts/schemas resource, add the following JSON to your template.

{
  "type": "Microsoft.Logic/integrationAccounts/schemas",
  "apiVersion": "2019-05-01",
  "name": "string",
  "___location": "string",
  "properties": {
    "content": "string",
    "contentType": "string",
    "documentName": "string",
    "fileName": "string",
    "metadata": {},
    "schemaType": "string",
    "targetNamespace": "string"
  },
  "tags": {
    "{customized property}": "string"
  }
}

Property Values

IntegrationAccountSchemaProperties

Name Description Value
content The content. string
contentType The content type. string
documentName The document name. string
fileName The file name. string
metadata The metadata. any
schemaType The schema type. 'NotSpecified'
'Xml' (required)
targetNamespace The target namespace of the schema. string

Microsoft.Logic/integrationAccounts/schemas

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 schema properties. IntegrationAccountSchemaProperties (required)
tags Resource tags Dictionary of tag names and values. See Tags in templates
type The resource type 'Microsoft.Logic/integrationAccounts/schemas'

ResourceTags

Name Description Value

Usage Examples

Azure Quickstart Templates

The following Azure Quickstart templates deploy this resource type.

Template Description
Azure Logic Apps - VETER Pipeline

Deploy to Azure		 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.

Terraform (AzAPI provider) resource definition

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

resource "azapi_resource" "symbolicname" {
  type = "Microsoft.Logic/integrationAccounts/schemas@2019-05-01"
  name = "string"
  parent_id = "string"
  ___location = "string"
  tags = {
    {customized property} = "string"
  }
  body = {
    properties = {
      content = "string"
      contentType = "string"
      documentName = "string"
      fileName = "string"
      metadata = ?
      schemaType = "string"
      targetNamespace = "string"
    }
  }
}

Property Values

IntegrationAccountSchemaProperties

Name Description Value
content The content. string
contentType The content type. string
documentName The document name. string
fileName The file name. string
metadata The metadata. any
schemaType The schema type. 'NotSpecified'
'Xml' (required)
targetNamespace The target namespace of the schema. string

Microsoft.Logic/integrationAccounts/schemas

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 schema properties. IntegrationAccountSchemaProperties (required)
tags Resource tags Dictionary of tag names and values.
type The resource type "Microsoft.Logic/integrationAccounts/schemas@2019-05-01"

ResourceTags

Name Description Value