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

`devices.getIotHubResource` returns a result with <https://www.pulumi.com/registry/packages/azure-native/api-docs/devices/getiothubresource/#eventhubendpoints_nodejs|eventHubEndpoints>. However, for putting the endpoint in a vault you might need to use the Azure Key Vault directly, since Pulumi is meant to manage resources, not objects in the data plane.

Thanks <@U038021B1CJ>, but what do you mean _use the Azure Key Vault directly?_ Do you mean manually?  How would you else automate it? I am stringing together a lot of resources that need to communicate with each other and if I quickly want to spin up new stack I wouldn't want there to be any manual work involved?

I meant using the official azure KV SDK in your code, alongside Pulumi.

ah, so this is not recommended? I should use a kv sdk to do so in stead? that would also let me have less resources in pulumi as every secret is now a resource...

```new azure.keyvault.Secret(name, {
  name,
  value,
  keyVaultId: this.resource.id,
});```

Actually, it seems like my response was not quite correct. While Pulumi does indeed not support 100% of the KV data plane, it looks like creating secrets should be fine.

That being said, if you wouldn’t want your secrets as Pulumi resources, you’re always free to use the KV SDK in parallel to Pulumi.