Share via

Microsoft.OperationalInsights workspaces/linkedServices 2020-08-01

  • Article

Bicep resource definition

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

resource symbolicname 'Microsoft.OperationalInsights/workspaces/linkedServices@2020-08-01' = {
  name: 'string'
  tags: {
    tagName1: 'tagValue1'
    tagName2: 'tagValue2'
  }
  parent: resourceSymbolicName
  properties: {
    provisioningState: 'string'
    resourceId: 'string'
    writeAccessResourceId: 'string'
  }
}

Property values

workspaces/linkedServices

Name Description Value
name The resource name

See how to set names and types for child resources in Bicep.		 string (required)
tags Resource tags. Dictionary of tag names and values. See Tags in templates
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: workspaces
properties The properties of the linked service. LinkedServiceProperties (required)

LinkedServiceProperties

Name Description Value
provisioningState The provisioning state of the linked service. 'Deleting'
'ProvisioningAccount'
'Succeeded'
'Updating'
resourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require read access string
writeAccessResourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require write access string

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Create Azure Automation account

Deploy to Azure		 This template provides an example of how create an Azure Automation account and links it to a new or existing Azure Monitor Log Analytics workspace.
Log Analytics workspace with solutions and data sources

Deploy to Azure		 Deploys a Log Analytics workspace with specified solutions and data sources

ARM template resource definition

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

{
  "type": "Microsoft.OperationalInsights/workspaces/linkedServices",
  "apiVersion": "2020-08-01",
  "name": "string",
  "tags": {
    "tagName1": "tagValue1",
    "tagName2": "tagValue2"
  },
  "properties": {
    "provisioningState": "string",
    "resourceId": "string",
    "writeAccessResourceId": "string"
  }
}

Property values

workspaces/linkedServices

Name Description Value
type The resource type 'Microsoft.OperationalInsights/workspaces/linkedServices'
apiVersion The resource api version '2020-08-01'
name The resource name

See how to set names and types for child resources in JSON ARM templates.		 string (required)
tags Resource tags. Dictionary of tag names and values. See Tags in templates
properties The properties of the linked service. LinkedServiceProperties (required)

LinkedServiceProperties

Name Description Value
provisioningState The provisioning state of the linked service. 'Deleting'
'ProvisioningAccount'
'Succeeded'
'Updating'
resourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require read access string
writeAccessResourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require write access string

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Create Azure Automation account

Deploy to Azure		 This template provides an example of how create an Azure Automation account and links it to a new or existing Azure Monitor Log Analytics workspace.
Log Analytics workspace with solutions and data sources

Deploy to Azure		 Deploys a Log Analytics workspace with specified solutions and data sources

Terraform (AzAPI provider) resource definition

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

resource "azapi_resource" "symbolicname" {
  type = "Microsoft.OperationalInsights/workspaces/linkedServices@2020-08-01"
  name = "string"
  parent_id = "string"
  tags = {
    tagName1 = "tagValue1"
    tagName2 = "tagValue2"
  }
  body = jsonencode({
    properties = {
      provisioningState = "string"
      resourceId = "string"
      writeAccessResourceId = "string"
    }
  })
}

Property values

workspaces/linkedServices

Name Description Value
type The resource type "Microsoft.OperationalInsights/workspaces/linkedServices@2020-08-01"
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: workspaces
tags Resource tags. Dictionary of tag names and values.
properties The properties of the linked service. LinkedServiceProperties (required)

LinkedServiceProperties

Name Description Value
provisioningState The provisioning state of the linked service. "Deleting"
"ProvisioningAccount"
"Succeeded"
"Updating"
resourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require read access string
writeAccessResourceId The resource id of the resource that will be linked to the workspace. This should be used for linking resources which require write access string