Update Azure Queue storage trigger for Azure Functions to fix wrong instructions for local development

[tanguySnoeck]

The documentation states that:

_When you're running your function project locally, the above configuration tells the runtime to use your local developer identity. The connection attempts to get a token from the following locations, in order:

• A local cache shared between Microsoft applications
• The current user context in Visual Studio
• The current user context in Visual Studio Code
• The current user context in the Azure CLI_

In the aforementioned section, the "above configuration" most likely refers to this part of the article:

Token Credential	<CONNECTION_NAME_PREFIX>__credential	Defines how a token should be obtained for the connection. This setting should be set to managedidentity if your deployed Azure Function intends to use managed identity authentication. This value is only valid when a managed identity is available in the hosting environment.

However, using this value locally doesn't work and the following error message is returned by the azure function runtime:
Azure.Identity: ManagedIdentityCredential authentication unavailable. Multiple attempts failed to obtain a token from the managed identity endpoint. Azure.Core: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (A socket operation was attempted to an unreachable network. (169.254.169.254:80)), indicating that the local environment is trying to connect to the managed identity endpoint located at 169.254.169.254:80.

However, using the value defaultazurecredential instead of managedidentity for the <CONNECTION_NAME_PREFIX>__credential property proved to be working as expected and shows the behaviour currently expected from the documentation, i.e.,

_The connection attempts to get a token from the following locations, in order:

• A local cache shared between Microsoft applications
• The current user context in Visual Studio
• The current user context in Visual Studio Code
• The current user context in the Azure CLI_

Thank you in advance for processing.

[prmerger-automator]

@tanguySnoeck : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit c6a5943:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/functions-reference.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ttorble]

@ggailey777

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team