No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@USZEU59B2> you can use the `DefaultHostname` property of `FunctionApp`.

Beyond that, you have to know the rest of the URL, as this depends on the HTTP triggers used in your function app, of which Pulumi can have no knowledge.

If you use a custom domain name for your function app, that domain name is its own resource (of type `CustomHostnameBinding`) so your Pulumi program would know about that too.

<@UF1PU93N1>, thanks, I've found that, but I'd still have to construct the Function App endpoint (https://`defaultHostname`/funcName). Was hoping to be able to access `getEndpoint()` just to avoid having to do that lots of times.

Right, I see what you mean. But I don’t think the Azure management plane has a representation of those endpoints, as they are more part of your app content, than the Function App resource at the Azure layer.

(BTW why do you have to do it lots of times?)

Because I may deploy more than 1 Function App per stack.
It's not a massive issue, just would have been nice to have the function available to a wider audience.

OK. Well maybe <@UB39JFCKC> should chime in, because I’m just a user, but I think you’re out of luck, I think you have to construct any endpoint URLs yourself.

Yeah, I sort don’t feel there’s enough value to expose this function. You could just put it into your code if you need it.

<@UB39JFCKC>, that's exactly what I've done. Seems a waste to duplicate code though ;)

It’s two lines, you are a perfectionist :wink: