Add instructions about consumption plan for azure functions deployment best practices#218
Merged
fanyang-mono merged 4 commits intomicrosoft:mainfrom Sep 4, 2025
Conversation
fanyang-mono
requested review from
a team,
conniey and
g2vinay
as code owners
fanyang-mono
requested review from
JasonYeMSFT,
JonathanCrd,
alzimmermsft,
joshfree,
tmeschter and
xiangyan99
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates Azure Functions deployment best practices documentation to provide clearer guidance on hosting plans and deployment configurations. The changes emphasize using Flex Consumption (FC1) plan over Y1 dynamic plan and add specific configuration requirements.
- Replaced generic hosting plan guidance with specific mandate to use FC1 over Y1
- Added requirement for functionAppConfig with deployment.storage for FC1 Function Apps
- Enhanced documentation with specific Azure sample repositories for reference
…unctions-deployment-best-practices.txt Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
JasonYeMSFT
approved these changes
Sep 3, 2025
github-project-automation
Bot
moved this from Untriaged
to In Progress
in Azure MCP Server
JasonYeMSFT
approved these changes
Sep 4, 2025
feiskyer
pushed a commit
to feiskyer/microsoft-mcp
that referenced
this pull request
Sep 8, 2025
…osoft#218) * Refactor ParseJsonOutput to use ParseError record and add test for handling non-JSON output * Fix formatting in ParseJsonOutput method and clean up AzCommandTests for non-JSON output handling
colbytimm
pushed a commit
to colbytimm/microsoft-mcp
that referenced
this pull request
Sep 27, 2025
…t best practices (microsoft#218) * Add instructions for consumption plan * Update tools/Azure.Mcp.Tools.AzureBestPractices/src/Resources/azure-functions-deployment-best-practices.txt Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update CHANGELOG * Update tests --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Add instructions about consumption plan for azure functions deployment best practices
GitHub issue number?
N/A
Pre-merge Checklist
CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies).\eng\common\spelling\Invoke-Cspell.ps1README.mddocumentation/docs/azmcp-commands.md/docs/e2eTestPrompts.mdToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptscrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test Pipeline