Azure functions| function(s) are not visible in the portal

 Azure functions| function(s) are not visible in the portal

Issue:

•  Portal is not displaying functions.

Solution:

Azure functions (function app) is the container of function like http trigger, timer, blob trigger etc.

Not displaying function on portal after deployment or any other time is very common issue.

Here we are focusing on one scenario only which can be the potential cause of this issue there can be some other scenarios which are not covered here.

 

we are talking about a property which is very frequently used with deployments.

 

WEBSITE_RUN_FROM_PACKAGE

1.       Check value

a.       If WEBSITE_RUN_FROM_PACKAGE = 1

                        i.      Content location is (in KUDU), d:\home\data\SitePackages

1.       Validate if SitePackages folder is available or not?

2.       Validate if folder contains correct files/DLLs which are needed for functions

                      ii.      packagename.txt (Inside folder d:\home\data\SitePackages)

1.       Is it pointing to correct package or not?

2.       There should not be any whitespace in name mentioned inside packagename.txt.

                    iii.      WWWROOT folder

1.       Validate if contents are mounted properly from SitePackages folder to WWWROOT folder

2.       If contents are not mounted properly then you may see one txt file with name “FAILED TO INITIALIZE RUN FROM PACKAGE.txt”

 

b.       If WEBSITE_RUN_FROM_PACKAGE = <Storage account URL>

                        i.      Does Storage account exist?

1.       Yes?

a.       Validate connection string

                                                               i.      Check if connection string is correct or not.

                                                             ii.      Get the connection string from storage account and compare with the app settings value.

b.       Validate SAS expiry

                                                               i.      Check if SAS token is expired or not

c.       Validate connectivity.

                                                               i.      Check if any network or firewall restriction is preventing Azure functions to connect with storage account

d.       Sync trigger

                                                               i.      If functions are not visible after latest deployment the check if sync trigger (which is mandatory) operation was performed post deployment or not.

e.       Managed Identity

                                                               i.      Validate managed identity configurations.

                                                             ii.      Azure Blob Storage can be configured to authorize requests with Azure AD. This means that instead of generating a SAS key with an expiration, you can instead rely on the application's managed identity (Ref)

2.       No?

a.       Storage account is mandatory in this case.

b.   Exit

Hope this helps.