"Gesundheitswesen überlastet, #Microsoft will mit #Cloud und KI helfen"
"Microsoft wirbt stark für den Einsatz seiner Dienste im Gesundheitswesen. Die Cloud-Infrastruktur #Azure sei dabei sehr sicher, verspricht das Unternehmen."
Es kann sich dabei wohl nur um einen Scherz handeln, oder? Nachdem die Kronjuwelen von Azure seit mehreren Jahre nachweislich infiltriert sind und kürzlich Millionen öffentliche interne Dateien aufgetaucht sind ... 🤦♂️
Day 211. #Azure App Service per default exposes an IIS management port for Web Apps. You don't want your Web App to come with this open port? Easy, simply redeploy it until you land on an underlying server where that port has been deactivated.
🔐 Vendor lock-in hurts UK govt ability to negotiate spending | The Register
「 "UK government's current approach to cloud adoption and management across its departments faces several challenges" which combined result "in risk concentration and vendor lock-in that inhibit UK government's negotiating power over the cloud vendors." 」
Helping a colleague troubleshoot an #azure oddity - trying to get the details of a Key Vault using the #azurecli with az keyvault show --name X but it errors out saying that an unrelated resource group could not be found. (Apparently the resource group did exist at one point, but has been deleted)
az keyvault list is empty, as is list-deleted, but the vault definitely exists.
After Chinese(?) hackers infiltrated #Azure & most probably all connected systems for years without being noticed, the Russians do seem to have stolen important source code.
Takeaways: #Microsoft isn't able to protect their most important assets. They don't even notice hackers in their systems for a long period of time. When your threat model relies on secret source code, you're not coding good #software.
Question to all #software engineers (of all genders, of course):
#Microsoft offers a wide range of corporate tools, that (in parts) interact with each other, making it very comfortable for companies (of any size) to use them and thus getting "vendor locked-in".
E.g.:
Outlook connects to teams,
Edge (plans) to recommend (and connect) to teams and vice versa; logging in with MS SSO, over VPN, and so on, very strongly interconnect their different tools.
Would all that be possible - already today - using only #OpenSource tools?
With the same level of comfort and "interconnectedness" in comparably "high polished" user interfaces?
I ask, as someone some time ago stated that Microsoft would be "exceptionally good" in doing so for corporates.
@fasnix I don't think it would be possible with the 'same level of DIScomfort'... but yes with a MUCH BETTER lever of comfort. 😉
I explain. IMHO #Microsoft is a pain even with interoperability in between different versions of their own suite. By using #OpenSource applications such as #LibreOffice, #NextCloud, #OpenProject, #Thunderbird, etc., you'll be able to interoperate with others using a far more diverse landscape of systems and applications, including Linux, Apple and old versions of Microsoft applications that they don't support themselves any more, but you'll come across all the time.
I moved away from Microsoft and used exclusively OpenSource software for almost 20 years with zero regrets.
I do this both at personal and corporate level.
The only 'downside' is that you will learn new things... 😎
To be fair, there are some niche areas where proprietary software might be the only cross-platform suitable solutions, and then you need to add those to your suite, but that has not been my experience with any of the Microsoft products at all.
Just as an indicator, on #Azure, Microsoft's own cloud computing service, 60% of the cores are running #Linux.
Now, if you are one of those people who are scared of computers, or think that software is some kind of black magic or voodoo... ok, don't try... but in any other scenario with a bit of natural curiosity, you'll be fine. 😊
But I'm thinking more about terraform or kubeconfigs where I can reference a role arn and the tooling switches automatically as long as I'm signed into my default profile.
Year 2024. #LeapDay still causes issues to #Azure.
Noticed that #paloalto data sent to #Sentinel via #AMA during 29th was logged with TimeReceived as 1st of March. Issue doesn’t happen if you use old #MMA / #OMS agent.
I just can't with #Azure. I'm not allowed to upgrade the node pool from 1.26 to 1.27 because Kube version 1.27 is no longer supported. But the system is otherwise cool with me creating an even older node pool.
I know that Microsoft had a rather controversial reputation but in general they did a good job with #Azure.
But sometimes it can be so tedious. I was lazy and wanted to click deploy an Application Gateway for testing purposes, which failed 3 times because of some error that wasn't really explained.
In the end I wrote and deployed everything with #Terraform and it just worked.
Not to self: do it properly right from the start.
Hello 👋 We'll be sharing updates from the #PostgreSQL team 🐘 at Microsoft here, including our open source contributions to the Postgres database core—plus our work on the Azure Database for PostgreSQL managed service. And more!
✅ If you missed this 📝 blog post on what's new with Postgres at Microsoft by @clairegiordano, it's still quite current & gives a good overview