What are some of your best practices to help stop shadow IT before it starts in Azure?

I recently started a new Azure engineering role. They don't really have any governance, processes, etc. in place, and I have a relatively free hand to propose and implement stuff.

The place I'm at has a reputation of shadow IT - businesses will hire their own devs, build their stuff out, then hand it over to us. Their logic is that it's easier to do that and get what they need rather than have to work with IT to do it right.

Azure is still fresh and new, and I want to start things out so the business doesn't see us as an impediment. Are there any best practices or guidelines you follow or push in your Azure (or overall cloud) environments to head off shadow IT at the pass? e.g. intake of new projects, laying out SLAs, etc.?

submitted by /u/MohnJaddenPowers
[link] [comments]

Read more here: https://www.reddit.com/r/AZURE/comments/ooxh18/what_are_some_of_your_best_practices_to_help_stop/

Content Attribution

This content was originally published by /u/MohnJaddenPowers at Microsoft Azure, and is syndicated here via their RSS feed. You can read the original post over there.

%d bloggers like this: