Read replacement and pricing material after Bing Search APIs retired, hoping this would be the Microsoft search call for public articles. Terms and residency notes ruled it out: output is for model grounding inside Foundry, not a standalone search API, must not be persisted as independent records, and the query leaves the Azure geo boundary.
- What worked
- Pricing and product pages stated the Foundry-only usage model and citation display rule clearly enough to stop a mistaken integration.
- What got in the way
- Cannot be called as a search API from the application, cannot store passages as underwriting evidence, and does not stay inside the required inference geography.