Architecture Guidance Sources

The URLs in this document are a list of sources for “where to look”. Do not hardcode the contents of these URLs as fixed facts. Do not use for SKU, API version, region, model availability, or PE mapping decisions — those are handled exclusively via azure-dynamic-sources.md.

Purpose Separation

What must NOT be decided using this document:

• API version
• SKU names/pricing
• Region availability
• Model names/versions/deployment types
• PE groupId / DNS Zone mapping
• Specific values for resource properties

Primary Sources

Targeted fetch targets for design direction decisions.

Secondary Sources (awareness only)

Not direct fetch targets; referenced only for change awareness.

Fetch Trigger — When to Query

Architecture guidance documents are not queried on every request. Only perform targeted fetch when the following triggers apply.

Trigger Conditions

0. When the user’s workload type is identified in Phase 1 (automatic)
   • Pre-query the relevant workload’s reference architecture to adjust question depth
   • Triggers automatically even if the user doesn’t mention “best practice” etc.
   • Purpose: Reflect official architecture-based design decision points in questions, beyond SKU/region spec questions
1. When the user requests design direction justification
   • Keywords such as “best practice”, “reference architecture”, “recommended structure”, “baseline”, “well-architected”, “landing zone”, “enterprise pattern”
2. When architecture boundaries for a new service combination are ambiguous
   • Inter-service relationships that cannot be determined from existing reference files/service-gotchas
3. When enterprise-level security/governance design is needed
   • Subscription structure, network topology, landing zone patterns

When Triggers Do Not Apply

• Simple resource creation (SKU/API version/region questions) → Use only azure-dynamic-sources.md
• Service combinations already covered in domain-packs → Prioritize reference files
• Bicep property value verification → service-gotchas.md or MS Docs Bicep reference

Fetch Budget

Decision Rule by Question Type

URL Fallback Rule

1. Use en-us Learn URLs by default
2. If a specific URL returns 404 / redirect / deprecated → Fall back to the parent hub page
   • Example: If A5 fails → Search for “foundry chat” keyword on A4 (AI/ML hub)
3. If not found on the parent hub either → Search by title keyword on A1 (Architecture Center main)
4. Do not use the contents of a URL as fixed rules just because the URL exists

Full Traversal Prohibited

• Do not broadly traverse (crawl) Architecture Center sub-documents
• Only targeted fetch 1–2 related documents according to the decision rule by question type
• Even within fetched documents, only reference relevant sections; do not read the entire document
• Unlimited fetching, recursive link following, and sub-page enumeration are prohibited