Skip to content

Conversation

prithads
Copy link
Contributor

added batch delete quotas per SKU

added batch delete quotas per SKU
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit e03b2f0:

💡 Validation status: suggestions

File Status Preview URL Details
articles/service-bus-messaging/batch-delete.md 💡Suggestion Details

articles/service-bus-messaging/batch-delete.md

  • Line 28, Column 36: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/azure.messaging.servicebus.servicebusreceiver.deletemessagesasync?view=azure-dotnet-preview
  • Line 33, Column 28: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/azure.messaging.servicebus.servicebusreceiver.purgemessagesasync?view=azure-dotnet-preview

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.

@ttorble ttorble requested a review from Copilot September 29, 2025 14:48
Copy link
Contributor

@Copilot 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 adds quota information to the batch delete documentation, specifically detailing the maximum batch size limits for different Azure Service Bus tiers.

  • Added a new "Quotas" section explaining tier-based limits for batch delete operations
  • Included a table showing maximum batch sizes for Standard (500 messages) and Premium (4000 messages) tiers

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

Comment on lines +63 to +66
| Tier | Maximum Batch Size per Request |
|:-----------:|:----------------------------:|
| Standard | 500 messages |
| Premium | 4000 messages |
Copy link
Preview

Copilot AI Sep 29, 2025

Choose a reason for hiding this comment

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

The table has inconsistent spacing and formatting. The header row has extra spaces around 'Tier' and the alignment syntax uses colons on both sides for center alignment but only one column appears to need centering. Consider using standard left alignment for both columns or ensure consistent spacing.

Suggested change
| Tier | Maximum Batch Size per Request |
|:-----------:|:----------------------------:|
| Standard | 500 messages |
| Premium | 4000 messages |
| Tier | Maximum Batch Size per Request |
| --- | --- |
| Standard | 500 messages |
| Premium | 4000 messages |

Copilot uses AI. Check for mistakes.

Comment on lines +61 to +62


Copy link
Preview

Copilot AI Sep 29, 2025

Choose a reason for hiding this comment

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

There are unnecessary empty lines before the table. Remove the extra blank lines on lines 61 and 62 to maintain consistent spacing in the documentation.

Suggested change

Copilot uses AI. Check for mistakes.

@ttorble
Copy link
Contributor

ttorble commented Sep 29, 2025

Hi @prithads - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

@spelluru

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 Sep 29, 2025
@prithads
Copy link
Contributor Author

prithads commented Oct 3, 2025 via email

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @spelluru

@ShannonLeavitt
Copy link
Contributor

@prithads - You can find the documentation, including instructions on how to pull your commits into the private repo, here.

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.

4 participants