Skip to content

Clarify updatable properties for draft messages#9832

Open
grtaylor806 wants to merge 1 commit intomicrosoftgraph:mainfrom
grtaylor806:patch-2
Open

Clarify updatable properties for draft messages#9832
grtaylor806 wants to merge 1 commit intomicrosoftgraph:mainfrom
grtaylor806:patch-2

Conversation

@grtaylor806
Copy link
Contributor

Updated properties to indicate they are updatable only if isDraft = true.

Important

Required for API changes:

  • [] Link to API.md file: ADD LINK HERE
  • [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE
  • [] OPTIONAL: Attach the documentation plan generated for AI-assisted docs authoring and validation to help speed up content review.

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

ADD INFORMATION HERE


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.

Updated properties to indicate they are updatable only if isDraft = true.
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 2aaf533:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/message-update.md ✅Succeeded

For more details, please refer to the build report.

@grtaylor806 grtaylor806 added the ready for content review PR is ready for a content review - content development and tech review are complete. label Mar 10, 2026
Copy link
Contributor

@FaithOmbongi FaithOmbongi left a comment

Choose a reason for hiding this comment

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

See review feedback inline

| Property | Type |Description|
|:---------------|:--------|:----------|
|bccRecipients|Recipient|The Bcc recipients for the message. |
|bccRecipients|Recipient|The Bcc recipients for the message. Updatable only if isDraft = true.|
Copy link
Contributor

Choose a reason for hiding this comment

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

@grtaylor806 - not: Please format all instances to match this change to ensure the formatted text remains the same in translated content. Update the beta file as well. Thank you.

Suggested change
|bccRecipients|Recipient|The Bcc recipients for the message. Updatable only if isDraft = true.|
|bccRecipients|Recipient|The Bcc recipients for the message. Updatable only if **isDraft** = `true`.|

Copy link
Contributor Author

@grtaylor806 grtaylor806 Mar 11, 2026

Choose a reason for hiding this comment

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

@FaithOmbongi - I was matching the style of other lines that already have this comment/statement, in that style. Lines 47 and 59 for example. So are you saying we need to change all of those lines too?

@FaithOmbongi FaithOmbongi self-assigned this Mar 11, 2026
@FaithOmbongi FaithOmbongi added changes requested content review in progress and removed ready for content review PR is ready for a content review - content development and tech review are complete. labels Mar 11, 2026
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.

2 participants