Latest / Best of LinkedIn: Digital Transformation & Tech / Best of LinkedIn: Cloud Insights CW 21/ 22

Transcript

Best of LinkedIn: Cloud Insights CW 21/ 22 · Best of LinkedIn: Digital Transformation & Tech

• 0:00
  Speaker 1: This episode is provided by Thomas Olguyer and Frenis based on the most relevant LinkedIn posts about cloud in calendar weeks, twenty one.
• 0:07
  Speaker 1: And twenty two.
• 0:08
  Speaker 1: Frenes has built a sovereign Cloud Market Radar for ICT providers with weekly hot news monthly reports quarterly leadership presentations an AI podcast for field teams.
• 0:18
  Speaker 1: you can find more info in the description.
• 0:20
  Speaker 0: And welcome to The Deep Dive.
• 0:22
  Speaker 0: Really excited to have you with us today as we dig into some pretty massive shifts happening right now.
• 0:26
  Speaker 0: Okay,
• 0:27
  Speaker 1: let's unpack this because the conversations were seeing across the ICT and tech industry on LinkedIn are just.
• 0:34
  Speaker 1: They are intense.
• 0:35
  Speaker 1: We're looking at a fundamentally different landscape.
• 0:37
  Speaker 0: Oh, absolutely the old playbooks are well they basically being thrown out of window right.
• 0:41
  Speaker 1: so our mission today is to cut through The noise and look at three major trends dominating calendar weeks twenty one.
• 0:47
  Speaker 1: in twenty two we were going To Look At New Geopolitical Reality Of Sovereign Cloud How Finoffs Is Evolving From Just You Know Passive Dashboards Into Actual Engineering Workflows.
• 0:57
  Speaker 1: And Finally This Sudden Really Harsh Reality Check Around AI Token Billing.
• 1:02
  Speaker 0: Yeah, that AI token bill is.
• 1:04
  Speaker 0: it's definitely causing some panic in the finance departments right
• 1:07
  Speaker 1: now.
• 1:07
  Speaker 1: Oh for sure.
• 1:08
  Speaker 1: but let's start with sovereignty because cloud architecture is no longer just an IT discussion?
• 1:14
  Speaker 1: Is
• 1:15
  Speaker 0: not at all?
• 1:15
  Speaker 0: I mean setting up a cloud environment today is essentially foreign policy executed through APIs.
• 1:20
  Speaker 0: its geopolitics
• 1:22
  Speaker 1: Right.
• 1:22
  Speaker 1: It makes me think of Imagine you rent this highly secure state-of the art vault in Europe, right?
• 1:29
  Speaker 1: You've got biometric locks zero trust laser grids.
• 1:32
  Speaker 1: The works yeah, you feel totally secured.
• 1:34
  Speaker 0: Yeah impenetrable
• 1:36
  Speaker 1: Exactly.
• 1:37
  Speaker 1: but then you find out the contractor who built the Vault is headquartered in the US and Because of that they are legally obligated by their local government to keep a master key.
• 1:46
  Speaker 1: Wow And under certain laws They could be forced use that key completely bypassing whatever European laws you thought were protecting your IP.
• 1:54
  Speaker 0: That is a perfect analogy.
• 1:56
  Speaker 0: And it's not a hypothetical movie plot either, that is the exact tension keeping enterprise architects awake right now.
• 2:03
  Speaker 0: Roger S and Emily K brought up some fantastic points about this on LinkedIn.
• 2:06
  Speaker 1: Yeah The illusion of geographic boundaries has basically shattered.
• 2:09
  Speaker 1: We used to think you know just build a data center in Frankfurt keep the data in Germany You check the compliance box Right
• 2:16
  Speaker 0: simple data residency.
• 2:18
  Speaker 0: But roger s points out that jurisdiction beats geography every single time.
• 2:23
  Speaker 0: he specifically brought up the U.S.
• 2:25
  Speaker 0: Cloud
• 2:25
  Speaker 1: Act, which is a huge deal.
• 2:27
  Speaker 0: it's massive because The cloud act explicitly says us law enforcement can compel any American company to hand over data they control regardless of where that physical server sits on the planet.
• 2:39
  Speaker 1: so if the parent companies in Seattle The U.S.
• 2:41
  Speaker 1: courts view a server in Frankfurt exactly the same way they view a Server in Virginia?
• 2:46
  Speaker 0: Exactly, and Emily Kaye pointed out how this totally undermines things like the AWS European Sovereign Cloud model.
• 2:53
  Speaker 0: AWS is aggressively pushing that showing off new European hospital-and utility customers.
• 2:58
  Speaker 1: But the service is still one hundred percent owned by Amazon.com Inc.
• 3:02
  Speaker 0: Creating legal separation on paper, like spinning up a European subsidiary doesn't actually grant legal immunity in practice if the ultimate parent company gets a foreign subpoena.
• 3:11
  Speaker 1: That puts Europe at really precarious position.
• 3:13
  Speaker 1: but I mean they can just unplug from US hyperscalars tomorrow.
• 3:17
  Speaker 1: The infrastructure gap is way too big.
• 3:19
  Speaker 0: No of course not.
• 3:20
  Speaker 0: you cant slip and switch.
• 3:22
  Speaker 0: The EU strategy is shifting.
• 3:24
  Speaker 0: Guido Hackenberg shared some really crucial updates on the upcoming Cata rules, that's the Cloud and AI Development Act from the European Commission.
• 3:31
  Speaker 1: Yeah those rules are going to tie sovereign cloud eligibility directly to providers.
• 3:38
  Speaker 1: legal entity in ownership right?
• 3:39
  Speaker 1: Yes
• 3:40
  Speaker 0: they're linking it directly to ownership Which means if Cata enforces these strict entity requirements, we could literally see major US hypersailers pushed out of highly sensitive EU government workloads.
• 3:53
  Speaker 0: We're talking healthcare defense judicial data.
• 3:56
  Speaker 1: So the question changes from where's the physical hard drive to?
• 4:02
  Speaker 1: If a foreign warrant lands on the parent company's desk, are you forced to hand over our data?
• 4:06
  Speaker 0: Exactly.
• 4:06
  Speaker 0: And this is already impacting the market.
• 4:08
  Speaker 0: Evan Kirstel highlighted a massive M&A ripple effect in The Netherlands recently.
• 4:12
  Speaker 0: Oh
• 4:12
  Speaker 1: right!
• 4:12
  Speaker 1: The Kindrel and Solvenity deal.
• 4:14
  Speaker 1: Yeah...the
• 4:15
  Speaker 0: Dutch government blocked Kindrel from acquiring solvenity…and Kindrel is no joke.
• 4:21
  Speaker 0: they have deep IBM Enterprise DNA.
• 4:24
  Speaker 0: But Solventy operates Digid which is digital identity backbone for Dutch citizens.
• 4:29
  Speaker 1: So it's critical national infrastructure,
• 4:31
  Speaker 0: right?
• 4:32
  Speaker 0: And blocking that deal proves that sovereignty today is entirely about jurisdictional ownership.
• 4:38
  Speaker 1: if we connect this to the bigger picture I know That something you always say true sovereignty is really about operational control under extreme pressure.
• 4:45
  Speaker 0: Exactly If We Connect This To The Bigger Picture It'S About Control.
• 4:48
  Speaker 0: Robert Felsen and Anne Leslie had this brilliant exchange about it.
• 4:52
  Speaker 0: fousin says sovereignty doesn't start at the database layer
• 4:58
  Speaker 1: Meaning like identity and telemetry.
• 5:00
  Speaker 0: Yeah, how identity is established?
• 5:02
  Speaker 0: How metadata is handled?
• 5:03
  Speaker 0: because if your core workload Is on a sovereign server but you're telemetery You know the data detailing who is logging in And when it's routed through a global network In a non-sovereign jurisdiction
• 5:15
  Speaker 1: then your whole security posture is compromised
• 5:17
  Speaker 0: Exactly.
• 5:18
  Speaker 0: Telemetry leakage defeats the whole purpose, and Anne Leslie took it a step further.
• 5:23
  Speaker 0: She challenged this obsession we have with redundancy.
• 5:26
  Speaker 0: Multi-region architectures don't protect you if The real threat is A geopolitical disruption of the shared control plane.
• 5:32
  Speaker 1: So It's not just about can We technically migrate our data?
• 5:35
  Speaker 0: No?
• 5:35
  Speaker 0: It's About do You Have the legal And technical authority to execute an exit strategy when things go wrong Without a foreign jurisdiction?
• 5:43
  Speaker 0: locking your admin accounts?
• 5:45
  Speaker 1: Wow Yeah, that really reframes the whole issue.
• 5:48
  Speaker 1: And we are seeing industry react with massive capital deployment.
• 5:52
  Speaker 1: Elke and Andrew posted that telecom an SAP just won a two hundred fifty million euro contract to build dedicated AI cloud for the German government.
• 6:01
  Speaker 0: Yeah clear signal that European states or funding infrastructure where they actually hold the master key... ...and
• 6:06
  Speaker 1: it's not just them!
• 6:07
  Speaker 1: Erindam Choudhury mentioned TCS launching sovereign secure Cloud for Europe.
• 6:11
  Speaker 1: Dr Marian Janek highlighted Google Cloud and Thales signing a memo for an independently operated German region.
• 6:18
  Speaker 0: Right, the hyperscalers are realizing they need localized partners to provide what George Politis called Silicon Trust actual hardware backed verifiable exit paths.
• 6:28
  Speaker 1: but building all this highly localized hardware back infrastructure that burns in incredible amount of capital
• 6:33
  Speaker 0: oh it is staggeringly expensive
• 6:36
  Speaker 1: which transitions us perfectly into our second theme because and looking at the LinkedIn consensus from weeks twenty-one to twenty two, traditional fan offices basically broken.
• 6:48
  Speaker 0: Yeah!
• 6:48
  Speaker 0: The traditional dashboard approach is just.
• 6:50
  Speaker 0: it's dead... It separates financial insight from engineering action.
• 6:54
  Speaker 0: Ankoj Madan made this brilliant argument for a total shift in methodology.
• 6:58
  Speaker 0: Because
• 6:58
  Speaker 1: right now what happens?
• 6:59
  Speaker 1: Finance sees a twenty five percent spike at end of month.
• 7:02
  Speaker 1: Panics and emails engineering to go hunt for abandoned resources.
• 7:06
  Speaker 0: Exactly, it's entirely reactive.
• 7:08
  Speaker 0: Madonna argues that Finoffs needs to shift left.
• 7:11
  Speaker 0: It belongs embedded directly inside internal developer platforms Inside the pull request.
• 7:16
  Speaker 1: So you embed namespace quotas and budget alerts directly into the PR?
• 7:20
  Speaker 0: Yeah If an engineer tries to spin up resources That blow past a budget The PR gets flagged right there.
• 7:27
  Speaker 0: They self-correct before the meter even starts running!
• 7:30
  Speaker 1: That makes so much sense.
• 7:32
  Speaker 1: But even when teams try to actively manage costs, aren't they often using tools that just misunderstand the environment?
• 7:39
  Speaker 1: Rogavendra R brought up a huge blind spot regarding Azure and AWS.
• 7:43
  Speaker 0: Oh, this is such an expensive mistake!
• 7:46
  Speaker 0: Rogavandra pointed out that third-party phenops dashboards frequently treat azure mechanics exactly like aws mechanics which
• 7:52
  Speaker 1: I mean on the surface sounds logical.
• 7:54
  Speaker 1: They're both cloud compute platforms
• 7:56
  Speaker 0: right but under the hood The discount structures are completely different.
• 7:59
  Speaker 0: aws relies heavily on compute commitments Like savings plans But azures biggest lever Is the azure hybrid benefit?
• 8:06
  Speaker 1: Which is software license portability thing?
• 8:08
  Speaker 1: right exact
• 8:08
  Speaker 0: Exactly.
• 8:09
  Speaker 0: It lets you take the on-premise Windows and SQL Server licenses that already own, apply them to cloud.
• 8:14
  Speaker 0: It can drop your pay as you go rate by up to eighty five percent.
• 8:18
  Speaker 1: Wait... Eighty Five Percent?
• 8:20
  Speaker 0: Yes!
• 8:21
  Speaker 0: But if your central dashboard is normalizing everything look like AWS.
• 8:25
  Speaker 0: it ignores portability so your biggest potential discount remains totally buried.
• 8:31
  Speaker 1: That leads me ask are Finops teams actually celebrating wrong savings?
• 8:36
  Speaker 1: Because Mohammed Bruechner mentioned teams cheering a ten percent compute discount while completely ignoring shelfware.
• 8:42
  Speaker 0: Yeah, the double-paying problem!
• 8:44
  Speaker 0: Bruekner calls it technology value management.
• 8:47
  Speaker 0: If your engineers don't configure those Azure Hybrid benefit tags in their infrastructure as code Microsoft just charges you with full on demand rate
• 8:55
  Speaker 1: Which includes this software license fee.
• 8:57
  Speaker 0: Exactly So are renting software by the hour that your procurement team already bought a permanent license for Ouch?
• 9:03
  Speaker 1: That hurts just to think about.
• 9:05
  Speaker 1: And then Nicholas Fundrini brought up another hidden cost, security fine ops.
• 9:08
  Speaker 1: Telemetry and sign costs are apparently scaling faster than the infrastructure
• 9:12
  Speaker 1: itself.".
• 9:13
  Speaker 0: Yeah because with microservices and zero trust every container is constantly talking and authenticating... ...and compliance says you have to log it all.
• 9:21
  Speaker 0: so you pay to ingest it and you pay again to store it!
• 9:24
  Speaker 1: But there was a really tactical fix shared for this right?
• 9:27
  Speaker 1: by Alan Visser.
• 9:29
  Speaker 0: Yes, Allen Visser suggested using XPath filtering right at the source using the Azure Monitor agent.
• 9:35
  Speaker 1: so instead of capturing all the noise and filtering it in the cloud you filter it at the node?
• 9:39
  Speaker 0: Precisely!
• 9:40
  Speaker 0: It's like putting a bouncer at the club door.
• 9:42
  Speaker 0: instead of bussing everyone to the Club just to kick ninety percent of them out You drop the noise before it hits your Siam workspace.
• 9:49
  Speaker 1: That is such a good analogy And it proves that if we can't react to a bill We have shape architecture Like Satya Brata Chowdhury's example with AI fine-tuning.
• 9:59
  Speaker 1: Oh,
• 9:59
  Speaker 0: the GPU request example?
• 10:01
  Speaker 0: Yes!
• 10:01
  Speaker 0: He outlined a scenario where data science team asks for eight H one hundred GPUs For two week fine tuning job.
• 10:08
  Speaker 1: Normally an automated platform just provisions that and tags it for billing.
• 10:11
  Speaker 1: right
• 10:11
  Speaker 0: Right but Satya brought up points out that fennups needs to step in And say hey have you considered A low rank adapter or lower I instead of full parameter fine tuning?
• 10:20
  Speaker 1: What does actually do to cost?
• 10:21
  Speaker 0: Elora freezes the original model weights and only trains a tiny matrix.
• 10:26
  Speaker 0: It can cut compute costs by five times or more before single workload even spins up.
• 10:30
  Speaker 0: Wow,
• 10:31
  Speaker 1: and shaping that spin Before it starts is critical now because that brings us to our final theme.
• 10:36
  Speaker 1: The AI experimentation phase is ending And the token bill has arrived!
• 10:41
  Speaker 1: It
• 10:41
  Speaker 0: really has...the flat rate era just slammed into a wall.
• 10:45
  Speaker 1: Rami Algafaji shared this shocking reality check.
• 10:48
  Speaker 1: Microsoft, who basically has infinite cloud capacity had to cancel their own internal Claude code licenses because the token billing became untenable.
• 10:56
  Speaker 0: Yeah and he also mentioned that report about Uber.
• 10:58
  Speaker 0: Their CTO warned staff they had burned through their entire twenty-twenty six AI budget in just four months.
• 11:04
  Speaker 1: Four months.
• 11:05
  Speaker 1: If Uber and Microsoft are hitting the brakes on usage-based pricing, that is a massive structural issue.
• 11:11
  Speaker 0: It is!
• 11:11
  Speaker 0: Token Pricing forces you to confront the real microeconomic cost of generative AI—and it's not just heavy model training either.
• 11:18
  Speaker 0: Venkat Reddy Chintalapudi warned about embedded AI Cost Cree.
• 11:22
  Speaker 1: Oh right…the thirty dollars per month per user for co-pilot addons
• 11:27
  Speaker 0: Exactly.
• 11:28
  Speaker 0: Enterprises are paying to upgrade thousands of employees, but only a fraction actually use the tools enough to justify the
• 11:35
  Speaker 1: cost.
• 11:35
  Speaker 1: It's like outfitting your entire company with sports cars When ninety percent of them Only need to drive To the grocery store down The street.
• 11:42
  Speaker 1: it just kills Your margins.
• 11:44
  Speaker 0: That is exactly.
• 11:45
  Speaker 0: But what's fascinating here is it not just financial risk, there are operational landmines.
• 11:50
  Speaker 0: Elliott Layton Woodruff warned that Microsoft is auto upgrading existing Azure Open AI resources to their new Foundry platform
• 11:57
  Speaker 1: which sounds like a marketing rebrand but its'nt
• 11:59
  Speaker 0: No!
• 12:00
  Speaker 0: Its fundamental shift in the resource provider.
• 12:03
  Speaker 0: It changes resource IDs and networking configs.
• 12:05
  Speaker 0: so if you use Terraform or Bicep and don't update your code Your pipeline will detect massive drift
• 12:11
  Speaker 1: Meaning your automation scripts might interpret that drift as an error and automatically delete your production AI environment.
• 12:17
  Speaker 0: Yes, it might tear down to recreate the old configuration... That
• 12:21
  Speaker 1: is terrifying!
• 12:23
  Speaker 1: Just the idea of consuming AI isn't enough.
• 12:26
  Speaker 1: you have strictly governed operations?
• 12:28
  Speaker 0: Which echoes exactly what Kevin Davis in Kashyap-Ai were saying.
• 12:32
  Speaker 0: The battle isn't about which model is smartest anymore.
• 12:34
  Speaker 0: It's about operating models
• 12:36
  Speaker 1: because organizations rushed to public cloud AI, got hit with the token bill and are now pivoting hard.
• 12:43
  Speaker 0: Yes a massive pivot towards small language models SLMs on private Cloud.
• 12:48
  Speaker 0: John Yoho cited a Goldman Sachs forecast predicting enterprise token demand will explode twenty four times by twenty thirty.
• 12:56
  Speaker 1: You literally cannot run twenty-four times the volume on a variable public cloud meter.
• 13:00
  Speaker 1: It would bankrupt you!
• 13:01
  Speaker 0: Exactly, that's why we're seeing demand for things like HPEs.
• 13:05
  Speaker 0: new private Cloud AI stack.
• 13:08
  Speaker 0: companies want on premise closed loop systems to escape the hyperstalar meter which
• 13:13
  Speaker 1: perfectly ties back our very first theme digital sovereignty.
• 13:16
  Speaker 1: Getting off the public meter is just another way of maintaining operational control over your own destiny.
• 13:21
  Speaker 0: It all connects, and it brings up a really profound point that Greg Powell shared in our sources.
• 13:26
  Speaker 0: Oh
• 13:26
  Speaker 1: I love this point!
• 13:27
  Speaker 0: Yeah he noted that over the last decade The cloud abstracted away the infrastructure layer.
• 13:32
  Speaker 0: you didn't have to rack servers anymore.
• 13:34
  Speaker 0: And now AI is abstracting away the execution layer... ...it turns right this block of code into build-this app
• 13:42
  Speaker 1: Right.
• 13:43
  Speaker 1: so if Cloud handles the Infer and AI handles the coding execution, what is actually left for the ICT professional over the next decade?
• 13:52
  Speaker 0: That's a big realization.
• 13:54
  Speaker 0: The true differentiator won't be pure technical deployment – it will be mastering geopolitical governance and microeconomics of these systems.
• 14:01
  Speaker 0: So
• 14:02
  Speaker 1: understanding how a US subpoena hits an European database… or configuring an Azure hybrid tag so you don't double pay for licenses.
• 14:09
  Speaker 0: Exactly, Or knowing when to suggest a lore I to an engineer before they rack up massive token bill.
• 14:15
  Speaker 1: Going back that vault analogy it really doesn't matter how thick the walls are.
• 14:19
  Speaker 1: if You do understand legal jurisdiction of master key and you Don't actively control microeconomic cost of electricity keeping alarms on
• 14:27
  Speaker 0: roll Then aren't actually in control of the Vault?
• 14:30
  Speaker 1: Exactly The future belongs people who control operating model and economics
• 14:34
  Speaker 0: Spot on, that's the real takeaway
• 14:57
  Speaker 1: here.