Hello, I have this recent issue with web app auth settings v2 provider (azure-native.web.WebAppAuthSettingsV2). The provider has suddenly started having issues with deletes. Trying to delete this resource in a up, results in an error: error: Status=400 Message="{"Code":"BadRequest","Message":"The parameter properties has an invalid value.","Target":null,"Details":[{"Message":"The parameter properties has an invalid value."},{"Code":"BadRequest"},{"ErrorEntity":{"ExtendedCode":"51008","MessageTemplate":"The parameter {0} has an invalid value.","Parameters":["properties"],"Code":"BadRequest","Message":"The parameter properties has an invalid value."}}],"Innererror":null}" Mind that constructing the resource works fine. The current hypothesis from ChatGpt, is that the provider deletes the resource by sending a PUT request to the azure rest api with a mostly empty payload. There must then have been some change to how the azure rest api handles the inputs, so that this empty payload becomes invalid and hence fails the delete. Has anyone encountered something similar? or know of a fix?

You're probably right, Pulumi cannot delete some resources in Azure so instead it does a PUT to set it back to the "default" state. I believe the resource you're referring to maps to this entry - https://github.com/pulumi/pulumi-azure-native/blob/12031f9be156f3b399b20a2302c8a7b8cc4f8026/provider/pkg/openapi/defaults/defaultResourcesState.go#L159 Either the API version has changed in Azure native and is no longer compatible with that shape of the default state, or Azure have modified what the default state should be. The easiest way to check is to deploy a web app without the Auth settings and observe the json structure of the Auth settings resource to see if it matches what Pulumi is trying to set it to or not.

FYI, you can generate a local SDK for any version of the Azure API: https://www.pulumi.com/registry/packages/azure-native/version-guide/#accessing-any-api-version-via-local-packages