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

<#CRVK66N5U|azure> question, is it bad practice to use the normal azure provider and the azure native provider in combination when writing azure pulumi code?

Okay cool, thank you for the confirmation.  It does seem like you want to define as many sub resources inside a major resource as possible to help avoid churn.   That seems to have been our major issue.

In our case we were attempting to add active directory admins to a sql server in a separate statement after the sql server declaration.  The sql server declaration was native and the active directory was not.  Combining them into one statement seems to avoid unnecessary delete/replaces.