A larkspur-field product is fully configured, but partners still see an empty developer portal. What step is missing?
Select an answer to reveal the explanation.
Short Explanation
Configured isn’t published. Flip the product (and API) to published or the larkspur-field portal stays empty.
Full Explanation
Creating an API or product draft is not enough for partners to see and subscribe. The lilac-fen team must publish the product (and ensure the API is in a published state as required by the portal configuration) so it becomes visible in the developer portal for subscription. Publication is the deliberate lifecycle step that surfaces the package to developers rather than leaving it as admin-only configuration.
Keeping everything in a private draft forever blocks discovery and onboarding even when the backend is healthy. Emailing backend URLs directly to partners bypasses APIM’s subscription, policy, and analytics model and reintroduces unmanaged origin exposure. Moving definitions into a private Git repo shares source control artifacts with staff but does not publish anything to the developer portal.
Exam caveat: unpublished products remain invisible to developers even if APIs exist in the management plane—publish is a required step, not an automatic side effect of saving an API.
Operational check: set the lilac-fen product to Published, confirm it appears for the intended portal groups, complete a test subscription from the developer portal, and verify the issued key authorizes calls through the gateway while unpublished siblings stay hidden.