Azure Function WebApp cannot start with error message - System.Private.CoreLib: Access to the path 'C:\home\site\wwwroot\host.json' is denied.

Maxim Rzhevskiy 30 Reputation points
2025-02-24T22:16:57.1233333+00:00

Azure Function WebApp cannot start with error message - System.Private.CoreLib: Access to the path 'C:\home\site\wwwroot\host.json' is denied.

Backend Kudu service is not responsive.

Any help on how to start WebApp?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,909 questions
{count} votes

Accepted answer
  1. Pravallika Kothaveeranna Gari 955 Reputation points Microsoft External Staff Moderator
    2025-03-05T15:37:06.1366667+00:00

    Hi @Maxim Rzhevskiy, I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue:

    Access denied to storage account from function app.

    Solution:

    The issue occurred because the Blob in Storage Account was set to Archive tier.

    As mentioned in MSDOC, a blob in the archive tier is offline which cannot be read or modified until it is rehydrated.

    While a blob is in the archive tier, it can't be read or modified.

    To read or download a blob in the archive tier, you must first rehydrate it to an online tier, either hot or cool.

    The rehydration process can take several hours and has associated costs.

    Please remember to "Accept Answer" if the sol has helped, so that others in the community facing similar issues can easily find the solution.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Maxim Rzhevskiy 30 Reputation points
    2025-03-05T04:21:56.12+00:00

    Yes, the issue was resolved. It turns out that WebApp was calling Storage Account BLOB which was set to Archive tier. Storage Account BLOB in Archive tier cannot be read.

    1 person found this answer helpful.
    0 comments No comments

  2. Maxim Rzhevskiy 30 Reputation points
    2025-03-05T04:23:42.6866667+00:00

    Yes, the issue was resolved. It turns out that WebApp was calling Storage Account BLOB which was set to Archive tier. Storage Account BLOB in Archive tier cannot be read.

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.