Azure Function

Question

I am attempting to deploy an Azure function and suddenly running into a 403 when performing the deployment where it seems something is being uploaded to a storage account but it seems that key authentication has been disabled (perhaps across the entire subscription by another person admin). I am not sure what storage account this is, how to set up the authentication, or how I can change my Azure function to not use this storage account? Is there a quick fix to re-enable my deployments?

Command:
func azure functionapp publish EuclidCICDAutomation --python

Log:
Generating summary of Oryx build

Deployment Log file does not exist in /tmp/oryx-build.log

The logfile at /tmp/oryx-build.log is empty. Unable to fetch the summary of build

Triggering recycle (preview mode disabled).

Linux Consumption plan has a 1.5 GB memory limit on a remote build container.

To check our service limit, please visit https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#service-limits

Writing the artifacts to a squashfs file

Parallel mksquashfs: Using 1 processor

Creating 4.0 filesystem on /home/site/artifacts/functionappartifact.squashfs, block size 131072.

[===========================================================-] 20828/20828 100%

Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072

    compressed data, compressed metadata, compressed fragments,

    compressed xattrs, compressed ids

    duplicates are removed

Filesystem size 99762.79 Kbytes (97.42 Mbytes)

    22.27% of uncompressed filesystem size (447874.14 Kbytes)

Inode table size 197739 bytes (193.10 Kbytes)

    27.85% of uncompressed inode table size (710023 bytes)

Directory table size 190044 bytes (185.59 Kbytes)

    28.48% of uncompressed directory table size (667380 bytes)

Number of duplicate files found 2229

Number of inodes 21934

Number of files 19467

Number of fragments 2105

Number of symbolic links 0

Number of device nodes 0

Number of fifo nodes 0

Number of socket nodes 0

Number of directories 2467

Number of ids (unique uids + gids) 1

Number of uids 1

    root (0)

Number of gids 1

    root (0)

Creating placeholder blob for linux consumption function app...

SCM_RUN_FROM_PACKAGE placeholder blob scm-latest-EuclidCICDAutomation.zip located

Uploading built content /home/site/artifacts/functionappartifact.squashfs for linux consumption function app...

Failed to upload because Azure Storage responds 403.

Key based authentication is not permitted on this storage account.

Generating summary of Oryx build

Deployment Log file does not exist in /tmp/oryx-build.log

The logfile at /tmp/oryx-build.log is empty. Unable to fetch the summary of build

Deployment Failed. deployer = Push-Deployer deploymentPath = Functions App ZipDeploy. Extract zip. Remote build.

Remote build failed!

Answer 1

Hello @David Gaspard

The error message suggests that key-based authentication is not permitted on the storage account. This could be due to the fact that key authentication has been disabled across the entire subscription by another admin.

To resolve this issue, you can try the following steps:

1. Check if you have the correct permissions to deploy the function. You need to have the Contributor or Owner role on the subscription or resource group level to deploy the function.
2. Check if you have the correct connection string for the storage account. You can find the connection string in the Azure portal under the storage account's settings. Make sure that the connection string is correct and that you have the correct permissions to access the storage account.
3. If key-based authentication is not permitted on the storage account, you can try using a SAS token instead. You can generate a SAS token for the storage account in the Azure portal under the storage account's settings. Make sure that the SAS token has the correct permissions to access the storage account.
4. If you are not sure which storage account is being used by your function, you can check the function's configuration settings in the Azure portal. The storage account connection string should be listed there.
5. If you are still unable to resolve the issue, you can try deploying the function to a different storage account. You can specify the storage account to use in the function's configuration settings.

If none of these steps work, reach out to me internally so I can help you further.