Microsoft.Graph.Users.Actions
{{ Fill in the Description }}
Microsoft.Graph.Users.Actions
| Add-MgUserChatMember |
Add multiple members in a single request to a team. The response provides details about which memberships could and couldn't be created. Note To view the beta release of this cmdlet, view Add-MgBetaUserChatMember |
| Add-MgUserDriveListContentTypeCopy |
Add a copy of a [content type][contentType] from a [site][site] to a [list][list]. Note To view the beta release of this cmdlet, view Add-MgBetaUserDriveListContentTypeCopy |
| Add-MgUserDriveListContentTypeCopyFromContentTypeHub |
Add or sync a copy of a published content type from the content type hub to a target site or a list. This method is part of the content type publishing changes to optimize the syncing of published content types to sites and lists, effectively switching from a 'push everywhere' to 'pull as needed' approach. The method allows users to pull content types directly from the content type hub to a site or list. For more information, see contentType: getCompatibleHubContentTypes and the blog post Syntex Product Updates - August 2021. Note To view the beta release of this cmdlet, view Add-MgBetaUserDriveListContentTypeCopyFromContentTypeHub |
| Add-MgUserFollowedSite |
Follow a user's site or multiple sites. Note To view the beta release of this cmdlet, view Add-MgBetaUserFollowedSite |
| Clear-MgUserChatMessageReaction |
Invoke action unsetReaction Note To view the beta release of this cmdlet, view Clear-MgBetaUserChatMessageReaction |
| Clear-MgUserChatMessageReplyReaction |
Invoke action unsetReaction Note To view the beta release of this cmdlet, view Clear-MgBetaUserChatMessageReplyReaction |
| Clear-MgUserManagedDevice |
Wipe a device Note To view the beta release of this cmdlet, view Clear-MgBetaUserManagedDevice |
| Clear-MgUserPresence |
Clear the application's presence session for a user. If it is the user's only presence session, the user's presence will change to Offline/Offline. For details about presences sessions, see presence: setPresence. Note To view the beta release of this cmdlet, view Clear-MgBetaUserPresence |
| Clear-MgUserPresenceUserPreferredPresence |
Clear the preferred availability and activity status for a user. Note To view the beta release of this cmdlet, view Clear-MgBetaUserPresenceUserPreferredPresence |
| Confirm-MgUserMemberGroup |
Check for membership in a specified list of group IDs, and return from that list those groups (identified by IDs) of which the specified user, group, service principal, organizational contact, device, or directory object is a member. This function is transitive. You can check up to a maximum of 20 groups per request. This function supports all groups provisioned in Microsoft Entra ID. Because Microsoft 365 groups cannot contain other groups, membership in a Microsoft 365 group is always direct. Note To view the beta release of this cmdlet, view Confirm-MgBetaUserMemberGroup |
| Confirm-MgUserMemberObject |
Invoke action checkMemberObjects Note To view the beta release of this cmdlet, view Confirm-MgBetaUserMemberObject |
| Copy-MgUserDriveItem |
Asynchronously creates a copy of an [driveItem][item-resource] (including any children), under a new parent item or with a new name. Note To view the beta release of this cmdlet, view Copy-MgBetaUserDriveItem |
| Copy-MgUserDriveListContentTypeToDefaultContentLocation |
Copy a file to a default content location in a [content type][contentType]. The file can then be added as a default file or template via a POST operation. Note To view the beta release of this cmdlet, view Copy-MgBetaUserDriveListContentTypeToDefaultContentLocation |
| Copy-MgUserDriveRoot |
Asynchronously creates a copy of an [driveItem][item-resource] (including any children), under a new parent item or with a new name. Note To view the beta release of this cmdlet, view Copy-MgBetaUserDriveRoot |
| Copy-MgUserMailFolder |
Copy a mailfolder and its contents to another mailfolder. Note To view the beta release of this cmdlet, view Copy-MgBetaUserMailFolder |
| Copy-MgUserMailFolderChildFolder |
Copy a mailfolder and its contents to another mailfolder. Note To view the beta release of this cmdlet, view Copy-MgBetaUserMailFolderChildFolder |
| Copy-MgUserMailFolderChildFolderMessage |
Copy a message to a folder within the user's mailbox. Note To view the beta release of this cmdlet, view Copy-MgBetaUserMailFolderChildFolderMessage |
| Copy-MgUserMailFolderMessage |
Copy a message to a folder within the user's mailbox. Note To view the beta release of this cmdlet, view Copy-MgBetaUserMailFolderMessage |
| Copy-MgUserMessage |
Copy a message to a folder within the user's mailbox. Note To view the beta release of this cmdlet, view Copy-MgBetaUserMessage |
| Copy-MgUserOnenoteNotebook |
For Copy operations, you follow an asynchronous calling pattern: First call the Copy action, and then poll the operation endpoint for the result. Note To view the beta release of this cmdlet, view Copy-MgBetaUserOnenoteNotebook |
| Copy-MgUserOnenotePageToSection |
Copy a page to a specific section. For copy operations, you follow an asynchronous calling pattern: First call the Copy action, and then poll the operation endpoint for the result. Note To view the beta release of this cmdlet, view Copy-MgBetaUserOnenotePageToSection |
| Copy-MgUserOnenoteSectionToNotebook |
For Copy operations, you follow an asynchronous calling pattern: First call the Copy action, and then poll the operation endpoint for the result. Note To view the beta release of this cmdlet, view Copy-MgBetaUserOnenoteSectionToNotebook |
| Copy-MgUserOnenoteSectionToSectionGroup |
For Copy operations, you follow an asynchronous calling pattern: First call the Copy action, and then poll the operation endpoint for the result. Note To view the beta release of this cmdlet, view Copy-MgBetaUserOnenoteSectionToSectionGroup |
| Disable-MgUserAuthenticationPhoneMethodSmsSignIn |
Disable SMS sign-in for an existing mobile phone number registered to a user. The number will no longer be available for SMS sign-in, which can prevent your user from signing in. |
| Disable-MgUserManagedDeviceLostMode |
Disable lost mode Note To view the beta release of this cmdlet, view Disable-MgBetaUserManagedDeviceLostMode |
| Enable-MgUserAuthenticationPhoneMethodSmsSignIn |
Enable SMS sign-in for an existing mobile phone number registered to a user. To be successfully enabled: |
| Export-MgUserPersonalData |
Submit a data policy operation request from a company administrator or an application to export an organizational user's data. This data includes the user's data stored in OneDrive and their activity reports. For more guidance about exporting data while complying with regulations, see Data Subject Requests and the GDPR and CCPA. Note To view the beta release of this cmdlet, view Export-MgBetaUserPersonalData |
| Find-MgUserManagedDevice |
Locate a device Note To view the beta release of this cmdlet, view Find-MgBetaUserManagedDevice |
| Find-MgUserMeetingTime |
Suggest meeting times and locations based on organizer and attendee availability, and time or location constraints specified as parameters. If findMeetingTimes cannot return any meeting suggestions, the response would indicate a reason in the emptySuggestionsReason property.Based on this value, you can better adjust the parameters and call findMeetingTimes again. The algorithm used to suggest meeting times and locations undergoes fine-tuning from time to time. In scenarios like test environments where the input parameters and calendar data remain static, expect that the suggested results may differ over time. Note To view the beta release of this cmdlet, view Find-MgBetaUserMeetingTime |
| Get-MgUserById |
Return the directory objects specified in a list of IDs. Only a subset of user properties are returned by default in v1.0. Some common uses for this function are to: Note To view the beta release of this cmdlet, view Get-MgBetaUserById |
| Get-MgUserCalendarSchedule |
Get the free/busy availability information for a collection of users, distributions lists, or resources (rooms or equipment) for a specified time period. Note To view the beta release of this cmdlet, view Get-MgBetaUserCalendarSchedule |
| Get-MgUserDefaultCalendarSchedule |
Get the free/busy availability information for a collection of users, distributions lists, or resources (rooms or equipment) for a specified time period. Note To view the beta release of this cmdlet, view Get-MgBetaUserDefaultCalendarSchedule |
| Get-MgUserMailTip |
Get the MailTips of one or more recipients as available to the signed-in user. Note that by making a POST call to the getMailTips action, you can request specific types of MailTips tobe returned for more than one recipient at one time. The requested MailTips are returned in a mailTips collection. Note To view the beta release of this cmdlet, view Get-MgBetaUserMailTip |
| Get-MgUserMemberGroup |
Return all the group IDs for the groups that the specified user, group, service principal, organizational contact, device, or directory object is a member of. This function is transitive. This API returns up to 11,000 group IDs. If more than 11,000 results are available, it returns a 400 Bad Request error with the Directory_ResultSizeLimitExceeded error code. As a workaround, use the List group transitive memberOf API. Note To view the beta release of this cmdlet, view Get-MgBetaUserMemberGroup |
| Get-MgUserMemberObject |
Return all IDs for the groups, administrative units, and directory roles that a user, group, service principal, organizational contact, device, or directory object is a member of. This function is transitive. Note: Only users and role-enabled groups can be members of directory roles. Note To view the beta release of this cmdlet, view Get-MgBetaUserMemberObject |
| Get-MgUserOnenoteNotebookFromWebUrl |
Retrieve the properties and relationships of a notebook object by using its URL path. The location can be user notebooks on Microsoft 365, group notebooks, or SharePoint site-hosted team notebooks on Microsoft 365. Note To view the beta release of this cmdlet, view Get-MgBetaUserOnenoteNotebookFromWebUrl |
| Grant-MgUserDriveItemPermission |
Grant users access to a link represented by a [permission][]. Note To view the beta release of this cmdlet, view Grant-MgBetaUserDriveItemPermission |
| Grant-MgUserDriveRootPermission |
Grant users access to a link represented by a [permission][]. Note To view the beta release of this cmdlet, view Grant-MgBetaUserDriveRootPermission |
| Hide-MgUserChatForUser |
Hide a chat for a user. Note To view the beta release of this cmdlet, view Hide-MgBetaUserChatForUser |
| Invoke-MgAcceptUserEvent |
Accept the specified event in a user calendar. Note To view the beta release of this cmdlet, view Invoke-MgBetaAcceptUserEvent |
| Invoke-MgAcceptUserEventInstance |
Accept the specified event in a user calendar. Note To view the beta release of this cmdlet, view Invoke-MgBetaAcceptUserEventInstance |
| Invoke-MgAcceptUserEventInstanceTentatively |
Tentatively accept the specified event in a user calendar. If the event allows proposals for new times, on responding tentative to the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times. Note To view the beta release of this cmdlet, view Invoke-MgBetaAcceptUserEventInstanceTentatively |
| Invoke-MgAcceptUserEventTentatively |
Tentatively accept the specified event in a user calendar. If the event allows proposals for new times, on responding tentative to the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times. Note To view the beta release of this cmdlet, view Invoke-MgBetaAcceptUserEventTentatively |
| Invoke-MgCheckinUserDriveItem |
Check in a checked out driveItem resource, which makes the version of the document available to others. Note To view the beta release of this cmdlet, view Invoke-MgBetaCheckinUserDriveItem |
| Invoke-MgCheckinUserDriveRoot |
Check in a checked out driveItem resource, which makes the version of the document available to others. Note To view the beta release of this cmdlet, view Invoke-MgBetaCheckinUserDriveRoot |
| Invoke-MgCheckoutUserDriveItem |
Check out a driveItem resource to prevent others from editing the document, and prevent your changes from being visible until the documented is checked in. Note To view the beta release of this cmdlet, view Invoke-MgBetaCheckoutUserDriveItem |
| Invoke-MgCheckoutUserDriveRoot |
Check out a driveItem resource to prevent others from editing the document, and prevent your changes from being visible until the documented is checked in. Note To view the beta release of this cmdlet, view Invoke-MgBetaCheckoutUserDriveRoot |
| Invoke-MgCleanUserManagedDeviceWindowsDevice |
Clean Windows device Note To view the beta release of this cmdlet, view Invoke-MgBetaCleanUserManagedDeviceWindowsDevice |
| Invoke-MgCreateOrGetUserOnlineMeeting |
Create an onlineMeeting object with a custom specified external ID. If the external ID already exists, this API will return the onlineMeeting object with that external ID. Note To view the beta release of this cmdlet, view Invoke-MgBetaCreateOrGetUserOnlineMeeting |
| Invoke-MgDeclineUserEvent |
Decline invitation to the specified event in a user calendar. If the event allows proposals for new times, on declining the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times. Note To view the beta release of this cmdlet, view Invoke-MgBetaDeclineUserEvent |
| Invoke-MgDeclineUserEventInstance |
Decline invitation to the specified event in a user calendar. If the event allows proposals for new times, on declining the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times. Note To view the beta release of this cmdlet, view Invoke-MgBetaDeclineUserEventInstance |
| Invoke-MgDismissUserEventInstanceReminder |
Dismiss a reminder that has been triggered for an event in a user calendar. Note To view the beta release of this cmdlet, view Invoke-MgBetaDismissUserEventInstanceReminder |
| Invoke-MgDismissUserEventReminder |
Dismiss a reminder that has been triggered for an event in a user calendar. Note To view the beta release of this cmdlet, view Invoke-MgBetaDismissUserEventReminder |
| Invoke-MgDownUserManagedDeviceShut |
Shut down device Note To view the beta release of this cmdlet, view Invoke-MgBetaDownUserManagedDeviceShut |
| Invoke-MgExtractUserDriveItemSensitivityLabel |
Invoke action extractSensitivityLabels Note To view the beta release of this cmdlet, view Invoke-MgBetaExtractUserDriveItemSensitivityLabel |
| Invoke-MgExtractUserDriveRootSensitivityLabel |
Invoke action extractSensitivityLabels Note To view the beta release of this cmdlet, view Invoke-MgBetaExtractUserDriveRootSensitivityLabel |
| Invoke-MgFollowUserDriveItem |
Follow a driveItem. Note To view the beta release of this cmdlet, view Invoke-MgBetaFollowUserDriveItem |
| Invoke-MgFollowUserDriveRoot |
Follow a driveItem. Note To view the beta release of this cmdlet, view Invoke-MgBetaFollowUserDriveRoot |
| Invoke-MgForwardUserEvent |
This action allows the organizer or attendee of a meeting event to forward themeeting request to a new recipient. If the meeting event is forwarded from an attendee's Microsoft 365 mailbox to another recipient, this actionalso sends a message to notify the organizer of the forwarding, and adds the recipient to the organizer'scopy of the meeting event. This convenience is not available when forwarding from an Outlook.com account. Note To view the beta release of this cmdlet, view Invoke-MgBetaForwardUserEvent |
| Invoke-MgForwardUserEventInstance |
This action allows the organizer or attendee of a meeting event to forward themeeting request to a new recipient. If the meeting event is forwarded from an attendee's Microsoft 365 mailbox to another recipient, this actionalso sends a message to notify the organizer of the forwarding, and adds the recipient to the organizer'scopy of the meeting event. This convenience is not available when forwarding from an Outlook.com account. Note To view the beta release of this cmdlet, view Invoke-MgBetaForwardUserEventInstance |
| Invoke-MgForwardUserMailFolderChildFolderMessage |
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 beta release of this cmdlet, view Invoke-MgBetaForwardUserMailFolderChildFolderMessage |
| Invoke-MgForwardUserMailFolderMessage |
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 beta release of this cmdlet, view Invoke-MgBetaForwardUserMailFolderMessage |
| Invoke-MgForwardUserMessage |
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 beta release of this cmdlet, view Invoke-MgBetaForwardUserMessage |
| Invoke-MgGraphUserChat |
Unhide a chat for a user. Note To view the beta release of this cmdlet, view Invoke-MgBetaGraphUserChat |
| Invoke-MgInviteUserDriveItem |
Sends a sharing invitation for a driveItem.A sharing invitation provides permissions to the recipients and optionally sends them an email with a [sharing link][]. Note To view the beta release of this cmdlet, view Invoke-MgBetaInviteUserDriveItem |
| Invoke-MgInviteUserDriveRoot |
Sends a sharing invitation for a driveItem.A sharing invitation provides permissions to the recipients and optionally sends them an email with a [sharing link][]. Note To view the beta release of this cmdlet, view Invoke-MgBetaInviteUserDriveRoot |
| Invoke-MgLicenseUser |
Reprocess all group-based license assignments for the user. To learn more about group-based licensing, see What is group-based licensing in Microsoft Entra ID. Also see Identify and resolve license assignment problems for a group in Microsoft Entra ID for more details. Note To view the beta release of this cmdlet, view Invoke-MgBetaLicenseUser |
| Invoke-MgLogoutUserManagedDeviceSharedAppleDeviceActiveUser |
Logout shared Apple device active user Note To view the beta release of this cmdlet, view Invoke-MgBetaLogoutUserManagedDeviceSharedAppleDeviceActiveUser |
| Invoke-MgMarkUserChatReadForUser |
Mark a chat as read for a user. Note To view the beta release of this cmdlet, view Invoke-MgBetaMarkUserChatReadForUser |
| Invoke-MgMarkUserChatUnreadForUser |
Mark a chat as unread for a user. Note To view the beta release of this cmdlet, view Invoke-MgBetaMarkUserChatUnreadForUser |
| Invoke-MgPreviewUserDriveItem |
Invoke action preview Note To view the beta release of this cmdlet, view Invoke-MgBetaPreviewUserDriveItem |
| Invoke-MgPreviewUserDriveRoot |
Invoke action preview Note To view the beta release of this cmdlet, view Invoke-MgBetaPreviewUserDriveRoot |
| Invoke-MgReauthorizeUserDriveItemSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the beta release of this cmdlet, view Invoke-MgBetaReauthorizeUserDriveItemSubscription |
| Invoke-MgReauthorizeUserDriveListSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the beta release of this cmdlet, view Invoke-MgBetaReauthorizeUserDriveListSubscription |
| Invoke-MgReauthorizeUserDriveRootSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the beta release of this cmdlet, view Invoke-MgBetaReauthorizeUserDriveRootSubscription |
| Invoke-MgReplyAllUserMailFolderChildFolderMessage |
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 beta release of this cmdlet, view Invoke-MgBetaReplyAllUserMailFolderChildFolderMessage |
| Invoke-MgReplyAllUserMailFolderMessage |
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 beta release of this cmdlet, view Invoke-MgBetaReplyAllUserMailFolderMessage |
| Invoke-MgReplyAllUserMessage |
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 beta release of this cmdlet, view Invoke-MgBetaReplyAllUserMessage |
| Invoke-MgReplyUserMailFolderChildFolderMessage |
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 an existing message and send it later. Note To view the beta release of this cmdlet, view Invoke-MgBetaReplyUserMailFolderChildFolderMessage |
| Invoke-MgReplyUserMailFolderMessage |
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 an existing message and send it later. Note To view the beta release of this cmdlet, view Invoke-MgBetaReplyUserMailFolderMessage |
| Invoke-MgReplyUserMessage |
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 an existing message and send it later. Note To view the beta release of this cmdlet, view Invoke-MgBetaReplyUserMessage |
| Invoke-MgRetireUserManagedDevice |
Retire a device Note To view the beta release of this cmdlet, view Invoke-MgBetaRetireUserManagedDevice |
| Invoke-MgRetryUserServiceProvisioning |
Retry the user service provisioning. Note To view the beta release of this cmdlet, view Invoke-MgBetaRetryUserServiceProvisioning |
| Invoke-MgScanUserManagedDeviceWindowsDefender |
Not yet documented Note To view the beta release of this cmdlet, view Invoke-MgBetaScanUserManagedDeviceWindowsDefender |
| Invoke-MgSnoozeUserEventInstanceReminder |
Postpone a reminder for an event in a user calendar until a new time. Note To view the beta release of this cmdlet, view Invoke-MgBetaSnoozeUserEventInstanceReminder |
| Invoke-MgSnoozeUserEventReminder |
Postpone a reminder for an event in a user calendar until a new time. Note To view the beta release of this cmdlet, view Invoke-MgBetaSnoozeUserEventReminder |
| Invoke-MgSoftUserChatMessageDelete |
Delete a single chatMessage or a chat message reply in a channel or a chat. Note To view the beta release of this cmdlet, view Invoke-MgBetaSoftUserChatMessageDelete |
| Invoke-MgSoftUserChatMessageReplyDelete |
Delete a single chatMessage or a chat message reply in a channel or a chat. Note To view the beta release of this cmdlet, view Invoke-MgBetaSoftUserChatMessageReplyDelete |
| Invoke-MgTranslateUserExchangeId |
Translate identifiers of Outlook-related resources between formats. Note To view the beta release of this cmdlet, view Invoke-MgBetaTranslateUserExchangeId |
| Invoke-MgUnfollowUserDriveItem |
Unfollow a driveItem. Note To view the beta release of this cmdlet, view Invoke-MgBetaUnfollowUserDriveItem |
| Invoke-MgUnfollowUserDriveRoot |
Unfollow a driveItem. Note To view the beta release of this cmdlet, view Invoke-MgBetaUnfollowUserDriveRoot |
| Join-MgUserDriveListContentTypeWithHubSite |
Associate a published [content type][contentType] present in a content type hub with a list of hub sites. Note To view the beta release of this cmdlet, view Join-MgBetaUserDriveListContentTypeWithHubSite |
| Lock-MgUserManagedDeviceRemote |
Remote lock Note To view the beta release of this cmdlet, view Lock-MgBetaUserManagedDeviceRemote |
| Move-MgUserMailFolder |
Move a mailfolder and its contents to another mailfolder. Note To view the beta release of this cmdlet, view Move-MgBetaUserMailFolder |
| Move-MgUserMailFolderChildFolder |
Move a mailfolder and its contents to another mailfolder. Note To view the beta release of this cmdlet, view Move-MgBetaUserMailFolderChildFolder |
| Move-MgUserMailFolderChildFolderMessage |
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 beta release of this cmdlet, view Move-MgBetaUserMailFolderChildFolderMessage |
| Move-MgUserMailFolderMessage |
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 beta release of this cmdlet, view Move-MgBetaUserMailFolderMessage |
| Move-MgUserMessage |
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 beta release of this cmdlet, view Move-MgBetaUserMessage |
| New-MgUserDriveItemLink |
You can use createLink action to share a DriveItem via a sharing link. The createLink action will create a new sharing link if the specified link type doesn't already exist for the calling application.If a sharing link of the specified type already exists for the app, the existing sharing link will be returned. DriveItem resources inherit sharing permissions from their ancestors. Note To view the beta release of this cmdlet, view New-MgBetaUserDriveItemLink |
| New-MgUserDriveItemListItemLink |
Invoke action createLink Note To view the beta release of this cmdlet, view New-MgBetaUserDriveItemListItemLink |
| New-MgUserDriveItemUploadSession |
Invoke action createUploadSession Note To view the beta release of this cmdlet, view New-MgBetaUserDriveItemUploadSession |
| New-MgUserDriveListItemLink |
Invoke action createLink Note To view the beta release of this cmdlet, view New-MgBetaUserDriveListItemLink |
| New-MgUserDriveRootLink |
You can use createLink action to share a DriveItem via a sharing link. The createLink action will create a new sharing link if the specified link type doesn't already exist for the calling application.If a sharing link of the specified type already exists for the app, the existing sharing link will be returned. DriveItem resources inherit sharing permissions from their ancestors. Note To view the beta release of this cmdlet, view New-MgBetaUserDriveRootLink |
| New-MgUserDriveRootListItemLink |
Invoke action createLink Note To view the beta release of this cmdlet, view New-MgBetaUserDriveRootListItemLink |
| New-MgUserDriveRootUploadSession |
Invoke action createUploadSession Note To view the beta release of this cmdlet, view New-MgBetaUserDriveRootUploadSession |
| New-MgUserEventAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to the specified 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 beta release of this cmdlet, view New-MgBetaUserEventAttachmentUploadSession |
| New-MgUserEventInstanceAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to the specified 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 beta release of this cmdlet, view New-MgBetaUserEventInstanceAttachmentUploadSession |
| New-MgUserMailFolderChildFolderMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to the specified 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 beta release of this cmdlet, view New-MgBetaUserMailFolderChildFolderMessageAttachmentUploadSession |
| New-MgUserMailFolderChildFolderMessageForward |
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 beta release of this cmdlet, view New-MgBetaUserMailFolderChildFolderMessageForward |
| New-MgUserMailFolderChildFolderMessageReply |
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 beta release of this cmdlet, view New-MgBetaUserMailFolderChildFolderMessageReply |
| New-MgUserMailFolderChildFolderMessageReplyAll |
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 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-all to a message in a single action. Note To view the beta release of this cmdlet, view New-MgBetaUserMailFolderChildFolderMessageReplyAll |
| New-MgUserMailFolderMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to the specified 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 beta release of this cmdlet, view New-MgBetaUserMailFolderMessageAttachmentUploadSession |
| New-MgUserMailFolderMessageForward |
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 beta release of this cmdlet, view New-MgBetaUserMailFolderMessageForward |
| New-MgUserMailFolderMessageReply |
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 beta release of this cmdlet, view New-MgBetaUserMailFolderMessageReply |
| New-MgUserMailFolderMessageReplyAll |
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 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-all to a message in a single action. Note To view the beta release of this cmdlet, view New-MgBetaUserMailFolderMessageReplyAll |
| New-MgUserManagedDeviceLogCollectionResponseDownloadUrl |
Invoke action createDownloadUrl Note To view the beta release of this cmdlet, view New-MgBetaUserManagedDeviceLogCollectionResponseDownloadUrl |
| New-MgUserManagedDeviceWindowsDefenderUpdateSignature |
Not yet documented Note To view the beta release of this cmdlet, view New-MgBetaUserManagedDeviceWindowsDefenderUpdateSignature |
| New-MgUserMessageAttachmentUploadSession |
Create an upload session that allows an app to iteratively upload ranges of a file, so as to attach the file to the specified 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 beta release of this cmdlet, view New-MgBetaUserMessageAttachmentUploadSession |
| New-MgUserMessageForward |
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 beta release of this cmdlet, view New-MgBetaUserMessageForward |
| New-MgUserMessageReply |
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 beta release of this cmdlet, view New-MgBetaUserMessageReply |
| New-MgUserMessageReplyAll |
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 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-all to a message in a single action. Note To view the beta release of this cmdlet, view New-MgBetaUserMessageReplyAll |
| New-MgUserTodoListTaskAttachmentUploadSession |
Create an upload session to iteratively upload ranges of a file as an attachment to a todoTask. As part of the response, this action returns an upload URL that you can use in subsequent sequential PUT queries. The request headers for each PUT operation let you specify the exact range of bytes to be uploaded. This allows the transfer to be resumed, in case the network connection is dropped during the upload. The following are the steps to attach a file to a Microsoft To Do task using an upload session: For an example that describes the end-to-end attachment process, see attach files to a To Do task. Note To view the beta release of this cmdlet, view New-MgBetaUserTodoListTaskAttachmentUploadSession |
| Publish-MgUserDriveListContentType |
Publishes a [contentType][] present in the content type hub site. Note To view the beta release of this cmdlet, view Publish-MgBetaUserDriveListContentType |
| Remove-MgAllUserDeviceFromManagement |
Retire all devices from management for this user Note To view the beta release of this cmdlet, view Remove-MgBetaAllUserDeviceFromManagement |
| Remove-MgUserDriveItemPermanent |
Invoke action permanentDelete Note To view the beta release of this cmdlet, view Remove-MgBetaUserDriveItemPermanent |
| Remove-MgUserDriveRootPermanent |
Invoke action permanentDelete Note To view the beta release of this cmdlet, view Remove-MgBetaUserDriveRootPermanent |
| Remove-MgUserFollowedSite |
Unfollow a user's site or multiple sites. Note To view the beta release of this cmdlet, view Remove-MgBetaUserFollowedSite |
| Remove-MgUserManagedDeviceUserFromSharedAppleDevice |
Delete user from shared Apple device Note To view the beta release of this cmdlet, view Remove-MgBetaUserManagedDeviceUserFromSharedAppleDevice |
| Request-MgUserManagedDeviceRemoteAssistance |
Request remote assistance Note To view the beta release of this cmdlet, view Request-MgBetaUserManagedDeviceRemoteAssistance |
| Reset-MgUserAuthenticationMethodPassword |
Reset a user's password, represented by a password authentication method object. This can only be done by an administrator with appropriate permissions and can't be performed on a user's own account. This flow writes the new password to Microsoft Entra ID and pushes it to on-premises Active Directory if configured using password writeback. The admin can either provide a new password or have the system generate one. The user is prompted to change their password on their next sign in. This reset is a long-running operation and returns a Location header with a link where the caller can periodically check for the status of the reset operation. Note To view the beta release of this cmdlet, view Reset-MgBetaUserAuthenticationMethodPassword |
| Reset-MgUserManagedDevicePasscode |
Reset passcode Note To view the beta release of this cmdlet, view Reset-MgBetaUserManagedDevicePasscode |
| Restart-MgUserManagedDeviceNow |
Reboot device Note To view the beta release of this cmdlet, view Restart-MgBetaUserManagedDeviceNow |
| Restore-MgUserDriveItem |
Restore a driveItem that has been deleted and is currently in the recycle bin. NOTE: This functionality is currently only available for OneDrive Personal. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveItem |
| Restore-MgUserDriveItemListItemDocumentSetVersion |
Restore a document set version. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveItemListItemDocumentSetVersion |
| Restore-MgUserDriveItemListItemVersion |
Restore a previous version of a ListItem to be the current version. This will create a new version with the contents of the previous version, but preserves all existing versions of the item. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveItemListItemVersion |
| Restore-MgUserDriveItemVersion |
Restore a previous version of a DriveItem to be the current version. This will create a new version with the contents of the previous version, but preserves all existing versions of the file. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveItemVersion |
| Restore-MgUserDriveListItemDocumentSetVersion |
Restore a document set version. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveListItemDocumentSetVersion |
| Restore-MgUserDriveListItemVersion |
Restore a previous version of a ListItem to be the current version. This will create a new version with the contents of the previous version, but preserves all existing versions of the item. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveListItemVersion |
| Restore-MgUserDriveRoot |
Restore a driveItem that has been deleted and is currently in the recycle bin. NOTE: This functionality is currently only available for OneDrive Personal. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveRoot |
| Restore-MgUserDriveRootListItemDocumentSetVersion |
Restore a document set version. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveRootListItemDocumentSetVersion |
| Restore-MgUserDriveRootListItemVersion |
Restore a previous version of a ListItem to be the current version. This will create a new version with the contents of the previous version, but preserves all existing versions of the item. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveRootListItemVersion |
| Restore-MgUserDriveRootVersion |
Restore a previous version of a DriveItem to be the current version. This will create a new version with the contents of the previous version, but preserves all existing versions of the file. Note To view the beta release of this cmdlet, view Restore-MgBetaUserDriveRootVersion |
| Restore-MgUserManagedDevicePasscode |
Recover passcode Note To view the beta release of this cmdlet, view Restore-MgBetaUserManagedDevicePasscode |
| Revoke-MgUserSignInSession |
Invalidates all the refresh tokens issued to applications for a user (as well as session cookies in a user's browser), by resetting the signInSessionsValidFromDateTime user property to the current date-time. Typically, this operation is performed (by the user or an administrator) if the user has a lost or stolen device. This operation prevents access to the organization's data through applications on the device by requiring the user to sign in again to all applications that they have previously consented to, independent of device. Note To view the beta release of this cmdlet, view Revoke-MgBetaUserSignInSession |
| Send-MgUserChatActivityNotification |
Send an activity feed notification in scope of a chat. For more information about sending notifications and the requirements for doing so, see sending Teams activity notifications. Note To view the beta release of this cmdlet, view Send-MgBetaUserChatActivityNotification |
| Send-MgUserMail |
Send the message specified in the request body using either JSON or MIME format. When using JSON format, you can include a file attachment in the same sendMail action call. When using MIME format: This method saves the message in the Sent Items folder. Alternatively, create a draft message to send later. To learn more about the steps involved in the backend before a mail is delivered to recipients, see here. Note To view the beta release of this cmdlet, view Send-MgBetaUserMail |
| Send-MgUserMailFolderChildFolderMessage |
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 beta release of this cmdlet, view Send-MgBetaUserMailFolderChildFolderMessage |
| Send-MgUserMailFolderMessage |
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 beta release of this cmdlet, view Send-MgBetaUserMailFolderMessage |
| Send-MgUserMessage |
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 beta release of this cmdlet, view Send-MgBetaUserMessage |
| Send-MgUserOnlineMeetingVirtualAppointmentReminderSm |
Send an SMS reminder to external attendees for a Teams virtual appointment. This feature requires Teams premium and attendees must have a valid United States phone number to receive SMS notifications. Note To view the beta release of this cmdlet, view Send-MgBetaUserOnlineMeetingVirtualAppointmentReminderSm |
| Send-MgUserOnlineMeetingVirtualAppointmentSm |
Send an SMS notification to external attendees when a Teams virtual appointment is confirmed, rescheduled, or canceled. This feature requires Teams premium. Attendees must have a valid United States phone number to receive these SMS notifications. Note To view the beta release of this cmdlet, view Send-MgBetaUserOnlineMeetingVirtualAppointmentSm |
| Send-MgUserTeamworkActivityNotification |
Send an activity feed notification to a user. For more information, see sending Teams activity notifications. Note To view the beta release of this cmdlet, view Send-MgBetaUserTeamworkActivityNotification |
| Set-MgUserChatMessageReaction |
Invoke action setReaction Note To view the beta release of this cmdlet, view Set-MgBetaUserChatMessageReaction |
| Set-MgUserChatMessageReplyReaction |
Invoke action setReaction Note To view the beta release of this cmdlet, view Set-MgBetaUserChatMessageReplyReaction |
| Set-MgUserDriveItemSensitivityLabel |
Invoke action assignSensitivityLabel Note To view the beta release of this cmdlet, view Set-MgBetaUserDriveItemSensitivityLabel |
| Set-MgUserDriveRootSensitivityLabel |
Invoke action assignSensitivityLabel Note To view the beta release of this cmdlet, view Set-MgBetaUserDriveRootSensitivityLabel |
| Set-MgUserLicense |
Add or remove subscriptions for the user. You can also enable and disable specific plans associated with a subscription. Note To view the beta release of this cmdlet, view Set-MgBetaUserLicense |
| Set-MgUserPresence |
Set the state of a user's presence session as an application. Note To view the beta release of this cmdlet, view Set-MgBetaUserPresence |
| Set-MgUserPresenceStatusMessage |
Set a presence status message for a user. An optional expiration date and time can be supplied. Note To view the beta release of this cmdlet, view Set-MgBetaUserPresenceStatusMessage |
| Set-MgUserPresenceUserPreferredPresence |
Set the preferred availability and activity status for a user. If the preferred presence of a user is set, the user's presence shows as the preferred status. Preferred presence takes effect only when at least one presence session exists for the user. Otherwise, the user's presence shows as Offline. A presence session is created as a result of a successful setPresence operation, or if the user is signed in on a Microsoft Teams client. For more details, see presence sessions and time-out and expiration. Note To view the beta release of this cmdlet, view Set-MgBetaUserPresenceUserPreferredPresence |
| Skip-MgUserManagedDeviceActivationLock |
Bypass activation lock Note To view the beta release of this cmdlet, view Skip-MgBetaUserManagedDeviceActivationLock |
| Stop-MgUserEvent |
This action allows the organizer of a meeting to send a cancellation message and cancel the event. The action moves the event to the Deleted Items folder. The organizer can also cancel an occurrence of a recurring meeting by providing the occurrence event ID. An attendee calling this action gets an error (HTTP 400 Bad Request), with the followingerror message: 'Your request can't be completed. You need to be an organizer to cancel a meeting.' This action differs from Delete in that Cancel is available to only the organizer, and letsthe organizer send a custom message to the attendees about the cancellation. Note To view the beta release of this cmdlet, view Stop-MgBetaUserEvent |
| Stop-MgUserEventInstance |
This action allows the organizer of a meeting to send a cancellation message and cancel the event. The action moves the event to the Deleted Items folder. The organizer can also cancel an occurrence of a recurring meeting by providing the occurrence event ID. An attendee calling this action gets an error (HTTP 400 Bad Request), with the followingerror message: 'Your request can't be completed. You need to be an organizer to cancel a meeting.' This action differs from Delete in that Cancel is available to only the organizer, and letsthe organizer send a custom message to the attendees about the cancellation. Note To view the beta release of this cmdlet, view Stop-MgBetaUserEventInstance |
| Sync-MgUserManagedDevice |
Not yet documented Note To view the beta release of this cmdlet, view Sync-MgBetaUserManagedDevice |
| Test-MgUserDriveItemPermission |
Invoke action validatePermission Note To view the beta release of this cmdlet, view Test-MgBetaUserDriveItemPermission |
| Test-MgUserDriveRootPermission |
Invoke action validatePermission Note To view the beta release of this cmdlet, view Test-MgBetaUserDriveRootPermission |
| Test-MgUserProperty |
Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. To validate the properties of an existing group, use the group: validateProperties function. The following policy validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate that the mail nickname is unique This API only returns the first validation failure that is encountered. If the properties fail multiple validations, only the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you are only validating the prefix and suffix naming policy. To learn more about configuring naming policies, see Configure naming policy. Note To view the beta release of this cmdlet, view Test-MgBetaUserProperty |
| Undo-MgUserChatMessageReplySoftDelete |
Undo soft deletion of a single chatMessage or a chat message reply in a channel or a chat. Note To view the beta release of this cmdlet, view Undo-MgBetaUserChatMessageReplySoftDelete |
| Undo-MgUserChatMessageSoftDelete |
Undo soft deletion of a single chatMessage or a chat message reply in a channel or a chat. Note To view the beta release of this cmdlet, view Undo-MgBetaUserChatMessageSoftDelete |
| Unpublish-MgUserDriveListContentType |
Unpublish a [contentType][] from a content type hub site. Note To view the beta release of this cmdlet, view Unpublish-MgBetaUserDriveListContentType |
| Update-MgUserChatInstalledApp |
Upgrade an app installation within a chat. Note To view the beta release of this cmdlet, view Update-MgBetaUserChatInstalledApp |
| Update-MgUserManagedDeviceWindowsDeviceAccount |
Not yet documented Note To view the beta release of this cmdlet, view Update-MgBetaUserManagedDeviceWindowsDeviceAccount |
| Update-MgUserOnenotePageContent |
Invoke action onenotePatchContent Note To view the beta release of this cmdlet, view Update-MgBetaUserOnenotePageContent |
| Update-MgUserPassword |
Enable the user to update their password. Any user can update their password without belonging to any administrator role. Note To view the beta release of this cmdlet, view Update-MgBetaUserPassword |