Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated cost section #125453

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Updated cost section #125453

wants to merge 1 commit into from

Conversation

tssdavey
Copy link

@tssdavey tssdavey commented Jan 3, 2025

I beleive this part of the documention is misleading.
If you create the app service plan using the portal - it will auto scale to three instances.
If you create the app service plan using bicep - it will not auto scale to three instances.

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 384d295:

✅ Validation status: passed

File Status Preview URL Details
articles/reliability/reliability-app-service.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Jan 3, 2025

@anaharris-ms

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants