Microsoft.Graph.Beta.Mail Module
Microsoft Graph PowerShell Cmdlets
Microsoft.Graph.Beta.Mail Cmdlets
| Cmdlet | Description |
|---|---|
| Copy-MgBetaUserMailFolder |
Copy a mail folder and its contents to another mail folder. Note To view the v1.0 release of this cmdlet, view Copy-MgUserMailFolder |
| Copy-MgBetaUserMailFolderChildFolder |
Copy a mail folder and its contents to another mail folder. Note To view the v1.0 release of this cmdlet, view Copy-MgUserMailFolderChildFolder |
| Copy-MgBetaUserMailFolderChildFolderMessage |
Copy a message to a folder within the user's mailbox. Note To view the v1.0 release of this cmdlet, view Copy-MgUserMailFolderChildFolderMessage |
| Copy-MgBetaUserMailFolderMessage |
Copy a message to a folder within the user's mailbox. Note To view the v1.0 release of this cmdlet, view Copy-MgUserMailFolderMessage |
| Copy-MgBetaUserMessage |
Copy a message to a folder within the user's mailbox. Note To view the v1.0 release of this cmdlet, view Copy-MgUserMessage |
| Get-MgBetaUserInferenceClassification |
Relevance classification of the user's messages based on explicit designations that override inferred relevance or importance. Note To view the v1.0 release of this cmdlet, view Get-MgUserInferenceClassification |
| Get-MgBetaUserInferenceClassificationOverride |
A set of overrides for a user to always classify messages from specific senders in certain ways: focused, or other. Read-only. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserInferenceClassificationOverride |
| Get-MgBetaUserInferenceClassificationOverrideCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserInferenceClassificationOverrideCount |
| Get-MgBetaUserMailFolder |
The user's mail folders. Read-only. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolder |
| Get-MgBetaUserMailFolderChildFolder |
The collection of child folders in the mailFolder. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolder |
| Get-MgBetaUserMailFolderChildFolderCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderCount |
| Get-MgBetaUserMailFolderChildFolderDelta |
Get a set of mail folders that have been added, deleted, or removed from the user's mailbox. A delta function call for mail folders in a mailbox is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls,you can query for incremental changes in the mail folders. This allows you to maintain and synchronizea local store of a user's mail folders without having to fetch all the mail folders of that mailbox from the server every time. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderDelta |
| Get-MgBetaUserMailFolderChildFolderMessage |
The collection of messages in the mailFolder. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessage |
| Get-MgBetaUserMailFolderChildFolderMessageAttachment |
The fileAttachment and itemAttachment attachments for the message. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageAttachment |
| Get-MgBetaUserMailFolderChildFolderMessageAttachmentCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageAttachmentCount |
| Get-MgBetaUserMailFolderChildFolderMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageContent |
| Get-MgBetaUserMailFolderChildFolderMessageCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageCount |
| Get-MgBetaUserMailFolderChildFolderMessageDelta |
Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can query for incremental changes in the messages inthat folder. Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageDelta |
| Get-MgBetaUserMailFolderChildFolderMessageExtension |
The collection of open extensions defined for the message. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageExtension |
| Get-MgBetaUserMailFolderChildFolderMessageExtensionCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageExtensionCount |
| Get-MgBetaUserMailFolderChildFolderMessageMention |
A collection of mentions in the message, ordered by the createdDateTime from the newest to the oldest. By default, a GET /messages does not return this property unless you apply $expand on the property. |
| Get-MgBetaUserMailFolderChildFolderMessageMentionCount |
Get the number of the resource |
| Get-MgBetaUserMailFolderChildFolderMessageRule |
The collection of rules that apply to the user's Inbox folder. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageRule |
| Get-MgBetaUserMailFolderChildFolderMessageRuleCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderChildFolderMessageRuleCount |
| Get-MgBetaUserMailFolderChildFolderOperation |
Get operations from users |
| Get-MgBetaUserMailFolderChildFolderOperationCount |
Get the number of the resource |
| Get-MgBetaUserMailFolderChildFolderUserConfiguration |
Get userConfigurations from users |
| Get-MgBetaUserMailFolderChildFolderUserConfigurationCount |
Get the number of the resource |
| Get-MgBetaUserMailFolderCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderCount |
| Get-MgBetaUserMailFolderDelta |
Get a set of mail folders that have been added, deleted, or removed from the user's mailbox. A delta function call for mail folders in a mailbox is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls,you can query for incremental changes in the mail folders. This allows you to maintain and synchronizea local store of a user's mail folders without having to fetch all the mail folders of that mailbox from the server every time. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderDelta |
| Get-MgBetaUserMailFolderMessage |
The collection of messages in the mailFolder. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessage |
| Get-MgBetaUserMailFolderMessageAttachment |
The fileAttachment and itemAttachment attachments for the message. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageAttachment |
| Get-MgBetaUserMailFolderMessageAttachmentCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageAttachmentCount |
| Get-MgBetaUserMailFolderMessageCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageCount |
| Get-MgBetaUserMailFolderMessageDelta |
Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can query for incremental changes in the messages inthat folder. Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageDelta |
| Get-MgBetaUserMailFolderMessageExtension |
The collection of open extensions defined for the message. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageExtension |
| Get-MgBetaUserMailFolderMessageExtensionCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageExtensionCount |
| Get-MgBetaUserMailFolderMessageMention |
A collection of mentions in the message, ordered by the createdDateTime from the newest to the oldest. By default, a GET /messages does not return this property unless you apply $expand on the property. |
| Get-MgBetaUserMailFolderMessageMentionCount |
Get the number of the resource |
| Get-MgBetaUserMailFolderMessageRule |
The collection of rules that apply to the user's Inbox folder. Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageRule |
| Get-MgBetaUserMailFolderMessageRuleCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMailFolderMessageRuleCount |
| Get-MgBetaUserMailFolderOperation |
Get operations from users |
| Get-MgBetaUserMailFolderOperationCount |
Get the number of the resource |
| Get-MgBetaUserMailFolderUserConfiguration |
Get userConfigurations from users |
| Get-MgBetaUserMailFolderUserConfigurationCount |
Get the number of the resource |
| Get-MgBetaUserMessage |
The messages in a mailbox or folder. Read-only. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserMessage |
| Get-MgBetaUserMessageAttachment |
The fileAttachment and itemAttachment attachments for the message. Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageAttachment |
| Get-MgBetaUserMessageAttachmentCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageAttachmentCount |
| Get-MgBetaUserMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageContent |
| Get-MgBetaUserMessageCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageCount |
| Get-MgBetaUserMessageDelta |
Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can query for incremental changes in the messages inthat folder. Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageDelta |
| Get-MgBetaUserMessageExtension |
The collection of open extensions defined for the message. Nullable. Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageExtension |
| Get-MgBetaUserMessageExtensionCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgUserMessageExtensionCount |
| Get-MgBetaUserMessageMention |
A collection of mentions in the message, ordered by the createdDateTime from the newest to the oldest. By default, a GET /messages does not return this property unless you apply $expand on the property. |
| Get-MgBetaUserMessageMentionCount |
Get the number of the resource |
| Invoke-MgBetaForwardUserMailFolderChildFolderMessage |
Forward a message using either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to forward a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgForwardUserMailFolderChildFolderMessage |
| Invoke-MgBetaForwardUserMailFolderMessage |
Forward a message using either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to forward a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgForwardUserMailFolderMessage |
| Invoke-MgBetaForwardUserMessage |
Forward a message using either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to forward a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgForwardUserMessage |
| Invoke-MgBetaMarkUserMailFolderChildFolderMessageAsJunk |
Mark a message as junk. This API adds the sender to the list of blocked senders and moves the message to the Junk Email folder, when moveToJunk is true. |
| Invoke-MgBetaMarkUserMailFolderChildFolderMessageAsNotJunk |
Mark a message as not junk. This API removes the sender from the list of blocked senders and moves the message to the Inbox folder, when moveToInbox is true. |
| Invoke-MgBetaMarkUserMailFolderMessageAsJunk |
Mark a message as junk. This API adds the sender to the list of blocked senders and moves the message to the Junk Email folder, when moveToJunk is true. |
| Invoke-MgBetaMarkUserMailFolderMessageAsNotJunk |
Mark a message as not junk. This API removes the sender from the list of blocked senders and moves the message to the Inbox folder, when moveToInbox is true. |
| Invoke-MgBetaMarkUserMessageAsJunk |
Mark a message as junk. This API adds the sender to the list of blocked senders and moves the message to the Junk Email folder, when moveToJunk is true. |
| Invoke-MgBetaMarkUserMessageAsNotJunk |
Mark a message as not junk. This API removes the sender from the list of blocked senders and moves the message to the Inbox folder, when moveToInbox is true. |
| Invoke-MgBetaReplyAllUserMailFolderChildFolderMessage |
Reply to all recipients of a message using either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply-all to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyAllUserMailFolderChildFolderMessage |
| Invoke-MgBetaReplyAllUserMailFolderMessage |
Reply to all recipients of a message using either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply-all to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyAllUserMailFolderMessage |
| Invoke-MgBetaReplyAllUserMessage |
Reply to all recipients of a message using either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply-all to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyAllUserMessage |
| Invoke-MgBetaReplyUserMailFolderChildFolderMessage |
Reply to the sender of a message using either JSON or MIME format. When using JSON format:* Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.* If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyUserMailFolderChildFolderMessage |
| Invoke-MgBetaReplyUserMailFolderMessage |
Reply to the sender of a message using either JSON or MIME format. When using JSON format:* Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.* If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyUserMailFolderMessage |
| Invoke-MgBetaReplyUserMessage |
Reply to the sender of a message using either JSON or MIME format. When using JSON format:* Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.* If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply to a message, and send it later. Note To view the v1.0 release of this cmdlet, view Invoke-MgReplyUserMessage |
| Invoke-MgBetaUnsubscribeUserMailFolderChildFolderMessage |
Submits an email request on behalf of the signed-in user to unsubscribe from an email distribution list. Uses the information in the List-Unsubscribe header. Message senders can use mailing lists in a user-friendly way by including an option for recipients to opt out. They can do so by specifying the List-Unsubscribe header in each message following RFC-2369. Note In particular, for the unsubscribe action to work, the sender must specify mailto: and not URL-based unsubscribe information. Setting that header would also set the unsubscribeEnabled property of the message instance to true, and the unsubscribeData property to the header data. If the unsubscribeEnabled property of a message is true, you can use the unsubscribe action to unsubscribe the user from similar future messages as managed by the message sender. A successful unsubscribe action moves the message to the Deleted Items folder. The actual exclusion of the user from future mail distribution is managed by the sender. |
| Invoke-MgBetaUnsubscribeUserMailFolderMessage |
Submits an email request on behalf of the signed-in user to unsubscribe from an email distribution list. Uses the information in the List-Unsubscribe header. Message senders can use mailing lists in a user-friendly way by including an option for recipients to opt out. They can do so by specifying the List-Unsubscribe header in each message following RFC-2369. Note In particular, for the unsubscribe action to work, the sender must specify mailto: and not URL-based unsubscribe information. Setting that header would also set the unsubscribeEnabled property of the message instance to true, and the unsubscribeData property to the header data. If the unsubscribeEnabled property of a message is true, you can use the unsubscribe action to unsubscribe the user from similar future messages as managed by the message sender. A successful unsubscribe action moves the message to the Deleted Items folder. The actual exclusion of the user from future mail distribution is managed by the sender. |
| Invoke-MgBetaUnsubscribeUserMessage |
Submits an email request on behalf of the signed-in user to unsubscribe from an email distribution list. Uses the information in the List-Unsubscribe header. Message senders can use mailing lists in a user-friendly way by including an option for recipients to opt out. They can do so by specifying the List-Unsubscribe header in each message following RFC-2369. Note In particular, for the unsubscribe action to work, the sender must specify mailto: and not URL-based unsubscribe information. Setting that header would also set the unsubscribeEnabled property of the message instance to true, and the unsubscribeData property to the header data. If the unsubscribeEnabled property of a message is true, you can use the unsubscribe action to unsubscribe the user from similar future messages as managed by the message sender. A successful unsubscribe action moves the message to the Deleted Items folder. The actual exclusion of the user from future mail distribution is managed by the sender. |
| Move-MgBetaUserMailFolder |
Move a mail folder and its contents to another mail folder. Note To view the v1.0 release of this cmdlet, view Move-MgUserMailFolder |
| Move-MgBetaUserMailFolderChildFolder |
Move a mail folder and its contents to another mail folder. Note To view the v1.0 release of this cmdlet, view Move-MgUserMailFolderChildFolder |
| Move-MgBetaUserMailFolderChildFolderMessage |
Move a message to another folder within the specified user's mailbox. This creates a new copy of the message in the destination folder and removes the original message. Note To view the v1.0 release of this cmdlet, view Move-MgUserMailFolderChildFolderMessage |
| Move-MgBetaUserMailFolderMessage |
Move a message to another folder within the specified user's mailbox. This creates a new copy of the message in the destination folder and removes the original message. Note To view the v1.0 release of this cmdlet, view Move-MgUserMailFolderMessage |
| Move-MgBetaUserMessage |
Move a message to another folder within the specified user's mailbox. This creates a new copy of the message in the destination folder and removes the original message. Note To view the v1.0 release of this cmdlet, view Move-MgUserMessage |
| New-MgBetaUserInferenceClassificationOverride |
Create new navigation property to overrides for users Note To view the v1.0 release of this cmdlet, view New-MgUserInferenceClassificationOverride |
| New-MgBetaUserMailFolder |
Create new navigation property to mailFolders for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolder |
| New-MgBetaUserMailFolderChildFolder |
Create new navigation property to childFolders for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolder |
| New-MgBetaUserMailFolderChildFolderMessage |
Create new navigation property to messages for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessage |
| New-MgBetaUserMailFolderChildFolderMessageAttachment |
Create new navigation property to attachments for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageAttachment |
| New-MgBetaUserMailFolderChildFolderMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to an Outlook item. The item can be a message or event. Use this approach to attach a file if the file size is between 3 MB and 150 MB. To attach a file that's smaller than 3 MB, do a POST operation on the attachments navigation property of the Outlook item; see how to do this for a message or for an event. As part of the response, this action returns an upload URL that you can use in subsequent sequential PUT queries. Request headers for each PUT operation let you specify the exact range of bytes to be uploaded. This allows transfer to be resumed, in case the network connection is dropped during upload. The following are the steps to attach a file to an Outlook item using an upload session: See attach large files to Outlook messages or events for an example. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageAttachmentUploadSession |
| New-MgBetaUserMailFolderChildFolderMessageExtension |
Create new navigation property to extensions for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageExtension |
| New-MgBetaUserMailFolderChildFolderMessageForward |
Create a draft to forward an existing message, in either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error.- Update the draft later to add content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, forward a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageForward |
| New-MgBetaUserMailFolderChildFolderMessageMention |
Create new navigation property to mentions for users |
| New-MgBetaUserMailFolderChildFolderMessageReply |
Create a draft to reply to the sender of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If replyTo is specified in the original message, per Internet Message Format (RFC 2822), you should send the reply to the recipients in replyTo, and not the recipients in from.- You can update the draft later to add reply content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply to a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageReply |
| New-MgBetaUserMailFolderChildFolderMessageReplyAll |
Create a draft to reply to the sender and all recipients of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), you should send the reply to the recipients in the replyTo and toRecipients properties, and not the recipients in the from and toRecipients properties.- You can update the draft message later. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply-all to a message in a single action. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageReplyAll |
| New-MgBetaUserMailFolderChildFolderMessageRule |
Create new navigation property to messageRules for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderChildFolderMessageRule |
| New-MgBetaUserMailFolderMessage |
Create new navigation property to messages for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessage |
| New-MgBetaUserMailFolderMessageAttachment |
Create new navigation property to attachments for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageAttachment |
| New-MgBetaUserMailFolderMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to an Outlook item. The item can be a message or event. Use this approach to attach a file if the file size is between 3 MB and 150 MB. To attach a file that's smaller than 3 MB, do a POST operation on the attachments navigation property of the Outlook item; see how to do this for a message or for an event. As part of the response, this action returns an upload URL that you can use in subsequent sequential PUT queries. Request headers for each PUT operation let you specify the exact range of bytes to be uploaded. This allows transfer to be resumed, in case the network connection is dropped during upload. The following are the steps to attach a file to an Outlook item using an upload session: See attach large files to Outlook messages or events for an example. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageAttachmentUploadSession |
| New-MgBetaUserMailFolderMessageExtension |
Create new navigation property to extensions for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageExtension |
| New-MgBetaUserMailFolderMessageForward |
Create a draft to forward an existing message, in either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error.- Update the draft later to add content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, forward a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageForward |
| New-MgBetaUserMailFolderMessageMention |
Create new navigation property to mentions for users |
| New-MgBetaUserMailFolderMessageReply |
Create a draft to reply to the sender of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If replyTo is specified in the original message, per Internet Message Format (RFC 2822), you should send the reply to the recipients in replyTo, and not the recipients in from.- You can update the draft later to add reply content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply to a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageReply |
| New-MgBetaUserMailFolderMessageReplyAll |
Create a draft to reply to the sender and all recipients of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), you should send the reply to the recipients in the replyTo and toRecipients properties, and not the recipients in the from and toRecipients properties.- You can update the draft message later. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply-all to a message in a single action. Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageReplyAll |
| New-MgBetaUserMailFolderMessageRule |
Create new navigation property to messageRules for users Note To view the v1.0 release of this cmdlet, view New-MgUserMailFolderMessageRule |
| New-MgBetaUserMessage |
Create new navigation property to messages for users Note To view the v1.0 release of this cmdlet, view New-MgUserMessage |
| New-MgBetaUserMessageAttachment |
Create new navigation property to attachments for users Note To view the v1.0 release of this cmdlet, view New-MgUserMessageAttachment |
| New-MgBetaUserMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to an Outlook item. The item can be a message or event. Use this approach to attach a file if the file size is between 3 MB and 150 MB. To attach a file that's smaller than 3 MB, do a POST operation on the attachments navigation property of the Outlook item; see how to do this for a message or for an event. As part of the response, this action returns an upload URL that you can use in subsequent sequential PUT queries. Request headers for each PUT operation let you specify the exact range of bytes to be uploaded. This allows transfer to be resumed, in case the network connection is dropped during upload. The following are the steps to attach a file to an Outlook item using an upload session: See attach large files to Outlook messages or events for an example. Note To view the v1.0 release of this cmdlet, view New-MgUserMessageAttachmentUploadSession |
| New-MgBetaUserMessageExtension |
Create new navigation property to extensions for users Note To view the v1.0 release of this cmdlet, view New-MgUserMessageExtension |
| New-MgBetaUserMessageForward |
Create a draft to forward an existing message, in either JSON or MIME format. When using JSON format, you can:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error.- Update the draft later to add content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, forward a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMessageForward |
| New-MgBetaUserMessageMention |
Create new navigation property to mentions for users |
| New-MgBetaUserMessageReply |
Create a draft to reply to the sender of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If replyTo is specified in the original message, per Internet Message Format (RFC 2822), you should send the reply to the recipients in replyTo, and not the recipients in from.- You can update the draft later to add reply content to the body or change other message properties. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply to a message in a single operation. Note To view the v1.0 release of this cmdlet, view New-MgUserMessageReply |
| New-MgBetaUserMessageReplyAll |
Create a draft to reply to the sender and all recipients of a message in either JSON or MIME format. When using JSON format:- Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.- If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), you should send the reply to the recipients in the replyTo and toRecipients properties, and not the recipients in the from and toRecipients properties.- You can update the draft message later. When using MIME format:- Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.- Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply-all to a message in a single action. Note To view the v1.0 release of this cmdlet, view New-MgUserMessageReplyAll |
| Remove-MgBetaUserInferenceClassificationOverride |
Delete navigation property overrides for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserInferenceClassificationOverride |
| Remove-MgBetaUserMailFolder |
Delete navigation property mailFolders for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolder |
| Remove-MgBetaUserMailFolderChildFolder |
Delete navigation property childFolders for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolder |
| Remove-MgBetaUserMailFolderChildFolderMessage |
Delete navigation property messages for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessage |
| Remove-MgBetaUserMailFolderChildFolderMessageAttachment |
Delete navigation property attachments for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessageAttachment |
| Remove-MgBetaUserMailFolderChildFolderMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessageContent |
| Remove-MgBetaUserMailFolderChildFolderMessageExtension |
Delete navigation property extensions for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessageExtension |
| Remove-MgBetaUserMailFolderChildFolderMessageMention |
Delete navigation property mentions for users |
| Remove-MgBetaUserMailFolderChildFolderMessagePermanent |
Permanently delete a message and place it in the Purges folder in the dumpster in the user's mailbox. Email clients such as Outlook or Outlook on the web can't access permanently deleted items. Unless there's a hold set on the mailbox, the items are permanently deleted after a set period of time. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessagePermanent |
| Remove-MgBetaUserMailFolderChildFolderMessageRule |
Delete navigation property messageRules for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderMessageRule |
| Remove-MgBetaUserMailFolderChildFolderPermanent |
Permanently delete a mail folder and remove its items from the user's mailbox. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderChildFolderPermanent |
| Remove-MgBetaUserMailFolderMessage |
Delete navigation property messages for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessage |
| Remove-MgBetaUserMailFolderMessageAttachment |
Delete navigation property attachments for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessageAttachment |
| Remove-MgBetaUserMailFolderMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessageContent |
| Remove-MgBetaUserMailFolderMessageExtension |
Delete navigation property extensions for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessageExtension |
| Remove-MgBetaUserMailFolderMessageMention |
Delete navigation property mentions for users |
| Remove-MgBetaUserMailFolderMessagePermanent |
Permanently delete a message and place it in the Purges folder in the dumpster in the user's mailbox. Email clients such as Outlook or Outlook on the web can't access permanently deleted items. Unless there's a hold set on the mailbox, the items are permanently deleted after a set period of time. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessagePermanent |
| Remove-MgBetaUserMailFolderMessageRule |
Delete navigation property messageRules for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderMessageRule |
| Remove-MgBetaUserMailFolderPermanent |
Permanently delete a mail folder and remove its items from the user's mailbox. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMailFolderPermanent |
| Remove-MgBetaUserMessage |
Delete navigation property messages for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMessage |
| Remove-MgBetaUserMessageAttachment |
Delete navigation property attachments for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMessageAttachment |
| Remove-MgBetaUserMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMessageContent |
| Remove-MgBetaUserMessageExtension |
Delete navigation property extensions for users Note To view the v1.0 release of this cmdlet, view Remove-MgUserMessageExtension |
| Remove-MgBetaUserMessageMention |
Delete navigation property mentions for users |
| Remove-MgBetaUserMessagePermanent |
Permanently delete a message and place it in the Purges folder in the dumpster in the user's mailbox. Email clients such as Outlook or Outlook on the web can't access permanently deleted items. Unless there's a hold set on the mailbox, the items are permanently deleted after a set period of time. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. Note To view the v1.0 release of this cmdlet, view Remove-MgUserMessagePermanent |
| Send-MgBetaUserMailFolderChildFolderMessage |
Send an existing draft message. The draft message can be a new message draft, reply draft, reply-all draft, or a forward draft. This method saves the message in the Sent Items folder. Alternatively, send a new message in a single operation. Note To view the v1.0 release of this cmdlet, view Send-MgUserMailFolderChildFolderMessage |
| Send-MgBetaUserMailFolderMessage |
Send an existing draft message. The draft message can be a new message draft, reply draft, reply-all draft, or a forward draft. This method saves the message in the Sent Items folder. Alternatively, send a new message in a single operation. Note To view the v1.0 release of this cmdlet, view Send-MgUserMailFolderMessage |
| Send-MgBetaUserMessage |
Send an existing draft message. The draft message can be a new message draft, reply draft, reply-all draft, or a forward draft. This method saves the message in the Sent Items folder. Alternatively, send a new message in a single operation. Note To view the v1.0 release of this cmdlet, view Send-MgUserMessage |
| Set-MgBetaUserMailFolderChildFolderMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Set-MgUserMailFolderChildFolderMessageContent |
| Set-MgBetaUserMailFolderMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Set-MgUserMailFolderMessageContent |
| Set-MgBetaUserMessageContent |
The unique identifier for an entity. Read-only. Note To view the v1.0 release of this cmdlet, view Set-MgUserMessageContent |
| Update-MgBetaUserInferenceClassification |
Update the navigation property inferenceClassification in users Note To view the v1.0 release of this cmdlet, view Update-MgUserInferenceClassification |
| Update-MgBetaUserInferenceClassificationOverride |
Update the navigation property overrides in users Note To view the v1.0 release of this cmdlet, view Update-MgUserInferenceClassificationOverride |
| Update-MgBetaUserMailFolder |
Update the navigation property mailFolders in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolder |
| Update-MgBetaUserMailFolderChildFolder |
Update the navigation property childFolders in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderChildFolder |
| Update-MgBetaUserMailFolderChildFolderMessage |
Update the navigation property messages in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderChildFolderMessage |
| Update-MgBetaUserMailFolderChildFolderMessageExtension |
Update the navigation property extensions in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderChildFolderMessageExtension |
| Update-MgBetaUserMailFolderChildFolderMessageReadState |
Invoke action updateAllMessagesReadState |
| Update-MgBetaUserMailFolderChildFolderMessageRule |
Update the navigation property messageRules in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderChildFolderMessageRule |
| Update-MgBetaUserMailFolderMessage |
Update the navigation property messages in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderMessage |
| Update-MgBetaUserMailFolderMessageExtension |
Update the navigation property extensions in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderMessageExtension |
| Update-MgBetaUserMailFolderMessageReadState |
Invoke action updateAllMessagesReadState |
| Update-MgBetaUserMailFolderMessageRule |
Update the navigation property messageRules in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMailFolderMessageRule |
| Update-MgBetaUserMessage |
Update the navigation property messages in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMessage |
| Update-MgBetaUserMessageExtension |
Update the navigation property extensions in users Note To view the v1.0 release of this cmdlet, view Update-MgUserMessageExtension |