Creating Azure Deployment Environments via the Azure Portal!

[@BrantScalan]

Will great content. Really enjoying it. I was wondering if you had any advice or maybe even a video/series on using ACA for multiple developers working on the same project where each dev can spawn their own dev environment locally, but when they push to say a dev branch with GHActions will spawn a dev environment and lastly a merge to Main pushes code live. Conceptually I get it but not grasping the best way to implement such a flow and environment for multiple devs. Thank you in advance

[@pkparsard]

Will, this is an awesome demo. Thanks for making it more intuitive and easy to follow. Question: When we specify the Contributor and UAA roles for the devcenter system assigned managed identity, do we do this at the subscription scope in which the dev center is hosted, or should it be for all the subscriptions in the tenant where we expect developers to provision environments as well ?

[@TestUser-b9v]

There's a billion guides on starting a new environment. This is the only one I've found which even remotely addresses the case I need. I've been asked to write an application for an existing azure cloud service, and to do that, I need to set up a development environment using non-production data. They don't make it easy. I have no way to create resource groups, or deployment environments and I don't have admin access. The best I can do is look at environmental variables to hack into the database and file-by-file copy the code used in the function app, and just guess at setting everything up somewhere else. This is a nightmare. All the azure help articles go in circles and only address admins starting new cloud projects. Surely there must be a way for a contributor to.. contribute? There don't appear to be any resource groups or deployment environments on this project, so I'm at a loss as to how it came to exist in the first place.