How to troubleshoot "functions runtime is unreachable"
This doc is intended to troubleshoot the following error when displayed in the Functions portal.
Error: Azure Functions Runtime is unreachable. Click here for details on storage configuration
This issue occurs when the Azure Functions Runtime cannot start. The most common reason for this error to occur is the function app losing access to its storage account. Read more about the storage account requirements here
We'll walk through the four most common error cases, how to identify, and how to resolve each case.
- Storage Account deleted
- Storage Account application settings deleted
- Storage Account credentials invalid
- Storage Account Inaccessible
- Daily Execution Quota Full
Storage account deleted
Every function app requires a storage account to operate. If that account is deleted your Function will not work.
How to find your storage account
Start by looking up your storage account name in your Application Settings. Either
WEBSITE_CONTENTAZUREFILECONNECTIONSTRING will contain the name of your storage account wrapped up in a connection string. Read more specifics at the application setting reference here
Search for your storage account in the Azure portal to see if it still exists. If it has been deleted, you will need to recreate a storage account and replace your storage connection strings. Your function code is lost and you will need to redeploy it again.
Storage account application settings deleted
In the previous step, if you did not have a storage account connection string they were likely deleted or overwritten. Deleting app settings is most commonly done when using deployment slots or Azure Resource Manager scripts to set application settings.
Required application settings
- Required for Consumption Plan Functions
- Do not check "slot setting" for any of these settings. When you swap deployment slots the Function will break.
- Do not set these settings when using automated deployments.
- These settings must be provided and valid at creation time. An automated deployment that does not contain these settings will result in a non-functional App, even if the settings are added after the fact.
Storage account credentials invalid
The above Storage Account connection strings must be updated if you regenerate storage keys. Read more about storage key management here
Storage account inaccessible
Your Function App must be able to access the storage account. Common issues that block a Functions access to a storage account are:
- Function Apps deployed to App Service Environments without the correct network rules to allow traffic to and from the storage account
- The storage account firewall is enabled and not configured to allow traffic to and from Functions. Read more about storage account firewall configuration here
Daily Execution Quota Full
If you have a Daily Execution Quota configured, your Function App will be temporarily disabled and many of the portal controls will become unavailable.
- To verify, check open Platform Features > Function App Settings in the portal. You will see the following message if you are over quota
The Function App has reached daily usage quota and has been stopped until the next 24 hours time frame.
- Remove the quota and restart your app to resolve the issue.
Now that your Function App is back and operational take a look at our quickstarts and developer references to get up and running again!
- Create your first Azure Function
Jump right in and create your first function using the Azure Functions quickstart.
- Azure Functions developer reference
Provides more technical information about the Azure Functions runtime and a reference for coding functions and defining triggers and bindings.
- Testing Azure Functions
Describes various tools and techniques for testing your functions.
- How to scale Azure Functions
Discusses service plans available with Azure Functions, including the Consumption hosting plan, and how to choose the right plan.
- Learn more about Azure App Service
Azure Functions leverages Azure App Service for core functionality like deployments, environment variables, and diagnostics.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.