A milkweed-ditch partner asks for a PDF of every APIM operation. Where should the developer point them for official interactive documentation?
Select an answer to reveal the explanation.
Short Explanation
Skip the PDF scavenger hunt—the APIM developer portal is the milkweed-ditch partner’s docs, try-it, and definition download surface.
Full Explanation
The API Management developer portal is the supported partner-facing documentation surface: auto-generated operation docs, interactive try-it calls, and API definition download. That is what the milkweed-ditch partner should use to learn and exercise city APIs under products and subscriptions—not ad-hoc operational tools meant for platform operators.
Kudu is an App Service SCM and debug console for site content and process inspection, not an API catalog for external developers. Storage account metrics show capacity and transaction counters useful for ops, not OpenAPI operation documentation or try-it sessions. Event Grid dead-letter stores hold failed event deliveries for messaging troubleshooting; they are not a developer portal for HTTP APIs.
Exam caveat: when the question asks for docs, try-it, and definition download together, the answer is the APIM developer portal—not generic Azure monitoring, SCM, or messaging blades that happen to show “information.”
Operational check: open the milkweed-ditch APIM developer portal URL, sign in as a test developer, browse an API’s operations, run a try-it call with a valid subscription, and download the API definition to confirm the full partner documentation experience end to end.