CODEWITHSUNDEEP
azureazure-functions
pawel.kalisz
pawel.kalisz

Reputation: 1245

Azure Functions without public endpoint

Is there a way to deploy some code as an Azure Function, but not expose it publicly? From what I see in documentation, AF always gets a public endpoint. Is that the only solution? I would like to build a solution in which AF are accessible only internally, by services which are behind firewall (no public access either). Is that possible?

Upvotes: 5

Views: 3278

Answers (3)

David Peden
David Peden

Reputation: 18464

You can apply access restrictions to an Azure Function. See my answer here.

Upvotes: 0

Andy T
Andy T

Reputation: 9901

Only HTTP trigger functions get a public endpoint. All other functions do not.

So you could create a queue trigger function, which has no public endpoint, and then have an internal service place a message in the queue that would cause the function to trigger.

Upvotes: 2

Mike S
Mike S

Reputation: 3169

Short Answer - No. If you're using the managed version through the Azure Portal, it's a public-facing service. However, there are some options that require more work on your part:

  1. There is an on-premise Azure Functions. You can get more details about that here: https://learn.microsoft.com/en-us/azure/azure-functions/functions-runtime-overview
  2. Azure Functions is open-source. You can deploy it yourself. The repro and more instructions are at: https://github.com/azure/azure-webjobs-sdk-script

Upvotes: 0

Related Questions