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

Have you tried adding this paramer to the pulumi.ResourceOptions <https://www.pulumi.com/docs/concepts/options/ignorechanges/|ignore_changes> parameter?

:point_up: that. Also it's not a bug. Pulumi is correctly reporting the diff in your state with what is in Azure. Since `earliestRestoreState` isn't a property you'd ever provide as an input (and probably can't anyway) it's within expectations that you'd want to use the `ignoreChanges` option

Thanks for pointing that out, <@U03TDBDDBCH> <@UDE2DCFT3>. That makes total sense and seems to be the option that we were looking for! :pray:
We'll try the `ignoreChanges`  approach.

Update: `ignoreChanges`  only applies to inputs. Since `earliestRestoreDate` is an output, it is useless here.