People going around installing random binaries on servers makes for support nightmares. Not to mention licensing/contractual/audit issues.
If it goes through “the bureaucracy”, as you term it, then it should be properly documented so that when issues arise, people know what’s on the server vs. what’s supposed to be there. If some auditor comes in and says “show me what’s installed, and show me what controls you have to ensure that the list is accurate” then having a bureaucracy and enterprise deployment platform makes sense. Even if it makes your job that little bit harder. Health care and finance are definitely industries in that bucket. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Tuesday, 31 January 2017 3:53 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: Used Azure SQL DB? Why or why not? Another argument we got from the DBAs was "we are responsible for the integrity of the data so we're not relying on some thing in the cloud we know nothing about." A major Melbourne hospital network said that to us recently. They demanded that the ASP.NET<http://ASP.NET> app be installed by their IT staff on their server. So instead of having it deployed live in 10 minutes it took 10 days to give them an MSI with instructions and get it through their bureaucracy (we think 10 days was pretty good!). Several months ago I tried to counter this argument by eventually finding an Azure page that listed the international security certifications. Among them was "Australian health data", but I don't think many hospitals would care. Does anyone know of significant Australian government, education or health services that are using Azure (or AWS or whatever) for managing big data? GK
