Skip to content

Update service-limits.md for ACS Chat to introduce new limits #127090

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

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

Conversation

tariqzafa700
Copy link

ACS Chat is going to add a new limit to throttle the usage of create chat thread and add chat participant APIs based on the requests from the same resource Id. Although the throttle limit exists on number of chat thread created per user but since a resource has the ability to create many such users, so we need to put a throttle limit at resource Id level.

ACS Chat is going to add a new limit to throttle the usage of create chat thread and add chat participant APIs based on the requests from the same resource Id. Although the throttle limit exists on number of chat thread created per user but since a resource has the ability to create many such users, so we need to put a throttle limit at resource Id level.
Copy link
Contributor

@tariqzafa700 : 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 121f29c:

✅ Validation status: passed

File Status Preview URL Details
articles/communication-services/concepts/service-limits.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@tophpalmer

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 Jun 11, 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