This message was deleted.

can you show a screenshot of the details?

One reason for this is that the resource is being created in an

apply()

or in some other context where the values aren't known to Pulumi. If this is the case for you, maybe you can refactor to move the constructor outside the

apply()

, and instead pass Input parameters to the constructor.

Thanks both, Somehow the state on Azure and Pulumi are not matched. So after run pulumi up with refresh the issue was gone.