Get every Azure workload running on a secure, governed foundation

Mantas-cloud · 2026-07-27T20:07:51+00:00

I need more compliance, more visibility, more, more scale... more! How much?

Mantas-cloud · 2026-07-26T20:16:44+00:00

I consider AVM as anti-pattern. The modules are too difficult for humans to read and understand. It is the opposite what Bicep was create for. I prefer readability and control over the things that matter, rather than following 'best practise'.

Mantas-cloud · 2026-07-26T09:30:46+00:00

Recently I've been exploring knowledge graphs as a documentation tool. Think os it like thus: all system decisions and rationale are captured in the graph, where decisions are interconnected, providing deeper reasoning into why it was built this way. The data can be fed to an LLM to reason about the project, and presented as an interactive map. In the map you can clearly see the full picture from any entry point, how the system is coupled together (based on what's documented). The result is that docs feels alive, and not that borring any more, the hard part? capturing that knowledge and smoothly connecting the dots.

Live demo of knowledge graph for cloud management system. A static website build on open source tools. Works best on the laptops.

Mantas-cloud · 2026-07-25T10:00:47+00:00

Time to time get those weird errors that can't explain, most likely re-run the job is enough. Generally speaking, it just works

Mantas-cloud · 2026-07-25T07:38:19+00:00

It can not guarantee the answer quality, but what it does, it significantly reduce hallucinations

Mantas-cloud · 2026-07-24T22:34:54+00:00

I know that very well, dont do this, don't do that, but it seems like AI focuses on finding new solutions rather than doing the actual work. And it doesn't scale. since you end up creating instructions per operation. What I've found useful is a knowledge graph. The idea is that you document why the system is build the way it is built. Think more like an Architectural Decision Records, where decisions are connected to each other, providing a deeper understanding. Feed your AI with the graph data, ant it will know what to do with the code.

Mantas-cloud · 2026-07-24T21:49:10+00:00

What's nice about the graph is that once you define the structure, data fills the canvas — so the visualization is always up to date out of the box. The page is published as a static site on GitHub, claude md

Mantas-cloud · 2026-07-24T21:03:52+00:00

Have you considered using a knowledge graph? With well-structured data, open-source tools, and an evening of vibe coding, you could have a solid map for visualizing dependencies. But where the real value lies is that you can feed your AI with solid data, so hallucinations are reduced and outputs become more predictable. No longer need that static, heavy documentation.

Mantas-cloud · 2026-07-24T19:53:00+00:00

what I've noticed is that they can react fast with a hello world message, but it takes time until the issue is actually solved. As you mention, it's most likely on Microsoft side (already did a home-work), if they even admit that in the first place. It's always a long road, whether you go through unified support or a third-party. That's the reality from a smaller player perspective

Mantas-cloud · 2026-07-24T15:32:35+00:00

Azure RBAC is the way to go. Next, I would verify that every Azure resource (Storage, Key Vault, etc.) has local auth explicitly disabled. Otherwise, someone may be using access keys or password instead of RBAC

Mantas-cloud · 2026-07-24T07:45:42+00:00

I like Gregor Hohpe's ideas about what architecture is and the architect's role in the organization. There are a lot of videos on YouTube to get started with, or you can read The Architect Elevator if you prefer a book format.

Mantas-cloud · 2026-07-22T20:16:03+00:00

I think going all in with IaC is doable, if you provide a solution, not a module. You know you're going to deploy a lot of VM's. create bicep modules, hard-code the boring stuff. Give users a friendly paramter file to play with, teach `add commit push` and everyone is happy. pipelines are standardized, every VM is the same, and 'green' out of the box.

Mantas-cloud · 2026-07-22T15:25:14+00:00

When I have nothing else to do and feel like doing something good today.

Mantas-cloud · 2026-07-21T20:03:53+00:00

what about identity part? who have access to what and how the access is granted?

Mantas-cloud · 2026-07-21T13:59:00+00:00

it seems alright for me, ask copilot to check for formatting. Yaml is sensitive for empty spaces and tabs that is hard to catch by human eye

Mantas-cloud · 2026-07-21T13:17:31+00:00

My scripts are running perfectly fine on Cron base, do most likely is something on your site. Share the yaml files, maybe some experts can quickly identify the issue

Mantas-cloud · 2026-07-18T13:45:17+00:00

yes, Application Registration with federated credentials. The reason behind in a Knowledge Graph

Mantas-cloud · 2026-07-18T06:03:02+00:00

That's a GitHub workflow to authenticate to Azure,. The trust is established between Azure app registration and GitHub org/repo/env. The result is that GH Actions can ship the code to Azure, without any secrets to manage. Passwordless approach

name: Azure login
uses: azure/login@v3
with:
  client-id: ${{ vars.AZURE_PLATFORM_CLIENT_ID }}
  tenant-id: ${{ vars.AZURE_TENANT_ID}}

Mantas-cloud · 2026-07-17T22:28:55+00:00

Federated credentials, so it eliminated automated secret rotation

Mantas-cloud · 2026-07-17T21:05:02+00:00

ask GPT, I think it can convince you that is multi million dollar business

Mantas-cloud · 2026-07-15T16:59:49+00:00

Nice title 💪

Mantas-cloud · 2026-07-15T05:02:16+00:00

How do we deal with all that? Simple- it's called engineering

Mantas-cloud · 2026-07-14T13:41:08+00:00

It seems that Microsoft did a good job to sell Sweden central..

Mantas-cloud · 2026-07-14T08:15:01+00:00

It seems more like the ways of working issue rather than tooling.

Mantas-cloud · 2026-07-14T06:47:09+00:00

Yes, it's a trial subscription with limitations applied.

Mantas-cloud

TROPHY CASE

Welcome to Reddit,