Update chatmessage-post.md

[dylanstetts]

Adding specifics the limitations for API throughput, hence why we do not recommend using this API for data migration (10 requests per 10 seconds)

Important

Required for API changes:

• Link to API.md file: https://github.com/microsoftgraph/microsoft-graph-docs-contrib/blob/main/api-reference/v1.0/api/chatmessage-post.md)
• Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl) VALID PRs DON'T INCLUDE API.MD or permissions JSON FILES: main...dylanstetts:microsoft-graph-docs-contrib:patch-4#diff-ff3ddd5e6bd4505b88803794f723a16a1531dffeeff199159b2eda2950edfc20

---

Add other supporting information, such as a description of the PR changes:

Small change indicating the throughput limit for the API. This throughput information was provided by engineering on Incident 641163449

---

Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.

• do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
• Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
• If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
• After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
• Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

[learn-build-service-prod]

Learn Build status updates of commit 6eb42da:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/v1.0/api/chatmessage-post.md	✅Succeeded

For more details, please refer to the build report.

[Danielabom]

PR approved.

[learn-build-service-prod]

Learn Build status updates of commit 5a73882:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/v1.0/api/chatmessage-post.md	✅Succeeded

For more details, please refer to the build report.