az deployment sub what-if shows that Microsoft.Elastic resource has changed but it doesn't

[akorobanov]

Related command

az deployment sub what-if --location northeurope --template-file main.bicep
az deployment sub create as well

part of the elasticCloud bicep template:

resource elasticCloud 'Microsoft.Elastic/monitors@2022-09-01-preview' = {
  name: 'test1301910940'
  location: northeurope
  properties: {
    userInfo: {
      emailAddress: "test@microsoft.com"  // sample email
    }
  }
  sku: {
    name: 'ess-monthly-consumption_Monthly'
  }
}

Describe the bug
If the resource was already created az deployment sub what-if always reports the properties.userInfo emailAddress as a changed property.

Accordingly, az deployment sub create tries to modify the elastic cluster and fails.

To Reproduce

1. Create elastic monitor with provided emailAddress (--user-info parameter)
2. Prepare Microsoft.Elastic/monitors bicep template with a provided emailAddress from the previous step.
3. Run az deployment sub what-if with the template from the previous step.

Expected behavior
Expected to see a no changes what-if result but receive 1 to modify.

Environment summary
ElasticCloud resource version - Microsoft.Elastic/monitors@2022-09-01-preview

Additional context

[yonzhan]

Thank you for opening this issue, we will look into it.

Thank you for your feedback. This has been routed to the support team for assistance.

[ferrydeboer]

I'm having the same problem and I'm baffled why I can't find more reports on this. It sounds like such a common scenario that makes me wonder if I'm missing some understanding about this particular resource or if barely anyone is actually deploying this through bicep?!

Redeployment of the most minimal bicep like I put below already fails which essentially makes it unusable! I'll go work my way around it now I guess by doing a conditional deployment of a module which can very well give me issues down the line.

To add a little bit more context to this following statement in the original report:

Accordingly, az deployment sub create tries to modify the elastic cluster and fails.

The actual failure I get when running a bicep deployment is:
There is already exiting resource with resourcedId /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Elastic/monitors/{monitorResourceName}

Now I managed to get the what-if to the point of not detecting a diff. Unfortunately even with no diff the above error message still occurs. Which defeats the purpose of a what-if if the actual execution of this trivial bicep is even giving different results.

I needed to do the following to even get to a point of the what-if not detecting a diff:

• not using an email (only works when I'm running te bicep locally under my own account which has a matching user in Elastic Cloud)
• generateApiKey: false because it noted that as a delete. Apparently the absence of the value is different from the default value.

resource elasticCloud 'Microsoft.Elastic/monitors@2023-06-01' = {
  name: 'myelastic'
  location: 'westeurope'
  sku: {
    name: 'ess-consumption-2024_Monthly'
  }
  properties: {
    userInfo: {
    }
    generateApiKey: false
    version: '7.17.21'
  }
}