A jasmine-walk APIM instance exists, but callers still get 404 because nothing was published to the gateway. What must the developer configure?
Select an answer to reveal the explanation.
Short Explanation
The instance is the box—not the API. Create the API, set the backend URL, map operations, then callers stop seeing jasmine-walk 404s.
Full Explanation
To expose a backend through API Management without an OpenAPI file, create an API in APIM, set the backend service URL, and map operations (HTTP method plus URL template) so the gateway knows how to forward calls. That manual definition path is how the juniper-creek team stands up a managed API when no specification import is available yet still needs products, policies, and portal discovery.
Only creating a storage account does not define HTTP operations or a gateway route—blobs and tables are not an API facade. Publishing a Function app alone exposes compute over HTTPS but is not the same as registering that backend inside APIM with products, subscriptions, and policies. Dropping a PDF of endpoints into a repo documents tribal knowledge for operators; it does not configure the management plane or create try-it documentation.
Exam caveat: import is preferred when a spec exists, but blank API plus operations plus backend URL is the valid manual path—do not invent a requirement that OpenAPI is mandatory before APIM can front a municipal service.
Operational check: in APIM, add a blank API, set the juniper-creek backend URL, add at least one operation matching a real backend route, test via the portal’s test console or curl through the gateway hostname, then attach the API to a product so developers can subscribe.