So I just created an Azure Function that is triggered by Azure Blob Storage upload. There is no HTTP trigger.
https://fa06192020test8.azurewebsites.net
(deleting soon, so hit it now!)
I don't want anything visible to the outside world.
AzureWebJobsDisableHomepage
app setting value to true
. However, you will still see a response when you hit the URL on the browser. Azure KeyVault
https://learn.microsoft.com/en-us/azure/key-vault/ and Managed Service Identity
https://learn.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview if you really really want to build secure Azure Functions on your high-level ops (Let's say you're parsing some government, PCI, PHI, PII
data)Since it's only Azure Blob Trigger Azure Functions, if you don't expose your azure functions URL to the Internet, nobody would predict your Azure Functions URL. Even if they predict, the above mentioned things would be still applied. So don't worry! :)
P.S. You can't (and also shouldn't) hide/remove the .azurewebsites.net URL. It's using everywhere. From deploying your code to the health checks. It's everywhere. Also, you should create HealthChecks via Application Insights as well to check whether your function is health or not.