Skip to content

Conversation

@atsushina
Copy link
Contributor

I hear from dev team that the number of recipients in email for SMTP cannot be increased more than 50 at this time (The one for REST API can be increased by the quota request).

I think that we should write the limit as a Note.

I hear from dev team that the number of recipients in email for SMTP cannot be increased more than 50 at this time (The one for REST API can be increased by the quota request).

I think that we should write the limit as a Note.
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 5939971:

✅ 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.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Nov 29, 2024

@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 Nov 29, 2024
@PMEds28
Copy link
Contributor

PMEds28 commented Jan 20, 2025

@tophpalmer

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

Hi @kagbakpem and @MsftPMACS, we were referred to you to ask about this PR.

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator
Copy link
Contributor

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

@prmerger-automator prmerger-automator bot requested a review from tophpalmer March 26, 2025 21:34
@v-dirichards
Copy link
Contributor

Hi @kagbakpem and @MsftPMACS,

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

I emailed the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

@kagbakpem I'll merge this PR based on your approval. If this article requires further changes, please open a separate pull request.

@v-dirichards v-dirichards merged commit b348528 into MicrosoftDocs:main Apr 10, 2025
2 checks passed
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.

7 participants