Challenge with Azure Log Analytics Workspace (LAW) and LACluster SKU in Automated Workflow

Question

Challenge with Azure Log Analytics Workspace (LAW) and LACluster SKU in Automated Workflow

Abhishek Arya 0 Microsoft Employee

We are implementing an Azure monitoring solution for one of our customers. The architecture requires that the Log Analytics Workspace (LAW) be configured with the LACluster SKU and linked to a dedicated cluster for log ingestion.

Issue: Initial Deployment Constraints

When provisioning the LAW for the first time with SKU set to LACluster, the deployment fails because the workspace is not yet linked to a cluster.
However, if we initially set the SKU to Pay-As-You-Go (PAYG), the deployment succeeds, allowing us to link the workspace to the dedicated cluster.
After 2-3 hours, the workspace automatically upgrades its SKU from Pay-As-You-Go to LACluster as expected.

Issue: Subsequent Workflow Runs

When running the workflow again, the deployment fails because the LAW is now linked to the cluster.
The error states that the SKU cannot be changed back to Pay-As-You-Go since the workspace is already associated with a cluster.
A workaround is to modify the SKU dynamically in the parameter file before the second run (i.e., set it to LACluster instead of Pay-As-You-Go), but the customer does not want parameter file modifications.

Question

How can we handle this scenario in an automated deployment workflow while ensuring:

The initial deployment succeeds without manual intervention.
The workflow runs successfully on subsequent deployments without modifying the parameter file.
The SKU remains compliant with LACluster without breaking the deployment process.

Would appreciate insights on best practices to handle this within Bicep or Terraform while maintaining idempotency in Azure Infrastructure as Code. 🚀We are implementing an Azure monitoring solution for one of our customers. The architecture requires that the Log Analytics Workspace (LAW) be configured with the LACluster SKU and linked to a dedicated cluster for log ingestion.

Issue: Initial Deployment Constraints

When provisioning the LAW for the first time with SKU set to LACluster, the deployment fails because the workspace is not yet linked to a cluster.
However, if we initially set the SKU to Pay-As-You-Go (PAYG), the deployment succeeds, allowing us to link the workspace to the dedicated cluster.
After 2-3 hours, the workspace automatically upgrades its SKU from Pay-As-You-Go to LACluster as expected.

Issue: Subsequent Workflow Runs

When running the workflow again, the deployment fails because the LAW is now linked to the cluster.
The error states that the SKU cannot be changed back to Pay-As-You-Go since the workspace is already associated with a cluster.
A workaround is to modify the SKU dynamically in the parameter file before the second run (i.e., set it to LACluster instead of Pay-As-You-Go), but the customer does not want parameter file modifications.

Question

How can we handle this scenario in an automated deployment workflow while ensuring:

The initial deployment succeeds without manual intervention.
The workflow runs successfully on subsequent deployments without modifying the parameter file.
The SKU remains compliant with LACluster without breaking the deployment process.

Would appreciate insights on best practices to handle this within Bicep while maintaining idempotency in Azure Infrastructure as Code.

Naveena Patlolla 1,720 Microsoft External Staff

Hi Abhishek Arya

When using Bicep/Terraform we need to use dependson.

Let's say if you are creating a storage account, first we need to create RG first then network security group.

// Define parameters for resource group name and location 
param resourceGroupName string = 'example-resourcesss' 
param location string = 'West Europe' 
// Create the resource group resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = {   
name: resourceGroupName   
location: location 
} 
// Create the network security group 
resource networkSecurityGroup 'Microsoft.Network/networkSecurityGroups@2021-08-01' = {   
name: 'example-security-group'   
location: location   
resourceGroup: resourceGroupName   
dependsOn: [     
resourceGroup // Explicit dependency on the resource group  
] 
}

Create the Log Analytics Cluster
Create the Log Analytics Workspace
Link the Workspace to the Cluster

dependsOn: [     
logAnalyticsWorkspace     
logAnalyticsCluster ]

For best practice, please follow the link below.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/best-practices

If the answer is helpful, please and "Upvote it".

Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-24T04:51:03.1333333+00:00

Hello Abhishek Arya,

I just wanted to check if the provided answer worked for you. If you need any further assistance, please let us know. We are always here to help whenever you need us.

If the answer is helpful, please and "Upvote it".
Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-25T04:39:20.73+00:00

Hello Abhishek Arya,

I would like to check if the issue has been resolved or if you need any assistance. Please feel free to let us know, as we are always here to help.

Additionally, if you have a moment, please review the provided solution.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Thanks
Abhishek Arya 0 Reputation points Microsoft Employee

2025-03-27T08:45:56.18+00:00

@vinod pittala still have the same issue as it is not resolved
Ashok Gandhi Kotnana 5,885 Reputation points Microsoft External Staff

2025-03-27T13:22:26.3633333+00:00
Hi @Abhishek Arya,

Creating a cluster and linking workspaces are asynchronous operations that may take several hours to complete.

During the linking or unlinking process, ingestion and queries remain unaffected and continue to function as usual.

Note: -

The deployment is failing because one resource requires provisioning for two hours before it can be associated with another. This dependency must be completed first.

To resolve this, use dependsOn for each resource, ensuring that the dependent resource is created before the next one.

Creating a cluster involves multiple resources and the operation typically completes in two hours. A dedicated cluster is billed once provisioned regardless of data ingestion and it's recommended to prepare the deployment to expedite the provisioning and workspaces link to the cluster. Verify the following:

A list of initial workspaces to be linked to the cluster is identified

You have permissions to the subscription intended for the cluster and any workspace to be linked Please share your code so we can replicate the issue and provide a solution i have pinged you in private message please share it over in private message

Refer to the below article it has step by step process and limitations how to do it

https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-dedicated-clusters?tabs=bicep
Ashok Gandhi Kotnana 5,885 Reputation points Microsoft External Staff

2025-03-28T13:15:13.91+00:00

Hi @Abhishek Arya,

Just want to check if the above answer worked for you or else please let us know if any help, Let me know if you need any further assistance required?

Thankyou
Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-31T02:25:24.81+00:00

Hello Abhishek Arya,

We haven't heard back from you regarding the solution Ashok Gandhi provided earlier. Could you please let us know if it was helpful? If you have any questions or encounter any issues, please don't hesitate to reach out. We are committed to resolving your concerns as a priority.

Thanks
Abhishek Arya 0 Reputation points Microsoft Employee

2025-03-31T11:19:16.74+00:00

i have used depends on but still face same issue. in initial stage it was completing in 45 minutes without any issue. Now even with 2 hours it's not working. i have updated the timeout to accommodate that.
Madugula Jahnavi 410 Reputation points Microsoft External Staff

2025-04-01T11:05:06.65+00:00

Abhishek Arya, Are you trying to deploy it with az deployment command only or any other approach?
Madugula Jahnavi 410 Reputation points Microsoft External Staff

2025-04-02T08:04:43.7066667+00:00

Abhishek Arya, We haven't heard any response from you. Did you get a chance to look into the above provided comment and if you have any other queries also, feel free to reach out here.

Your answer

Naveena Patlolla 1,720 Reputation points Microsoft External Staff

2025-03-21T22:52:22.87+00:00

Hi Abhishek Arya

When using Bicep/Terraform we need to use dependson.

Let's say if you are creating a storage account, first we need to create RG first then network security group.

// Define parameters for resource group name and location param resourceGroupName string = 'example-resourcesss' param location string = 'West Europe' // Create the resource group resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = { name: resourceGroupName location: location } // Create the network security group resource networkSecurityGroup 'Microsoft.Network/networkSecurityGroups@2021-08-01' = { name: 'example-security-group' location: location resourceGroup: resourceGroupName dependsOn: [ resourceGroup // Explicit dependency on the resource group ] }

Create the Log Analytics Cluster

Create the Log Analytics Workspace

Link the Workspace to the Cluster

dependsOn: [ logAnalyticsWorkspace logAnalyticsCluster ]

For best practice, please follow the link below.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/best-practices

If the answer is helpful, please and "Upvote it".
Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-24T04:51:03.1333333+00:00

Hello Abhishek Arya,

I just wanted to check if the provided answer worked for you. If you need any further assistance, please let us know. We are always here to help whenever you need us.

If the answer is helpful, please and "Upvote it".
Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-25T04:39:20.73+00:00

Hello Abhishek Arya,

I would like to check if the issue has been resolved or if you need any assistance. Please feel free to let us know, as we are always here to help.

Additionally, if you have a moment, please review the provided solution.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Thanks
Abhishek Arya 0 Reputation points Microsoft Employee

2025-03-27T08:45:56.18+00:00

@vinod pittala still have the same issue as it is not resolved
Ashok Gandhi Kotnana 5,885 Reputation points Microsoft External Staff

2025-03-27T13:22:26.3633333+00:00

Hi @Abhishek Arya,

Creating a cluster and linking workspaces are asynchronous operations that may take several hours to complete.

During the linking or unlinking process, ingestion and queries remain unaffected and continue to function as usual.

Note: -

The deployment is failing because one resource requires provisioning for two hours before it can be associated with another. This dependency must be completed first.

To resolve this, use dependsOn for each resource, ensuring that the dependent resource is created before the next one.

Creating a cluster involves multiple resources and the operation typically completes in two hours. A dedicated cluster is billed once provisioned regardless of data ingestion and it's recommended to prepare the deployment to expedite the provisioning and workspaces link to the cluster. Verify the following:

A list of initial workspaces to be linked to the cluster is identified

You have permissions to the subscription intended for the cluster and any workspace to be linked Please share your code so we can replicate the issue and provide a solution i have pinged you in private message please share it over in private message

Refer to the below article it has step by step process and limitations how to do it

https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-dedicated-clusters?tabs=bicep
Ashok Gandhi Kotnana 5,885 Reputation points Microsoft External Staff

2025-03-28T13:15:13.91+00:00

Hi @Abhishek Arya,

Just want to check if the above answer worked for you or else please let us know if any help, Let me know if you need any further assistance required?

Thankyou
Vinod Pittala 1,600 Reputation points Microsoft External Staff

2025-03-31T02:25:24.81+00:00

Hello Abhishek Arya,

We haven't heard back from you regarding the solution Ashok Gandhi provided earlier. Could you please let us know if it was helpful? If you have any questions or encounter any issues, please don't hesitate to reach out. We are committed to resolving your concerns as a priority.

Thanks
Abhishek Arya 0 Reputation points Microsoft Employee

2025-03-31T11:19:16.74+00:00

i have used depends on but still face same issue. in initial stage it was completing in 45 minutes without any issue. Now even with 2 hours it's not working. i have updated the timeout to accommodate that.
Madugula Jahnavi 410 Reputation points Microsoft External Staff

2025-04-01T11:05:06.65+00:00

Abhishek Arya, Are you trying to deploy it with az deployment command only or any other approach?
Madugula Jahnavi 410 Reputation points Microsoft External Staff

2025-04-02T08:04:43.7066667+00:00

Abhishek Arya, We haven't heard any response from you. Did you get a chance to look into the above provided comment and if you have any other queries also, feel free to reach out here.

Share via

Challenge with Azure Log Analytics Workspace (LAW) and LACluster SKU in Automated Workflow

Your answer