Redeployment Noise - How to fix

[martyh888]

When I re-run the deployments on many items I am getting a lot of noise on things that haven't changed. Either it reports these items needed deleting (location seems to be a big issue on this) or it wants to create the same values again (I am working on the App Services Type) Below is some examples of the issues I am facing with this noise

The following is already set and declared in the bicep but is ignored on every deployment and showing as needs to be added again

~ Microsoft.Web/sites/siteName [2020-12-01]
    + properties.siteConfig.http20Enabled:       false
    + properties.siteConfig.localMySqlEnabled:   false
    + properties.siteConfig.netFrameworkVersion: "v4.0"

The following is saying we need to delete the location but if I try to add a location to the virtual networks Site type it is not allowed so again I get a modified resource

 ~ Microsoft.Web/sites/SiteName/networkConfig/virtualNetwork [2020-12-01]
    - location: "eastus"

Ideally, I would like to be able to see these as ignored so that when I do redeploy it will show as no changes if there are no values different from the current deployed values in the what if.

Can you provide feedback on options to overcome this (temporary bypass) or where this is in the development phase as for an auditing point this would be a great tool to be able to make sure the infrastructure code matches the current deployments and seems this is the main reason I am wanting to use bicep so that my deployments are consistent and version managed

[slavizh]

Report issues here: https://github.com/Azure/arm-template-whatif/issues
What-If is separate feature from Bicep for which noise is tracked separately. If I remember correctly CLI/PS contains link to the What-If repo when you use the feature during deployment.

[brwilkinson]

@martyh888 feel free to link your noise issue back here if you like. If you are happy you reported it over there you can mark @slavizh answer as 'answered'.