Chapter 2. Planning and Managing AI Solutions in Microsoft Azure
Building AI solutions in Azure often feels like constructing a skyscraper; you can’t just focus on laying bricks (or writing code). Many an organization learns this the hard way when a perfectly accurate customer sentiment model is rejected because the engineer overlooked compliance checks for European user data. The truth is that successful AI engineering requires orchestrating stakeholders, security protocols, and cost controls as much as it demands technical skill.
Take a retail inventory forecasting tool: while developers obsess over long short-term memory (LSTM) models, warehouse managers care about latency, finance teams demand cost alerts via Microsoft Cost Management, and security leads insist on RBAC roles like “Cognitive Services Data Viewer” to lock down supply chain data. The AI-102 exam tests this kind of big-picture thinking by requiring you to know when to use Azure OpenAI’s GPT-4 for creative copywriting and when to use Azure AI services’ prebuilt Text Analytics for straightforward sentiment checks—all while avoiding the “$10,000/month cloud bill” horror stories.
Security isn’t an afterthought—it’s the foundation. Imagine deploying a medical imaging model that accidentally exposes patient IDs due to a misconfigured Azure Kubernetes Service (AKS) cluster. I’ve seen teams waste months retrofitting security when they could’ve baked it in up front by using Azure Policy to automatically block noncompliant ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access