Skip to main content

Phase 5 of Intelligent Cloud Modernisation: Build-run-evolve of AI-Native solutions

By

 By Phase 5, most organisations have working systems. Applications are refactored, data modernised, AI integrated, and governance established. It is tempting to think the journey is over.

AI-Native platforms are not classic IT. You don’t deploy and forget. Models drift, prompts evolve, embeddings go stale, costs shift, and user expectations change quickly. This is why Phase 5 is a continual Build–Run–Evolve cycle.


In the image I use for this phase, the cycle is simple: Build → Run → Evolve. Behind this simplicity lies a serious message: AI requires automation and operational discipline on par with engineering.

Build: Focus on making delivery repeatable, not dependent on individual effort.

In AI projects, ‘heroic delivery’ is common: one team member deploys the model, another fixes the pipeline, and a few keep the platform alive. This does not scale.
Build means we standardise how we build and release everything: infrastructure, applications, data pipelines, prompts, models, policies. The keyword here is reproducibility.
In Azure, the tooling is familiar: Infrastructure as Code with Bicep or Terraform, CI/CD with GitHub Actions or Azure DevOps, and packaging with container registries. For AI workloads specifically, Azure Machine Learning gives model registries, versioning, endpoints, and pipelines, so the AI part follows the same release discipline as software.
At the build stage, you treat prompts and evaluations like code. As with code changes, prompt updates can break production, so ensure you test, approve, and create rollback plans for changes.

Run: Manage AI as a platform, not as a one-time experiment

Running AI workloads differs from traditional apps. Monitoring CPU and uptime is not enough. You must track intelligence: response latency by prompt, retrieval latency, token usage, fallback rates, hallucination incidents, and quality drift.
Run is where observability becomes a platform layer. Teams need dashboards and alerts linking app health to AI health. In Azure, this includes Azure Monitor, Application Insights, and Log Analytics. For security, it connects with Defender for Cloud and Sentinel as needed.
Run also includes cost visibility. Key takeaway: Integrate FinOps practices like tracking AI unit costs, cost per interaction, and budget guardrails into daily operations to maintain control over spending.

Evolve: Keep improving based on feedback, changes in data, and business needs

Evolve is the part that many organisations underestimate. AI solutions change because the world changes. Data changes, customer behaviour changes, regulations change, and models change. If you don’t evolve, the quality drops, and people stop trusting the system.
Evolution means setting feedback loops and improvement cycles. Capture user feedback, measure quality, detect drift, and then adjust: retrain, re-embed, retune, update prompts, tighten governance, or change model routing for cost and performance.
In Azure, evolution brings MLOps and AIOps together: model lifecycle automation via Azure ML, plus operational learning from monitoring and incident patterns. The goal is not to avoid, but to make change safe and continuous.

Final thought

Build-Run-Evolve turns an AI initiative into a capability. Without this phase, AI stays fragile: it works today, breaks tomorrow, and causes confusion. With it, AI becomes robust: each release is smarter, faster, and more reliable.

Comments

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

[Post Event] Azure AI Connect, March 2025

By
On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.
Post a Comment
Read more