ListSecrets not working on .NET 8 isolated functions running on a dedicated plan

Annelotte Mons 25 Reputation points
2024-05-08T14:47:19.7833333+00:00

Recently upgraded a .NET 6 functions project to .NET 8 isolated worker model. Turns out this breaks our deployments which are using the "listSecrets()" functionality to get the function keys. When looking in the portal its working fine on a reference to it, but the listSecrets on it fails with an error message stating Function Not Found.

The functions themselves seem to work just fine in Azure on the dedicated plan. So I'm a bit puzzled that this functionality isn't working?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,353 questions
{count} vote

Accepted answer
  1. MayankBargali-MSFT 69,416 Reputation points
    2024-05-10T12:38:45.4666667+00:00

    @Annelotte Mons Thanks for confirmation.

    Can you please update the listSecrets to listkeys in your ARM template and see if it helps you to resolve the issue.

    I see a previous discussion here where the team recommended to use ListKeys instead of ListSecrets as you shouldn't be used anymore.

    Let me know if you still face the issue after leveraging the listkeys method in your ARM template.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful