CODEWITHSUNDEEP
azure
Volker
Volker

Reputation: 1817

Starting with azure development as a company

We are a small company and are still unsure how to start all this azure stuff.

Ok, we are clear on the technicalities like table storage and queues and all the that stuff, what we don't know about at all is how to set up the organization around developing for our developers. Which/how many azure accounts, shared or individual ones.

So far we've done classic windows development, so everyone has his environment, unit tests run either locally or on the build server (after pushing to mercurial or git), deployment from the build server.

The thing is that we want to use Azure not just as a hoster, but the full set, like blob/document/table storage, event hubs, storage queues, ReliableActors and everything. Things we can't do locally.

What's the appropriate way for azure then? There are about 20 to 30 developers and most have the enterprise msdn subscription.

What is a "company or organisation" account for? Should developers have their own accounts? Does DevOps need their passwords for all the bamboo or jenkins build stuff?

Upvotes: 3

Views: 397

Answers (1)

Francois
Francois

Reputation: 893

I went through this recently and I can share a few tips here since I'm also not aware of a DevOps specific platform to share this on StackExhange.

As far as organizing your subscriptions go look at Azure Pay-As-You-Go Dev/Test Subscriptions link or Enterprise Dev/Test link if you are an Enterprise Agreement customer. These are aimed at development teams, you get discounted rates since you don't pay for software licenses that are already included in your MSDN subscription.

It is best to use individual developer subscriptions for exploration, POC etc while running your main dev workload in the Dev-Test subscription. It looks tempting to try and save a buck by spreading the work across multiple MSDN subscriptions to use the credits but I wouldn't recommend it. It becomes a pain to manage 20~30 subscriptions and they can run out of credits and things stop working. If you remove the spending limit on all the subscriptions you run the risk of racking up a huge bill accidently if multiple devs leave VMs on or add premium storage to VMs etc.

As far as DevOps go, use RBAC and Azure Active Directory to manage access and certificates for your DevOps tooling, build servers, release management etc don't use individual developer credentials for this.

And I agree with the other comments, get in touch with MS as well, this is just the tip of the iceberg but it will get you started.

Upvotes: 1

Related Questions