Study guide
Azure AI and Machine Learning Services
Microsoft Azure Fundamentals AZ-900
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips
2 Domain 1: Cloud Concepts (25-30%)
1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model
3 Domain 2A: Azure Architecture Components
2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview
4 Domain 2B: Azure Compute Services
2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop
5 Domain 2C: Azure Networking Services
2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery
6 Domain 2D: Azure Storage Services
2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics
7 Domain 2E: Azure Identity, Access, and Security
2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services
8 Domain 3A: Azure Cost Management
3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization
9 Domain 3B: Azure Governance and Compliance
3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together
10 Domain 3C: Azure Monitoring and Management Tools
3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health
11 Additional Azure Services and Exam Review
Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice
12 Advanced Azure Topics and Service Deep Dives
Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans
Azure AI and Machine Learning Services
Key Takeaways Explain This Topic AI
The July 20, 2026 AZ-900 skills outline does not assign Azure AI, Copilot, or Responsible AI a separate domain weight; study this section as optional context.
Azure AI Language and similar services provide prebuilt APIs; Azure Machine Learning supports custom-model training and operations.
Microsoft Foundry is the current name for the platform previously called Azure AI Foundry; model names and regional availability change.
Azure OpenAI data location depends on deployment type and feature; do not assume every prompt or output remains in one tenant or region.
Older Custom Vision and Bot Framework SDK recommendations require lifecycle review before adoption.
Last updated: September 2026
Scope note: The Microsoft AZ-900 skills outline dated July 20, 2026 does not list Azure AI, Copilot, or Responsible AI as a separate exam objective. This section is optional Azure context. Finish the three published AZ-900 domains first; do not infer an AI-heavy exam refresh from this page.
Prebuilt services versus custom models
Azure offers AI services for different levels of control. A prebuilt API can classify sentiment or transcribe speech without training a model. Azure Machine Learning supports teams that prepare data, train, evaluate, deploy, and monitor their own models. Microsoft Foundry is a broader platform for building and operating generative-AI applications and agents. These are useful conceptual distinctions, but the published AZ-900 outline does not assign them a weight or guarantee questions about them.
A product name alone rarely identifies the right design. Ask what input the app has, whether the team needs to train a model, what data-governance constraints apply, and who will operate the result. An API can be the simpler choice for an established task; a custom model may be necessary when the prediction depends on an organization's own labeled history. This is a general architecture judgment, not an AZ-900 scoring shortcut.
Examples of ready-made Azure AI capabilities
Need Current capability to investigate Design question
Extract text and structure from documents Azure AI Document Intelligence What document types, accuracy, and review workflow are required?
Transcribe or synthesize speech Azure AI Speech Which language, latency, and privacy controls are needed?
Detect sentiment and key phrases Azure AI Language Is a prebuilt text-analysis API sufficient?
Translate text Azure AI Translator Which languages and quality checks are required?
Analyze images Azure AI Vision What image-analysis features and regional availability apply?
These services have different prices, limits, model versions, and region support. A “prebuilt” service still requires application integration, testing, privacy review, and monitoring. It does not guarantee accurate or appropriate results for every population or business process.
Older tutorials may recommend Custom Vision , Anomaly Detector , Content Moderator , or the Bot Framework SDK as default starting points. Product lifecycle changes make that unsafe. Custom Vision is on a retirement path, and the Bot Framework SDK is archived. Check Microsoft's current migration and product-status documentation before selecting any older service. Do not memorize a retired product list as if it were an AZ-900 objective.
Azure Machine Learning
Azure Machine Learning supports the lifecycle of a custom predictive model: prepare data, select an experiment, train and evaluate, register a model, deploy an endpoint, and monitor performance. Automated ML can search candidate algorithms; notebooks and pipelines support more controlled workflows. A custom model also brings responsibilities that an API does not remove: representative training data, security, versioning, drift monitoring, and retraining.
Example: A retailer wants to forecast demand from its own sales, inventory, calendar, and promotion history. Azure Machine Learning can support that data-specific training workflow. A prebuilt sentiment API would not solve the forecasting problem. Conversely, if a team merely needs sentiment from customer reviews, Azure AI Language can be a practical prebuilt starting point.
Generative AI and Microsoft Foundry
Azure OpenAI provides access to supported generative models through Azure. Microsoft Foundry is the current name for the platform previously called Azure AI Foundry; it helps teams select models, build applications or agents, evaluate responses, and operate the system. Model availability and names change, so an exam guide should not depend on a fixed GPT or image-model version. A chatbot is an application pattern that may combine a model, orchestration, retrieval, identity, and a delivery channel; a model endpoint alone is not a complete, governed application.
Enterprise controls may include Microsoft Entra authentication, role-based access, private networking, monitoring, and content safety. They must be configured and tested. Do not assume all prompts and outputs stay inside one tenant or Azure region. Processing location depends on the selected deployment type (regional, data-zone, or global), model, feature, and current service terms. A regulated workload needs a specific deployment and data-flow review, not a general promise based on the product name.
Responsible operation
Responsible AI is a governance practice rather than a single deployable product. Teams should consider fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability. Human review may be needed where errors affect people or legal rights. Evaluation must test realistic inputs, edge cases, and misuse, then continue after release as data and models change. These principles are valuable context but are not a newly added AZ-900 domain.
How to use this section while preparing
If you are studying strictly for AZ-900, prioritize cloud concepts, Azure architecture and services, and management and governance. Know the published objectives and the purpose of the services actually listed there. Return to this section as optional context if your work involves AI, or when planning a later AI-focused credential. When you do, verify current Microsoft documentation: names, model versions, regional availability, and retirement dates change faster than core cloud concepts.
Study boundary: Prebuilt text analysis, custom model training, and generative-app platforms solve different problems. This is a useful Azure distinction, but no published July 2026 AZ-900 weight or AI expansion supports treating it as a tested fourth domain.