Let me start with the thing that colours everything else about this documentation. The product has changed names and shape more than once in a short period, and the documentation has been dragged along behind each change rather than rewritten for it. You will find pages using current terminology, pages using the previous terminology, and blog posts and Learn modules that sit somewhere in between, all reachable from a search and all appearing equally authoritative. This is not a trivial complaint.
When you are learning something new, you cannot tell which page is current, and the cost of following a stale one is an hour lost in a portal looking for a button that has moved. Anyone writing about this platform has to open with that warning, and Microsoft has had long enough to fix it. With that said, there is real substance here, and the evaluation material is where I would send someone first. Microsoft has invested properly in the question of how you know whether your application is any good, and the documentation reflects it.
There are built-in evaluators for groundedness, relevance, coherence and similarity, guidance on building your own, and a workflow for running them against test sets rather than eyeballing outputs. Most vendor documentation treats evaluation as a checkbox. This treats it as a practice, and a developer who reads that section carefully will come away with a better mental model of the problem than the tooling alone would give them. The content safety material is similarly serious.
Filters across the obvious harm categories, configurable severity, prompt shields for injection attempts, groundedness detection to catch fabrication. You can argue about whether the filters are calibrated well and people do, but the documentation explains what they are actually checking and what the severity levels mean, which is more transparency than the category usually offers. If you are shipping something to the public and someone in your organisation is going to ask what happens when a user tries to make it say something appalling, this is where you get your answer. The model catalogue coverage is genuinely broad and the deployment guidance is more honest than I expected.
Serverless endpoints, managed compute, and the trade-offs between them in cost and latency are laid out reasonably plainly. The distinction between models Microsoft serves directly and models you are deploying yourself onto compute you pay for by the hour is important and is not hidden. Enterprise concerns get proper treatment, which is the thing this documentation is genuinely for. Private networking, managed identity, customer-managed keys, regional availability, data residency.
These are boring and they are also the questions that actually determine whether a project gets approved, and there are few places outside cloud vendor documentation where they are written down at all. Now the structural problems. The volume is enormous and the signposting is weak. There is no clear reading order, the conceptual pages and the how-to pages and the reference pages interleave, and the search returns a mixture of current and outdated material with no visual distinction.
Finding the right page is a skill you develop over weeks, and it is a skill specific to this documentation rather than transferable knowledge. The reliance on portal instructions is the other persistent irritation. Long sequences of click here, then select this blade, then expand that panel, illustrated with screenshots that no longer match what you are looking at. Cloud portals change constantly and documenting a workflow as a click sequence guarantees the documentation rots.
The pages that lead with the SDK or the CLI age far better and there are not enough of them. And there is the deeper limitation that applies to all cloud vendor learning material. You are being taught Azure's decomposition of the problem. Hubs and projects and connections and deployments are Azure concepts, not concepts about building applications on language models, and someone who learns exclusively here ends up fluent in a vocabulary that does not travel.
Ask them to reason about evaluation or retrieval or cost outside this platform and the framework does not transfer cleanly. That is true of every cloud provider and it is still worth saying out loud. My three point three reflects the split. The evaluation and safety material is legitimately good and I would recommend it to people who will never touch Azure, because it explains the concepts well.
The enterprise coverage is thorough and hard to find elsewhere. Against that, the naming churn has left the documentation in a genuinely confusing state, the volume defeats navigation, the portal-first instructions go stale, and the whole thing teaches a platform rather than a discipline. Read it if you have to, and read the evaluation chapters even if you do not.