How to properly use azd up with multiple environments or teams?

[MatteoMgr2008]

Hey folks! 👋

I'm experimenting with azd for setting up some Azure infrastructure in a team context, and I was wondering:

What’s the best way to manage multiple environments (e.g. dev, staging, prod) using azd up, especially when several developers are working on the same project?

I’ve seen references to environment names and configurations, but I’m not entirely sure how to structure things when each team member has their own Azure subscription or resource group.

Should we be using different .azure folders, or is there a cleaner way to handle this?

Any real-world setup tips or gotchas would be super helpful! Thanks a lot 😊

[anshkumar2311]

Hey Matteo 👋 — great question!

When working with azd in a team or across multiple environments (like dev, staging, and prod), here's how to keep things clean and collaborative:

✅ What works best:

1. Create a separate environment for each case

   • Use azd env new dev, azd env new staging, azd env new john-dev, etc.
   • Each environment keeps its own settings, secrets, and infra isolated.

2. Let each developer have their own environment

   • This avoids clashes and gives everyone a safe sandbox.
   • Each azd env can target a different Azure subscription or resource group.

3. Don't worry about the .azure folder

   • azd manages it for each environment automatically.
   • Just avoid committing it to Git (add it to .gitignore).

4. Use azd env set to store secrets or settings per environment

   • Super helpful for things like API keys, DB strings, etc.

💡 Pro tips:

• Use azd env list to see all your environments.
• Use azd env select <env-name> to switch between them.
• Keep your infra code versioned in Git, but not the .azure folder.

In short: one environment per person or stage, switch with azd env select, and let azd handle the rest.