Skip to content

Conversation

@skmkzyk
Copy link
Contributor

@skmkzyk skmkzyk commented Oct 23, 2025

Clarified billing information regarding Capacity Unit Hour charges and default instance exclusions.

Clarified billing information regarding Capacity Unit Hour charges and default instance exclusions.
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit fcf461d:

✅ Validation status: passed

File Status Preview URL Details
articles/firewall/prescaling.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot October 23, 2025 14:39
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the billing documentation for Azure Firewall prescaling to provide clearer information about how Capacity Unit Hour charges work in relation to regular Azure Firewall fees and default instance allocations.

  • Clarified that Capacity Unit Hour charges are in addition to regular Azure Firewall fees
  • Added explanation that two default running instances are excluded from billable capacity unit calculations

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.


Prescaling introduces a **Capacity Unit Hour** billing meter. You pay based on the number of capacity units provisioned per hour.
Prescaling introduces a **Capacity Unit Hour** billing meter that is **charged in addition to** the regular Azure Firewall fees, calculated per provisioned capacity unit per hour.
Note that the instance count used for this calculation excludes the two default running instances—so if 10 instances are provisioned, the billable count is 8.
Copy link

Copilot AI Oct 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The explanation uses an em dash followed by 'so' which creates a run-on sentence structure. Consider splitting into two sentences or using a colon for better clarity: 'Note that the instance count used for this calculation excludes the two default running instances. For example, if 10 instances are provisioned, the billable count is 8.' Alternatively: 'Note that the instance count used for this calculation excludes the two default running instances: if 10 instances are provisioned, the billable count is 8.'

Suggested change
Note that the instance count used for this calculation excludes the two default running instances—so if 10 instances are provisioned, the billable count is 8.
Note that the instance count used for this calculation excludes the two default running instances. For example, if 10 instances are provisioned, the billable count is 8.

Copilot uses AI. Check for mistakes.
@v-dirichards
Copy link
Contributor

@sujamiya

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 Oct 23, 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