Microsoft.OperationalInsights workspaces/linkedServices

The workspaces/linkedServices resource type can be deployed to: Resource groups.

To learn about resource group deployments, see Bicep or ARM template.

Template format

To create a Microsoft.OperationalInsights/workspaces/linkedServices resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.OperationalInsights/workspaces/linkedServices@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

For Bicep, set this value in the resource declaration.
'Microsoft.OperationalInsights/workspaces/linkedServices'
apiVersion The resource api version

For Bicep, set this value in the resource declaration.
'2020-08-01'
name The resource name

See how to set names and types for child resources in Bicep or JSON ARM templates.
string (required)
tags Resource tags. Dictionary of tag names and values. See Tags in templates
properties Linked service properties. 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.