Skip to main content

From cloud-first to AI-Native - the certification Shift

By

 For a long time, the focus was clear: infrastructure, development, data, security and DevOps. AI was there, but more as an extra topic. Now this is changing. AI is becoming part of normal delivery, and as a result, the certifications that matter are also changing. This is not only about learning a new technology. It is about showing that our teams can design, build and deliver AI-native solutions in a real project environment.

The most relevant AI certifications now are:
AWS
  • AWS Certified AI Practitioner
  • AWS Certified Machine Learning Engineer – Associate
  • AWS Certified Generative AI Developer – Professional
Microsoft Azure
  • Microsoft Certified: Agentic AI Business Solutions Architect
  • Microsoft Certified: Azure AI Engineer Associate
  • Microsoft Certified: Azure AI Fundamentals
GitHub
  • GitHub Copilot Certification
AWS is making this shift in a practical way. An AI Practitioner helps create broad AI literacy. A Machine Learning Engineer – Associate brings more engineering depth. Generative AI Developer – Professional is especially relevant because it is consistent with what customers are asking for now: real GenAI solutions, not just experiments.
Microsoft is also showing a clear direction. One important signal is that the Azure AI Engineer Associate is being retired. This is relevant because it shows that Microsoft is moving away from the old single-path AI engineering model and more toward agentic AI, business solutions, and practical AI application skills. In simple words, the market is moving from “knowing AI” to “using AI in delivery.”
GitHub Copilot is also part of this shift. I see it less like a simple certification and more like a sign of how software engineering is changing. AI is now helping teams write code faster, explore options quicker, and improve productivity in day-to-day work. For this reason, GitHub Copilot is becoming relevant not only for developers as well as for DevOps and technical leads.
If I look at certification paths by role, I would think about them like this:
  • Development: AI Practitioner : Generative AI Developer – Professional
  • DevOps: AI Practitioner : Machine Learning Engineer – Associate : GitHub Copilot
  • Infrastructure: AI Fundamentals : core cloud infrastructure certifications
    Architecture: Generative AI Developer – Professional : Agentic AI Business Solutions Architect
For me, the big message is simple: this is the year when certifications start moving from cloud-first to AI-native. The teams which adapt faster will be in a better position, both for presales and for delivery.

Comments

Post a Comment

Popular posts from this blog

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

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

Azure Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more