Skip to content

Web: clarify maximumInstanceCount is per function group - #45083

Open
CooperLink wants to merge 2 commits into
Azure:mainfrom
CooperLink:web/flexconsumption-maxinstancecount-perfunctiongroup-doc
Open

Web: clarify maximumInstanceCount is per function group#45083
CooperLink wants to merge 2 commits into
Azure:mainfrom
CooperLink:web/flexconsumption-maxinstancecount-perfunctiongroup-doc

Conversation

@CooperLink

@CooperLink CooperLink commented Jul 29, 2026

Copy link
Copy Markdown

Summary

Clarifies that the Flex Consumption maximumInstanceCount limit is the maximum number of on-demand instances per function group, not across the entire function app.

Updates the FunctionsScaleAndConcurrency.maximumInstanceCount description from:

"The maximum number of instances for the function app."

to:

"The maximum number of on demand instances per function group."

This matches the Flex Consumption scale-curve enforcement behavior.

Changes

  • Source of truth: AppService/models.tsp (@doc on maximumInstanceCount)
  • Regenerated emitted openapi.json for all TypeSpec-managed versions: 2025-03-01, 2025-05-01, 2026-03-01-preview, 2026-03-15, 2026-07-15

Description-only, non-breaking change. Pre-TypeSpec frozen versions (2023-12-01, 2024-04-01, 2024-11-01) are intentionally left unchanged.

Work item

AB#38015448

@github-actions

github-actions Bot commented Jul 29, 2026

Copy link
Copy Markdown

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).


Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added ARMReview resource-manager TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 29, 2026
@github-actions

github-actions Bot commented Jul 29, 2026

Copy link
Copy Markdown

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.Web-AppService
TypeSpec Microsoft.Web
Go sdk/resourcemanager/appservice/armappservice
JavaScript @azure/arm-appservice
Java com.azure.resourcemanager:azure-resourcemanager-appservice
Python azure-mgmt-web
C# Azure.ResourceManager.AppService

Comment generated by After APIView workflow run.

@github-actions github-actions Bot added ARMAutoSignedOff-IncrementalTSP ARMAutoSignedOff-Trivial ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMAutoSignedOff-IncrementalTSP ARMAutoSignedOff-Trivial ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review resource-manager TypeSpec Authored with TypeSpec Web Apps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant