Changes in Azure Function Storage Queue Integration

Question

Hi,

We began experiencing major issues with our Azure functions (.NET 8 Isolated, Consumption, Linux) the 6th of March. Suddenly, our queue triggered functions were not triggering correctly. After some trial and error, we discovered that we could trigger them manually by just visiting the function in the azure portal or by synchronizing the function triggers using the Sync-AzureFunctionTriggers powershell cmdlet. But they never triggered when the function was idle.

After being stuck in that state for almost a week, we finally found logs in our Storage Environment indicating that the queue metadata endpoint was failing (https://learn.microsoft.com/en-us/rest/api/storageservices/get-queue-metadata). It was failing because we used PascalCased queue-names in our .NET application while the storage queue enforced only lowercase letters.

So while there obviously was an error on our part, the same code had been working great for several years before this. Something must have changed in either the Azure Function or Storage Queue infrastructure.

We would like to be able to work proactively with these kinds of issues and identify them as fast as possible, preferably before they are released.

Our questions follows:

1. Was there release notes posted somewhere explaining this change?
2. Do you have any other tips regarding staying up to date with the continous development of azure functions, storage environments, etc.

Kind regards,

Mikael