Update functions-best-practices.md

[azarboon]

I'm afraid the current "best practice" is incomplete. It mentions only about concurrency but both parallelism and concurrency have to be considered. Also, it doesn't mention anything about languages' built-in support for those features. I've added those.

[prmerger-automator[bot]]

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

[learn-build-service-prod[bot]]

Learn Build status updates of commit 72c2c7f:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/functions-best-practices.md	:white_check_mark: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

[ShannonLeavitt]

@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

[v-ccolin]

I sent an email to the content owner on 01/12/2025.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@ggailey777

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod[bot]]

Learn Build status updates of commit 4980167:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	:x:Error		Details

• [Error: CannotMergeCommit] Cannot merge commit 498016756efd0f3f4f5862cbd14c07794e3bad4a in branch patch-98367 of repository https://github.com/azarboon/azure-docs into branch main (commit 58e0fcfe8d00f4f6325f60b59c81285fe64dd444). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[azarboon]

@v-dirichards thanks. I committed your suggestion but it says there is a conflict. Can you please check that out?

[learn-build-service-prod[bot]]

Learn Build status updates of commit 7242315:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/functions-best-practices.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

[azarboon]

@ggailey777 @v-dirichards can you please authorize this merge?

[v-dirichards]

@ggailey777 @v-dirichards can you please authorize this merge?

@azarboon In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM.

---

@ggailey777 Could you take a look? Thanks!