Hi @Daniel noyn
Welcome to Microsoft Q&A! Thanks for posting the question.
I will first suggest you to verify whether you are able to run your function app (HTTP trigger) from any of the tools such as postman/fiddler to verify whether you are able to execute your function or not. If you are not able to run the function app HTTP trigger then the troubleshooting needs to start from the function app end.
If the function was executed successfully then I will suggest you to review the blazor code how you are calling the function. If you have deployed the blazor code in azure storage then the suggestion will be to verify whether your storage in a virtual network or any NSG blocking the call to the azure function.
The above will help you with the initial troubleshooting to verify which component might be causing the issue. If you have configured the function authorization level then you can still pass the authentication keys in query parameter while calling the function endpoint.
I am also sharing some of the reference articles/videos that can help you start with Blazor, Azure Functions, and Azure Storage.
https://www.youtube.com/watch?v=QeSNtE4HnZY
https://azure.microsoft.com/en-in/resources/videos/build-2019-serverless-web-apps-with-blazor-azure-functions-and-azure-storage/
https://microsoft.github.io/AzureTipsAndTricks/blog/tip286.html
https://channel9.msdn.com/Shows/On-NET/Blazor-and-Azure-Functions
Once you have tested the above please share your result/observation if you need any assistance in troubleshooting it further.