No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This sounds like a bug in the upstream Terraform resource provider - would be worth making sure there is an issue tracking it. 

I don’t have any great workarounds to suggest - other than making sure the two updates are deployed separately which is definitely not ideal. 

There are more complicated things you could try - like using a get method to look up the existing resource and then conditionally setting the new value for the conflicting property on whether the existing and new value of the other property match. That may well be more complicated than it’s worth though. 

What is the resource in question?

It’s an Azure managed KubernetesCluster (AKS)