💡Tip: Why not use dotnet user-secrets for local dev team?

by Dec 1, 2023Shorts

💡Tip: Why not use dotnet user-secrets for local dev team?

The question arises often, but it’s not team-friendly in an active codebase.

Why?

  • When secrets are added or altered, everyone must be informed of new keys/values.

  • Onboarding means transferring user secrets machine to machine.

The solution? Azure Key Vault for local development.

  • It informs the entire team when a secret is added/changed.

  • Onboarding is simply adding the new member to the Azure Active Directory Group with Azure Key Vault access.

Problem solved!

Remy van Duijkeren

Remy van Duijkeren

The Marketing Developer

I build automation and integrations that remove the annoying stuff—using Power Platform, Dynamics 365 & Azure.

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related

Hourly billing is nuts.

Hourly billing is nuts. Because the slower someone works, the more you pay. And the faster someone is… the more they get punished. Great system,...

read more