Text decision tree
Choose deployment geography, capacity, model source and tuning after selecting Microsoft Foundry.
Adapted from Chapter 20 of Decision Trees: Frameworks for Technology Choices. Sources reviewed 2026-11-05.
START
Q5 Processing constrained to a geography?
YES -> Data Zone or Regional. Choose a supported scope that satisfies the boundary. Then Q6.
NO -> Otherwise evaluate a Global deployment. Continue to the load-shape question. Then Q6.
Q6 What is the load shape?
CHOOSE -> Steady / Spiky / Offline. Provisioned / Standard / Batch, where supported. Then Q7.
Q7 Which model source and support contract?
CHECK -> Azure-sold or partner model. Check terms, support, filtering and availability. Then Q8.
Q8 Prompting and retrieval fail the evaluation set?
YES -> Consider supported fine-tuning. Evaluate SFT, DPO or RFT only where applicable. Then Q9.
NO -> If they already meet the target, do not fine-tune merely to add another component. Then Q9.
Q9 Existing legacy resources, APIs or SDK code?
YES -> Plan migration before the build. Check the current lifecycle and compatibility. Then END.
NO -> Otherwise continue with the selected supported configuration. Then END.
END: The deployment choice is complete only when the selected model, geography, capacity and API combination is supported.
AI-generated chapter illustration
BookWriter-generated chapter 20 illustration
This AI-generated illustration gives a visual overview. It can simplify labels or imply connections that do not preserve every decision. For exact branches, prerequisites and stop conditions, follow the video graph and the text tree above.
Reference links
- September Foundry update — 2026-10-16.
- Microsoft Copilot harness in Foundry Agent Service — 2026-10-28.
- Hosted-agent network egress controls — 2026-09-24.