Azure Cognitive Services hands you pre-trained AI capabilities as API calls: computer vision, speech recognition, language understanding, translation, anomaly detection. The real question is when to reach for these off-the-shelf tools versus training a custom model. It's one of those architecture decisions that looks simple until you're three months into a project and realizing you picked wrong.
The build vs. buy decision
Training your own ML model means: labelled training data, ML engineering expertise, training infrastructure, and ongoing monitoring. You get a model tuned to your specific domain. Cognitive Services gives you a model Microsoft trained on broad datasets. It handles common cases without any of that investment. Here's the rule I use: if your common case is 80+ percent of what you need, Cognitive Services gets you there faster. If you're in a specialized domain or those edge cases matter most, custom training usually wins.
Form Recognizer for document processing
Form Recognizer (now Document Intelligence) extracts structured data from forms, invoices, receipts, and ID documents. The pre-trained models handle common document types without custom training. For your custom documents, you can train a model with just 5 examples. The win here is obvious: swap out that brittle OCR pipeline that needs field-by-field configuration for something that actually understands document structure.
The Language Understanding layer
Azure Language Service does: named entity recognition, sentiment analysis, key phrase extraction, conversational language understanding. If you need to classify user intent (support ticket routing, FAQ matching), the custom CLU models train on 50 utterances per intent. Microsoft manages the infrastructure. Your model becomes an API endpoint. The real work is just defining your intents and labeling examples.
Content moderation in production
The Content Moderator API handles text and image moderation: explicit content, profanity, personally identifiable information. For any platform with user-generated content, automated moderation is your first pass before human review kicks in. The API's false positive and negative rates are documented. Building a real system means: tuning your confidence thresholds, designing the workflow for borderline cases, and monitoring quality as patterns shift.