recall&buildMy learning

Azure AI architecture

Four short sessions. One idea per card.

Session 1 · card 1 of 4Browse without signing in
Intelligent applicationTap a component to learn its role.

Orchestration calls these layers and receives results ↓

History · retrieved context · generated output · business actions

Original teaching diagram based on Microsoft’s pattern. Logical roles may share a service; this is not a required Azure resource list.

Follow one example request
  1. An employee asks whether a taxi is reimbursable.
  2. The API authenticates the request and checks access.
  3. Orchestration loads relevant history and permitted policy passages.
  4. The model drafts an answer using that context.
  5. If a claim must be submitted, a separate tool checks permissions and any required approval.
  6. The application validates and returns the result, recording appropriate evidence.

This is our illustrative walkthrough, not a claim that every request needs every layer.

See the highlighted architecture ↓

TWO KINDS OF AI WORKLOAD

Does a RAG assistant need to train its own model?

Explain it in your own words, then compare.

1 / 16
Connect this idea to a hands-on lab