Microsoft.Graph.Beta.Users.Actions
Microsoft Graph PowerShell Cmdlets
Microsoft.Graph.Beta.Users.Actions
Add-MgBetaUserChatMember |
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 v1.0 release of this cmdlet, view Add-MgUserChatMember |
Add-MgBetaUserDriveListContentTypeCopy |
Invoke action addCopy Note To view the v1.0 release of this cmdlet, view Add-MgUserDriveListContentTypeCopy |
Add-MgBetaUserDriveListContentTypeCopyFromContentTypeHub |
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 getCompatibleHubContentTypes and the blog post Syntex Product Updates - August 2021. Note To view the v1.0 release of this cmdlet, view Add-MgUserDriveListContentTypeCopyFromContentTypeHub |
Add-MgBetaUserFollowedSite |
Follow a user's site or multiple sites. Note To view the v1.0 release of this cmdlet, view Add-MgUserFollowedSite |
Add-MgBetaUserPendingAccessReviewInstanceDecision |
Apply review decisions on an accessReviewInstance if the decisions were not applied automatically because the autoApplyDecisionsEnabled property is false in the review's accessReviewScheduleSettings. The status of the accessReviewInstance must be Completed to call this method. |
Clear-MgBetaUserAndBlockManagedApp |
Blocks the managed app user from app check-in. |
Clear-MgBetaUserChatMessageReaction |
Invoke action unsetReaction Note To view the v1.0 release of this cmdlet, view Clear-MgUserChatMessageReaction |
Clear-MgBetaUserChatMessageReplyReaction |
Invoke action unsetReaction Note To view the v1.0 release of this cmdlet, view Clear-MgUserChatMessageReplyReaction |
Clear-MgBetaUserManagedAppRegistrationByAzureAdDeviceId |
Issues a wipe operation on an app registration with specified aad device Id. |
Clear-MgBetaUserManagedAppRegistrationByDeviceTag |
Issues a wipe operation on an app registration with specified device tag. |
Clear-MgBetaUserManagedDevice |
Wipe a device Note To view the v1.0 release of this cmdlet, view Clear-MgUserManagedDevice |
Clear-MgBetaUserPresence |
Clear a presence session of an application for a user. If it is the user's only presence session, a successful clearPresence changes the user's presence to Offline/Offline. Read more about presence sessions and their time-out and expiration. Note To view the v1.0 release of this cmdlet, view Clear-MgUserPresence |
Clear-MgBetaUserPresenceUserPreferredPresence |
Clear the preferred availability and activity status for a user. Note To view the v1.0 release of this cmdlet, view Clear-MgUserPresenceUserPreferredPresence |
Complete-MgBetaUserChatMigration |
Invoke action completeMigration |
Complete-MgBetaUserOutlookTask |
Complete an Outlook task which sets the completedDateTime property to the current date, and the status property to completed. If you are completing a task in a recurring series, in the response, the task collection will contain the completed task in the series, and the next task in the series. The completedDateTime property represents the date when the task is finished. The time portion of completedDateTime is set to midnight UTC by default. By default, this operation (and the POST, GET, and PATCH task operations) returns date-related properties in UTC. You can use the Prefer: outlook.timezone header to have all the date-related properties in the response represented in a time zone different than UTC. |
Complete-MgBetaUserOutlookTaskFolderTask |
Complete an Outlook task which sets the completedDateTime property to the current date, and the status property to completed. If you are completing a task in a recurring series, in the response, the task collection will contain the completed task in the series, and the next task in the series. The completedDateTime property represents the date when the task is finished. The time portion of completedDateTime is set to midnight UTC by default. By default, this operation (and the POST, GET, and PATCH task operations) returns date-related properties in UTC. You can use the Prefer: outlook.timezone header to have all the date-related properties in the response represented in a time zone different than UTC. |
Complete-MgBetaUserOutlookTaskGroupTaskFolderTask |
Complete an Outlook task which sets the completedDateTime property to the current date, and the status property to completed. If you are completing a task in a recurring series, in the response, the task collection will contain the completed task in the series, and the next task in the series. The completedDateTime property represents the date when the task is finished. The time portion of completedDateTime is set to midnight UTC by default. By default, this operation (and the POST, GET, and PATCH task operations) returns date-related properties in UTC. You can use the Prefer: outlook.timezone header to have all the date-related properties in the response represented in a time zone different than UTC. |
Confirm-MgBetaUserInformationProtectionSignature |
Invoke action verifySignature |
Confirm-MgBetaUserMemberGroup |
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 v1.0 release of this cmdlet, view Confirm-MgUserMemberGroup |
Confirm-MgBetaUserMemberObject |
Invoke action checkMemberObjects Note To view the v1.0 release of this cmdlet, view Confirm-MgUserMemberObject |
Convert-MgBetaUserExternalToInternalMemberUser |
Convert an externally authenticated user into an internal user. The user is able to sign into the host tenant as an internal user and access resources as a member. For more information about this conversion, see Convert external users to internal users. |
Copy-MgBetaUserDriveItem |
Asynchronously create a copy of a driveItem (including any children) under a new parent item or with a new name. After the request is acknowledged, it enters a queue. The actual copying, including any subitems, occurs at an undetermined time. Progress is reported until the operation is completed by monitoring the progress. Note To view the v1.0 release of this cmdlet, view Copy-MgUserDriveItem |
Copy-MgBetaUserDriveListContentTypeToDefaultContentLocation |
Invoke action copyToDefaultContentLocation Note To view the v1.0 release of this cmdlet, view Copy-MgUserDriveListContentTypeToDefaultContentLocation |
Copy-MgBetaUserDriveRoot |
Asynchronously create a copy of a driveItem (including any children) under a new parent item or with a new name. After the request is acknowledged, it enters a queue. The actual copying, including any subitems, occurs at an undetermined time. Progress is reported until the operation is completed by monitoring the progress. Note To view the v1.0 release of this cmdlet, view Copy-MgUserDriveRoot |
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 |
Copy-MgBetaUserOnenoteNotebook |
Copies a notebook to the Notebooks folder in the destination Documents library. The folder is created if it doesn't exist. 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 v1.0 release of this cmdlet, view Copy-MgUserOnenoteNotebook |
Copy-MgBetaUserOnenotePageToSection |
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 v1.0 release of this cmdlet, view Copy-MgUserOnenotePageToSection |
Copy-MgBetaUserOnenoteSectionToNotebook |
Copies a section to a specific notebook. 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 v1.0 release of this cmdlet, view Copy-MgUserOnenoteSectionToNotebook |
Copy-MgBetaUserOnenoteSectionToSectionGroup |
Copies a section to a specific section group. 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 v1.0 release of this cmdlet, view Copy-MgUserOnenoteSectionToSectionGroup |
Disable-MgBetaUserAuthenticationMethodSmsSignIn |
Invoke action disableSmsSignIn |
Disable-MgBetaUserManagedDevice |
Invoke action disable |
Disable-MgBetaUserManagedDeviceLostMode |
Disable lost mode Note To view the v1.0 release of this cmdlet, view Disable-MgUserManagedDeviceLostMode |
Enable-MgBetaUserAuthenticationMethodSmsSignIn |
Invoke action enableSmsSignIn |
Enable-MgBetaUserManagedDeviceLostMode |
Enable lost mode |
Export-MgBetaUserPersonalData |
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 information about exporting data while complying with regulations, see Data Subject Requests and the GDPR and CCPA. Note To view the v1.0 release of this cmdlet, view Export-MgUserPersonalData |
Find-MgBetaUserManagedDevice |
Locate a device Note To view the v1.0 release of this cmdlet, view Find-MgUserManagedDevice |
Find-MgBetaUserMeetingTime |
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 v1.0 release of this cmdlet, view Find-MgUserMeetingTime |
Get-MgBetaUserById |
Return the directory objects specified in a list of IDs. Some common uses for this function are to: Note To view the v1.0 release of this cmdlet, view Get-MgUserById |
Get-MgBetaUserCalendarSchedule |
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 v1.0 release of this cmdlet, view Get-MgUserCalendarSchedule |
Get-MgBetaUserDefaultCalendarSchedule |
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 v1.0 release of this cmdlet, view Get-MgUserDefaultCalendarSchedule |
Get-MgBetaUserMailTip |
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 v1.0 release of this cmdlet, view Get-MgUserMailTip |
Get-MgBetaUserMemberGroup |
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 DirectoryResultSizeLimitExceeded error code. If you get the DirectoryResultSizeLimitExceeded error code, use the List group transitive memberOf API instead. Note To view the v1.0 release of this cmdlet, view Get-MgUserMemberGroup |
Get-MgBetaUserMemberObject |
Invoke action getMemberObjects Note To view the v1.0 release of this cmdlet, view Get-MgUserMemberObject |
Get-MgBetaUserOnenoteNotebookFromWebUrl |
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 v1.0 release of this cmdlet, view Get-MgUserOnenoteNotebookFromWebUrl |
Get-MgBetaUserOwnedObjectByType |
Retrieve a list of recently deleted application and group objects owned by the specified user. This API returns up to 1,000 deleted objects owned by the user, sorted by ID, and doesn't support pagination. |
Get-MgBetaUserPasswordSingleSignOnCredential |
Get the list of password-based single sign-on credentials for a given user. This API returns the encrypted passwords as null or empty strings. |
Grant-MgBetaUserDriveItemListItemPermission |
Grant users access to a link represented by a permission. |
Grant-MgBetaUserDriveItemPermission |
Grant users access to a link represented by a permission. Note To view the v1.0 release of this cmdlet, view Grant-MgUserDriveItemPermission |
Grant-MgBetaUserDriveListItemPermission |
Grant users access to a link represented by a permission. |
Grant-MgBetaUserDriveListPermission |
Grant users access to a link represented by a permission. |
Grant-MgBetaUserDriveRootListItemPermission |
Grant users access to a link represented by a permission. |
Grant-MgBetaUserDriveRootPermission |
Grant users access to a link represented by a permission. Note To view the v1.0 release of this cmdlet, view Grant-MgUserDriveRootPermission |
Hide-MgBetaUserChatForUser |
Hide a chat for a user. Note To view the v1.0 release of this cmdlet, view Hide-MgUserChatForUser |
Initialize-MgBetaUserManagedDeviceEsim |
Activate eSIM on the device. |
Invoke-MgBetaAcceptUserEvent |
Accept the specified event in a user calendar. Note To view the v1.0 release of this cmdlet, view Invoke-MgAcceptUserEvent |
Invoke-MgBetaAcceptUserEventInstance |
Accept the specified event in a user calendar. Note To view the v1.0 release of this cmdlet, view Invoke-MgAcceptUserEventInstance |
Invoke-MgBetaAcceptUserEventInstanceTentatively |
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 v1.0 release of this cmdlet, view Invoke-MgAcceptUserEventInstanceTentatively |
Invoke-MgBetaAcceptUserEventTentatively |
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 v1.0 release of this cmdlet, view Invoke-MgAcceptUserEventTentatively |
Invoke-MgBetaAcceptUserPendingAccessReviewInstanceRecommendation |
Allows the acceptance of recommendations on all accessReviewInstanceDecisionItem objects that haven't been reviewed for an accessReviewInstance object for which the calling user is a reviewer. Recommendations are generated if recommendationsEnabled is true on the accessReviewScheduleDefinition object. If there isn't a recommendation on an accessReviewInstanceDecisionItem object no decision will be recorded. |
Invoke-MgBetaArchiveUserPlannerPlan |
Archive a plannerPlan object. Archiving a plan, also archives the plannerTasks and plannerBuckets in the plan. An archived entity is read-only. Archived entities cannot be updated. An archived plan can be unarchived. All archived entities can be deleted. Archived tasks are not included in the response for list of tasks assigned to a user. |
Invoke-MgBetaBatchUserPendingAccessReviewInstanceRecordDecision |
Enables reviewers to review all accessReviewInstanceDecisionItem objects in batches by using principalId, resourceId, or neither. |
Invoke-MgBetaBufferUserInformationProtectionDecrypt |
Invoke action decryptBuffer |
Invoke-MgBetaBufferUserInformationProtectionEncrypt |
Invoke action encryptBuffer |
Invoke-MgBetaBulkReprovisionUserManagedDeviceCloudPc |
Bulk reprovision a set of Cloud PC devices with Intune managed device IDs. |
Invoke-MgBetaBulkRestoreUserManagedDeviceCloudPc |
Restore multiple Cloud PC devices with a single request that includes the IDs of Intune managed devices and a restore point date and time. |
Invoke-MgBetaBulkUserCloudPcResize |
Perform a bulk resize action to resize a group of cloudPCs that successfully pass validation. If any devices can't be resized, those devices indicate 'resize failed'. The remaining devices are provisioned for the resize process. |
Invoke-MgBetaBulkUserManagedDeviceSetCloudPcReviewStatus |
Set the review status of multiple Cloud PC devices with a single request that includes the IDs of Intune managed devices. |
Invoke-MgBetaCheckinUserDriveItem |
Check in a checked out driveItem resource, which makes the version of the document available to others. Note To view the v1.0 release of this cmdlet, view Invoke-MgCheckinUserDriveItem |
Invoke-MgBetaCheckinUserDriveRoot |
Check in a checked out driveItem resource, which makes the version of the document available to others. Note To view the v1.0 release of this cmdlet, view Invoke-MgCheckinUserDriveRoot |
Invoke-MgBetaCheckoutUserDriveItem |
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 v1.0 release of this cmdlet, view Invoke-MgCheckoutUserDriveItem |
Invoke-MgBetaCheckoutUserDriveRoot |
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 v1.0 release of this cmdlet, view Invoke-MgCheckoutUserDriveRoot |
Invoke-MgBetaCleanUserManagedDeviceWindowsDevice |
Clean Windows device Note To view the v1.0 release of this cmdlet, view Invoke-MgCleanUserManagedDeviceWindowsDevice |
Invoke-MgBetaCreateOrGetUserOnlineMeeting |
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 v1.0 release of this cmdlet, view Invoke-MgCreateOrGetUserOnlineMeeting |
Invoke-MgBetaDeclineUserEvent |
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 v1.0 release of this cmdlet, view Invoke-MgDeclineUserEvent |
Invoke-MgBetaDeclineUserEventInstance |
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 v1.0 release of this cmdlet, view Invoke-MgDeclineUserEventInstance |
Invoke-MgBetaDeprovisionUserManagedDevice |
Invoke action deprovision |
Invoke-MgBetaDismissUserEventInstanceReminder |
Dismiss a reminder that has been triggered for an event in a user calendar. Note To view the v1.0 release of this cmdlet, view Invoke-MgDismissUserEventInstanceReminder |
Invoke-MgBetaDismissUserEventReminder |
Dismiss a reminder that has been triggered for an event in a user calendar. Note To view the v1.0 release of this cmdlet, view Invoke-MgDismissUserEventReminder |
Invoke-MgBetaDownloadUserManagedDeviceAppDiagnostic |
Invoke action downloadAppDiagnostics |
Invoke-MgBetaDownUserManagedDeviceShut |
Shut down device Note To view the v1.0 release of this cmdlet, view Invoke-MgDownUserManagedDeviceShut |
Invoke-MgBetaEnrollUserManagedDeviceNowAction |
Trigger comanagement enrollment action on ConfigurationManager client |
Invoke-MgBetaExecuteUserManagedDeviceAction |
Invoke action executeAction |
Invoke-MgBetaExtractUserDriveItemSensitivityLabel |
Invoke action extractSensitivityLabels Note To view the v1.0 release of this cmdlet, view Invoke-MgExtractUserDriveItemSensitivityLabel |
Invoke-MgBetaExtractUserDriveRootSensitivityLabel |
Invoke action extractSensitivityLabels Note To view the v1.0 release of this cmdlet, view Invoke-MgExtractUserDriveRootSensitivityLabel |
Invoke-MgBetaExtractUserInformationProtectionPolicyLabel |
Using the metadata that exists on an already-labeled piece of information, resolve the metadata to a specific sensitivity label. The contentInfo input is resolved to informationProtectionContentLabel. |
Invoke-MgBetaExtractUserSecurityInformationProtectionSensitivityLabelContentLabel |
Use the metadata that exists on an already-labeled piece of information to resolve the metadata to a specific sensitivity label. The contentInfo input is resolved to informationProtectionContentLabel. |
Invoke-MgBetaFollowUserDriveItem |
Follow a driveItem. Note To view the v1.0 release of this cmdlet, view Invoke-MgFollowUserDriveItem |
Invoke-MgBetaFollowUserDriveRoot |
Follow a driveItem. Note To view the v1.0 release of this cmdlet, view Invoke-MgFollowUserDriveRoot |
Invoke-MgBetaForwardUserEvent |
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 v1.0 release of this cmdlet, view Invoke-MgForwardUserEvent |
Invoke-MgBetaForwardUserEventInstance |
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 v1.0 release of this cmdlet, view Invoke-MgForwardUserEventInstance |
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-MgBetaGraphUserChat |
Unhide a chat for a user. Note To view the v1.0 release of this cmdlet, view Invoke-MgGraphUserChat |
Invoke-MgBetaHasUserDeviceEnrollmentConfigurationPayloadLink |
Invoke action hasPayloadLinks |
Invoke-MgBetaInitiateUserManagedDeviceAttestation |
Perform Device Attestation |
Invoke-MgBetaInitiateUserManagedDeviceMobileDeviceManagementKeyRecovery |
Perform MDM key recovery and TPM attestation |
Invoke-MgBetaInitiateUserManagedDeviceOnDemandProactiveRemediation |
Perform On Demand Proactive Remediation |
Invoke-MgBetaInvalidateAllUserRefreshToken |
Invalidates all of the user's refresh tokens issued to applications (as well as session cookies in a user's browser), by resetting the refreshTokensValidFromDateTime 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 would prevent access to any of the organization's data accessed through applications on the device without the user first being required to sign in again. In fact, this operation would force the user to sign in again for all applications that they have previously consented to, independent of device. For developers, if the application attempts to redeem a delegated access token for this user by using an invalidated refresh token, the application will get an error. If this happens, the application will need to acquire a new refresh token by making a request to the authorize endpoint, which will force the user to sign in. |
Invoke-MgBetaInviteUserDriveItem |
Sends a sharing invitation for a driveItem.A sharing invitation provides permissions to the recipients and optionally sends an email to the recipients to notify them the item was shared. Note To view the v1.0 release of this cmdlet, view Invoke-MgInviteUserDriveItem |
Invoke-MgBetaInviteUserDriveRoot |
Sends a sharing invitation for a driveItem.A sharing invitation provides permissions to the recipients and optionally sends an email to the recipients to notify them the item was shared. Note To view the v1.0 release of this cmdlet, view Invoke-MgInviteUserDriveRoot |
Invoke-MgBetaLicenseUser |
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 v1.0 release of this cmdlet, view Invoke-MgLicenseUser |
Invoke-MgBetaLogoutUserManagedDeviceSharedAppleDeviceActiveUser |
Logout shared Apple device active user Note To view the v1.0 release of this cmdlet, view Invoke-MgLogoutUserManagedDeviceSharedAppleDeviceActiveUser |
Invoke-MgBetaMarkUserChatReadForUser |
Mark a chat as read for a user. Note To view the v1.0 release of this cmdlet, view Invoke-MgMarkUserChatReadForUser |
Invoke-MgBetaMarkUserChatUnreadForUser |
Mark a chat as unread for a user. Note To view the v1.0 release of this cmdlet, view Invoke-MgMarkUserChatUnreadForUser |
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-MgBetaOverrideUserManagedDeviceComplianceState |
Invoke action overrideComplianceState |
Invoke-MgBetaPlayUserManagedDeviceLostModeSound |
Play lost mode sound |
Invoke-MgBetaPreviewUserDriveItem |
Invoke action preview Note To view the v1.0 release of this cmdlet, view Invoke-MgPreviewUserDriveItem |
Invoke-MgBetaPreviewUserDriveRoot |
Invoke action preview Note To view the v1.0 release of this cmdlet, view Invoke-MgPreviewUserDriveRoot |
Invoke-MgBetaReauthorizeUserDriveItemSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the v1.0 release of this cmdlet, view Invoke-MgReauthorizeUserDriveItemSubscription |
Invoke-MgBetaReauthorizeUserDriveListSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the v1.0 release of this cmdlet, view Invoke-MgReauthorizeUserDriveListSubscription |
Invoke-MgBetaReauthorizeUserDriveRootSubscription |
Reauthorize a subscription when you receive a reauthorizationRequired challenge. Note To view the v1.0 release of this cmdlet, view Invoke-MgReauthorizeUserDriveRootSubscription |
Invoke-MgBetaRecordUserPendingAccessReviewInstanceDecision |
As a reviewer of an access review, record a decision for an accessReviewInstanceDecisionItem that is assigned to you and that matches the principal or resource IDs specified. If no IDs are specified, the decisions will apply to every accessReviewInstanceDecisionItem for which you are the reviewer. |
Invoke-MgBetaReenableUserManagedDevice |
Invoke action reenable |
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-MgBetaReprovisionUserCloudPc |
Reprovision a specific Cloud PC. |
Invoke-MgBetaReprovisionUserManagedDeviceCloudPc |
Reprovision a Cloud PC with an Intune managed device ID. |
Invoke-MgBetaRetireUserManagedDevice |
Retire a device Note To view the v1.0 release of this cmdlet, view Invoke-MgRetireUserManagedDevice |
Invoke-MgBetaRetryUserCloudPcPartnerAgentInstallation |
Retry installation for the partner agents that failed to install on the Cloud PC. Service side checks which agent installation failed firstly and retry. |
Invoke-MgBetaRetryUserServiceProvisioning |
Retry the user service provisioning. Note To view the v1.0 release of this cmdlet, view Invoke-MgRetryUserServiceProvisioning |
Invoke-MgBetaRotateUserManagedDeviceBitLockerKey |
Rotate BitLockerKeys |
Invoke-MgBetaRotateUserManagedDeviceFileVaultKey |
Invoke action rotateFileVaultKey |
Invoke-MgBetaRotateUserManagedDeviceLocalAdminPassword |
Initiates a manual rotation for the local admin password on the device |
Invoke-MgBetaScanUserManagedDeviceWindowsDefender |
Invoke action windowsDefenderScan Note To view the v1.0 release of this cmdlet, view Invoke-MgScanUserManagedDeviceWindowsDefender |
Invoke-MgBetaSignUserInformationProtectionDigest |
Invoke action signDigest |
Invoke-MgBetaSnoozeUserEventInstanceReminder |
Postpone a reminder for an event in a user calendar until a new time. Note To view the v1.0 release of this cmdlet, view Invoke-MgSnoozeUserEventInstanceReminder |
Invoke-MgBetaSnoozeUserEventReminder |
Postpone a reminder for an event in a user calendar until a new time. Note To view the v1.0 release of this cmdlet, view Invoke-MgSnoozeUserEventReminder |
Invoke-MgBetaSoftUserChatMessageDelete |
Delete a single chatMessage or a chat message reply in a channel or a chat. Note To view the v1.0 release of this cmdlet, view Invoke-MgSoftUserChatMessageDelete |
Invoke-MgBetaSoftUserChatMessageReplyDelete |
Delete a single chatMessage or a chat message reply in a channel or a chat. Note To view the v1.0 release of this cmdlet, view Invoke-MgSoftUserChatMessageReplyDelete |
Invoke-MgBetaTranslateUserExchangeId |
Translate identifiers of Outlook-related resources between formats. Note To view the v1.0 release of this cmdlet, view Invoke-MgTranslateUserExchangeId |
Invoke-MgBetaTroubleshootUserCloudPc |
Troubleshoot a specific Cloud PC. Use this API to check the health status of the Cloud PC and the session host. |
Invoke-MgBetaUnarchiveUserPlannerPlan |
Unarchive a plannerPlan object. Unarchiving a plan, also unarchives the plannerTasks and plannerBuckets in the plan. Only a plan that is archived can be unarchived. |
Invoke-MgBetaUnfollowUserDriveItem |
Unfollow a driveItem. Note To view the v1.0 release of this cmdlet, view Invoke-MgUnfollowUserDriveItem |
Invoke-MgBetaUnfollowUserDriveRoot |
Unfollow a driveItem. Note To view the v1.0 release of this cmdlet, view Invoke-MgUnfollowUserDriveRoot |
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. |
Join-MgBetaUserDriveListContentTypeWithHubSite |
Invoke action associateWithHubSites Note To view the v1.0 release of this cmdlet, view Join-MgUserDriveListContentTypeWithHubSite |
Lock-MgBetaUserManagedDeviceRemote |
Remote lock Note To view the v1.0 release of this cmdlet, view Lock-MgUserManagedDeviceRemote |
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-MgBetaUserManagedDeviceToOu |
Invoke action moveDevicesToOU |
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 |
Move-MgBetaUserPlannerPlanToContainer |
Move a planner plan object from one planner plan container to another. Planner plans can only be moved from a user container to a group container. |
New-MgBetaUserCloudPcSnapshot |
Create a snapshot for a specific Cloud PC device. |
New-MgBetaUserDeviceEnrollmentConfigurationEnrollmentNotificationConfiguration |
Invoke action createEnrollmentNotificationConfiguration |
New-MgBetaUserDriveItemLink |
Create a link to share a driveItem driveItem.The createLink action creates 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 is returned. DriveItem resources inherit sharing permissions from their ancestors. Note To view the v1.0 release of this cmdlet, view New-MgUserDriveItemLink |
New-MgBetaUserDriveItemListItemLink |
Create a sharing link for a listItem. The createLink action creates 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, this action returns the existing sharing link. listItem resources inherit sharing permissions from the list the item resides in. Note To view the v1.0 release of this cmdlet, view New-MgUserDriveItemListItemLink |
New-MgBetaUserDriveItemUploadSession |
Invoke action createUploadSession Note To view the v1.0 release of this cmdlet, view New-MgUserDriveItemUploadSession |
New-MgBetaUserDriveListItemLink |
Create a sharing link for a listItem. The createLink action creates 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, this action returns the existing sharing link. listItem resources inherit sharing permissions from the list the item resides in. Note To view the v1.0 release of this cmdlet, view New-MgUserDriveListItemLink |
New-MgBetaUserDriveRootLink |
Create a link to share a driveItem driveItem.The createLink action creates 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 is returned. DriveItem resources inherit sharing permissions from their ancestors. Note To view the v1.0 release of this cmdlet, view New-MgUserDriveRootLink |
New-MgBetaUserDriveRootListItemLink |
Create a sharing link for a listItem. The createLink action creates 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, this action returns the existing sharing link. listItem resources inherit sharing permissions from the list the item resides in. Note To view the v1.0 release of this cmdlet, view New-MgUserDriveRootListItemLink |
New-MgBetaUserDriveRootUploadSession |
Invoke action createUploadSession Note To view the v1.0 release of this cmdlet, view New-MgUserDriveRootUploadSession |
New-MgBetaUserEventAttachmentUploadSession |
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-MgUserEventAttachmentUploadSession |
New-MgBetaUserEventInstanceAttachmentUploadSession |
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-MgUserEventInstanceAttachmentUploadSession |
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-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-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-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-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-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-MgBetaUserManagedDeviceLogCollectionRequest |
Invoke action createDeviceLogCollectionRequest |
New-MgBetaUserManagedDeviceLogCollectionResponseDownloadUrl |
Invoke action createDownloadUrl Note To view the v1.0 release of this cmdlet, view New-MgUserManagedDeviceLogCollectionResponseDownloadUrl |
New-MgBetaUserManagedDeviceWindowsDefenderUpdateSignature |
Invoke action windowsDefenderUpdateSignatures Note To view the v1.0 release of this cmdlet, view New-MgUserManagedDeviceWindowsDefenderUpdateSignature |
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-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-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 |
New-MgBetaUserMobileAppTroubleshootingEventAppLogCollectionRequestDownloadUrl |
Invoke action createDownloadUrl |
New-MgBetaUserOutlookTaskAttachmentUploadSession |
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. |
New-MgBetaUserOutlookTaskFolderTaskAttachmentUploadSession |
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. |
New-MgBetaUserOutlookTaskGroupTaskFolderTaskAttachmentUploadSession |
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. |
New-MgBetaUserTodoListTaskAttachmentUploadSession |
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 v1.0 release of this cmdlet, view New-MgUserTodoListTaskAttachmentUploadSession |
Publish-MgBetaUserDriveListContentType |
Invoke action publish Note To view the v1.0 release of this cmdlet, view Publish-MgUserDriveListContentType |
Remove-MgBetaAllUserDeviceFromManagement |
Retire all devices from management for this user Note To view the v1.0 release of this cmdlet, view Remove-MgAllUserDeviceFromManagement |
Remove-MgBetaUserCalendarPermanent |
Permanently delete a calendar folder and the events that it contains and remove them from the mailbox. For more information about item retention, see Configure Deleted Item retention and Recoverable Items quotas. |
Remove-MgBetaUserChatAccessForUser |
Remove access to a chat for a user. |
Remove-MgBetaUserContactFolderChildFolderContactPermanent |
Permanently delete a contact 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. |
Remove-MgBetaUserContactFolderChildFolderPermanent |
Permanently delete a contact 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. |
Remove-MgBetaUserContactFolderContactPermanent |
Permanently delete a contact 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. |
Remove-MgBetaUserContactFolderPermanent |
Permanently delete a contact 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. |
Remove-MgBetaUserContactPermanent |
Permanently delete a contact 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. |
Remove-MgBetaUserDriveItemCheckout |
Discard the check out of a driveItem. This action releases a driveItem resource that was previously checked out. Any changes made to the item while it was checked out are discarded. The same user that performed the checkout must discard it. Another alternative is to use application permissions. |
Remove-MgBetaUserDriveItemPermanent |
Invoke action permanentDelete Note To view the v1.0 release of this cmdlet, view Remove-MgUserDriveItemPermanent |
Remove-MgBetaUserDriveRootCheckout |
Discard the check out of a driveItem. This action releases a driveItem resource that was previously checked out. Any changes made to the item while it was checked out are discarded. The same user that performed the checkout must discard it. Another alternative is to use application permissions. |
Remove-MgBetaUserDriveRootPermanent |
Invoke action permanentDelete Note To view the v1.0 release of this cmdlet, view Remove-MgUserDriveRootPermanent |
Remove-MgBetaUserEventInstancePermanent |
Permanently delete an event and place it in the Purges folder in the dumpster in the user's mailbox. Email clients such as Outlook or the 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. |
Remove-MgBetaUserEventPermanent |
Permanently delete an event and place it in the Purges folder in the dumpster in the user's mailbox. Email clients such as Outlook or the 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. |
Remove-MgBetaUserFollowedSite |
Unfollow a user's site or multiple sites. Note To view the v1.0 release of this cmdlet, view Remove-MgUserFollowedSite |
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. |
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. |
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. |
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. |
Remove-MgBetaUserManagedDeviceFirmwareConfigurationInterfaceManagement |
Remove device from Device Firmware Configuration Interface management |
Remove-MgBetaUserManagedDeviceUserFromSharedAppleDevice |
Delete user from shared Apple device Note To view the v1.0 release of this cmdlet, view Remove-MgUserManagedDeviceUserFromSharedAppleDevice |
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. |
Remove-MgBetaUserOutlookTaskFolderPermanent |
Permanently delete an outlook task 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. |
Remove-MgBetaUserOutlookTaskFolderTaskPermanent |
Permanently delete an Outlook task and place it in the Purges folder in the user's mailbox. Email clients such as Outlook or the 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. |
Remove-MgBetaUserOutlookTaskGroupTaskFolderPermanent |
Permanently delete an outlook task 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. |
Remove-MgBetaUserOutlookTaskGroupTaskFolderTaskPermanent |
Permanently delete an Outlook task and place it in the Purges folder in the user's mailbox. Email clients such as Outlook or the 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. |
Remove-MgBetaUserOutlookTaskPermanent |
Permanently delete an Outlook task and place it in the Purges folder in the user's mailbox. Email clients such as Outlook or the 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. |
Remove-MgBetaUserPasswordSingleSignOnCredential |
Delete the password-based single sign-on credentials for a given user to a given service principal. |
Rename-MgBetaUserCloudPc |
Rename a specific Cloud PC. Use this API to update the displayName for the Cloud PC entity. |
Rename-MgBetaUserCloudPcUserAccountType |
Change the account type of the user on a specific Cloud PC. |
Rename-MgBetaUserManagedDeviceAssignment |
Invoke action changeAssignments |
Request-MgBetaUserManagedDeviceRemoteAssistance |
Request remote assistance Note To view the v1.0 release of this cmdlet, view Request-MgUserManagedDeviceRemoteAssistance |
Reset-MgBetaUserAuthenticationMethodPassword |
Initiate a reset for the password associated with 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. To reset a user's password in in Azure AD B2C, use the Update user API operation and update the passwordProfile > forceChangePasswordNextSignIn object. 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 will return a Location header with a link where the caller can periodically check for the status of the reset operation. Note To view the v1.0 release of this cmdlet, view Reset-MgUserAuthenticationMethodPassword |
Reset-MgBetaUserManagedDevicePasscode |
Reset passcode Note To view the v1.0 release of this cmdlet, view Reset-MgUserManagedDevicePasscode |
Reset-MgBetaUserPendingAccessReviewInstanceDecision |
Resets decisions of all accessReviewInstanceDecisionItem objects on an accessReviewInstance to notReviewed. |
Resize-MgBetaUserCloudPc |
Upgrade or downgrade an existing Cloud PC to a configuration with a new virtual CPU (vCPU) and storage size. |
Resize-MgBetaUserManagedDeviceCloudPc |
Upgrade or downgrade an existing Cloud PC to another configuration with a new virtual CPU (vCPU) and storage size. |
Restart-MgBetaUserCloudPc |
Reboot a specific Cloud PC. |
Restart-MgBetaUserManagedDeviceNow |
Reboot device Note To view the v1.0 release of this cmdlet, view Restart-MgUserManagedDeviceNow |
Restore-MgBetaUserCloudPc |
Restore a specific Cloud PC. Use this API to trigger a remote action that restores a Cloud PC device to a previous state. |
Restore-MgBetaUserDriveItem |
Restore a driveItem that has been deleted and is currently in the recycle bin. Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveItem |
Restore-MgBetaUserDriveItemListItemDocumentSetVersion |
Restore a document set version. Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveItemListItemDocumentSetVersion |
Restore-MgBetaUserDriveItemListItemVersion |
Invoke action restoreVersion Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveItemListItemVersion |
Restore-MgBetaUserDriveItemVersion |
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 v1.0 release of this cmdlet, view Restore-MgUserDriveItemVersion |
Restore-MgBetaUserDriveListItemDocumentSetVersion |
Restore a document set version. Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveListItemDocumentSetVersion |
Restore-MgBetaUserDriveListItemVersion |
Invoke action restoreVersion Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveListItemVersion |
Restore-MgBetaUserDriveRoot |
Restore a driveItem that has been deleted and is currently in the recycle bin. Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveRoot |
Restore-MgBetaUserDriveRootListItemDocumentSetVersion |
Restore a document set version. Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveRootListItemDocumentSetVersion |
Restore-MgBetaUserDriveRootListItemVersion |
Invoke action restoreVersion Note To view the v1.0 release of this cmdlet, view Restore-MgUserDriveRootListItemVersion |
Restore-MgBetaUserDriveRootVersion |
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 v1.0 release of this cmdlet, view Restore-MgUserDriveRootVersion |
Restore-MgBetaUserManagedDeviceCloudPc |
Restore a Cloud PC device to a previous state with an Intune managed device ID. |
Restore-MgBetaUserManagedDevicePasscode |
Recover passcode Note To view the v1.0 release of this cmdlet, view Restore-MgUserManagedDevicePasscode |
Revoke-MgBetaUserDriveItemListItemPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserDriveItemPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserDriveListItemPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserDriveListPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserDriveRootListItemPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserDriveRootPermissionGrant |
Revoke access to a listItem or driveItem granted via a sharing link by removing the specified recipient from the link. |
Revoke-MgBetaUserManagedDeviceAppleVppLicense |
Revoke all Apple Vpp licenses for a device |
Revoke-MgBetaUserSignInSession |
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. If the application attempts to redeem a delegated access token for this user by using an invalidated refresh token, the application will get an error. If this happens, the application will need to acquire a new refresh token by making a request to the authorize endpoint, which will force the user to sign in. Note To view the v1.0 release of this cmdlet, view Revoke-MgUserSignInSession |
Send-MgBetaUserChatActivityNotification |
Send an activity feed notification in the scope of a chat. For more information, see sending Teams activity notifications. Note To view the v1.0 release of this cmdlet, view Send-MgUserChatActivityNotification |
Send-MgBetaUserMail |
Send the message specified in the request body using either JSON or MIME format. When using JSON format, you can include an attachment and use a mention to call out another user in the new message. 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 v1.0 release of this cmdlet, view Send-MgUserMail |
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-MgBetaUserManagedDeviceCustomNotificationToCompanyPortal |
Invoke action sendCustomNotificationToCompanyPortal |
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 |
Send-MgBetaUserOnlineMeetingJoinWebUrlVirtualAppointmentReminderSm |
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. |
Send-MgBetaUserOnlineMeetingJoinWebUrlVirtualAppointmentSm |
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. |
Send-MgBetaUserOnlineMeetingVirtualAppointmentReminderSm |
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 v1.0 release of this cmdlet, view Send-MgUserOnlineMeetingVirtualAppointmentReminderSm |
Send-MgBetaUserOnlineMeetingVirtualAppointmentSm |
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 v1.0 release of this cmdlet, view Send-MgUserOnlineMeetingVirtualAppointmentSm |
Send-MgBetaUserPendingAccessReviewInstanceReminder |
Send a reminder to the reviewers of a currently active accessReviewInstance. |
Send-MgBetaUserTeamworkActivityNotification |
Send an activity feed notification to a user. For more information, see sending Teams activity notifications. Note To view the v1.0 release of this cmdlet, view Send-MgUserTeamworkActivityNotification |
Set-MgBetaUserChatMessageReaction |
Invoke action setReaction Note To view the v1.0 release of this cmdlet, view Set-MgUserChatMessageReaction |
Set-MgBetaUserChatMessageReplyReaction |
Invoke action setReaction Note To view the v1.0 release of this cmdlet, view Set-MgUserChatMessageReplyReaction |
Set-MgBetaUserCloudPcReviewStatus |
Invoke action setReviewStatus |
Set-MgBetaUserDeviceEnrollmentConfiguration |
Invoke action assign |
Set-MgBetaUserDeviceEnrollmentConfigurationPriority |
Invoke action setPriority |
Set-MgBetaUserDriveItemSensitivityLabel |
Invoke action assignSensitivityLabel Note To view the v1.0 release of this cmdlet, view Set-MgUserDriveItemSensitivityLabel |
Set-MgBetaUserDriveRootSensitivityLabel |
Invoke action assignSensitivityLabel Note To view the v1.0 release of this cmdlet, view Set-MgUserDriveRootSensitivityLabel |
Set-MgBetaUserLicense |
Add or remove licenses for the user to enable or disable their use of Microsoft cloud offerings that the company has licenses to. For example, an organization can have a Microsoft 365 Enterprise E3 subscription with 100 licenses, and this request assigns one of those licenses to a specific user. You can also enable and disable specific plans associated with a subscription. Direct user licensing is an alternative to group-based licensing. To get the subscriptions available in the directory, perform a GET subscribedSkus request. Note To view the v1.0 release of this cmdlet, view Set-MgUserLicense |
Set-MgBetaUserManagedDeviceCloudPcReviewStatus |
Set the review status of a specific Cloud PC device. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC as suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. |
Set-MgBetaUserManagedDeviceName |
Set device name of the device. |
Set-MgBetaUserPresence |
Set the availability and activity status in a presence session of an application for a user. Note To view the v1.0 release of this cmdlet, view Set-MgUserPresence |
Set-MgBetaUserPresenceStatusMessage |
Set a presence status message for a user. An optional expiration date and time can be supplied. Note To view the v1.0 release of this cmdlet, view Set-MgUserPresenceStatusMessage |
Set-MgBetaUserPresenceUserPreferredPresence |
Set the preferred availability and activity status for a user. If the preferred presence of a user is set, the user's presence is the preferred presence. Preferred presence takes effect only when there is at least one presence session of the user. Otherwise, the user's presence stays as Offline. A presence session can be created as a result of a successful setPresence operation, or if the user is signed in on a Teams client. Read more about presence sessions and their time-out and expiration. Note To view the v1.0 release of this cmdlet, view Set-MgUserPresenceUserPreferredPresence |
Skip-MgBetaUserManagedDeviceActivationLock |
Bypass activation lock Note To view the v1.0 release of this cmdlet, view Skip-MgUserManagedDeviceActivationLock |
Start-MgBetaUserCloudPc |
Power on a Windows 365 Frontline Cloud PC. This action supports Microsoft Endpoint Manager (MEM) admin scenarios. After a Windows 365 Frontline Cloud PC is powered on, it is allocated to a user, and licenses are assigned immediately. Only IT admin users can perform this action. |
Start-MgBetaUserManagedDeviceConfigurationManagerAction |
Trigger action on ConfigurationManager client |
Start-MgBetaUserSolutionWorkingTimeScheduleWorkingTime |
Trigger the policies associated with the start of working hours for a specific user. Note To view the v1.0 release of this cmdlet, view Start-MgUserSolutionWorkingTimeScheduleWorkingTime |
Stop-MgBetaUserCloudPc |
Power off a Windows 365 Frontline Cloud PC. This action supports Microsoft Endpoint Manager (MEM) admin scenarios. After a Windows 365 Frontline Cloud PC is powered off, it's deallocated, and licenses are revoked immediately. Only IT admin users can perform this action. |
Stop-MgBetaUserCloudPcGracePeriod |
End the grace period for a specific Cloud PC. The grace period is triggered when the Cloud PC license is removed or the provisioning policy is unassigned. It allows users to access Cloud PCs for up to seven days before deprovisioning occurs. Ending the grace period immediately deprovisions the Cloud PC without waiting the seven days. |
Stop-MgBetaUserEvent |
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 v1.0 release of this cmdlet, view Stop-MgUserEvent |
Stop-MgBetaUserEventInstance |
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 v1.0 release of this cmdlet, view Stop-MgUserEventInstance |
Stop-MgBetaUserPendingAccessReviewInstance |
Stop a currently active accessReviewInstance. After the access review instance stops, the instance status will be Completed, the reviewers can no longer give input, and the access review decisions can be applied. Stopping an instance will not effect future instances. To prevent a recurring access review from starting future instances, update the schedule definition to change its scheduled end date. |
Stop-MgBetaUserPendingAccessReviewInstanceApplyDecision |
Invoke action stopApplyDecisions |
Stop-MgBetaUserPendingAccessReviewInstanceStage |
Stop an access review stage that is inProgress. After the access review stage stops, the stage status will be Completed and the reviewers can no longer give input. If there are subsequent stages that depend on the completed stage, the next stage will be created. The accessReviewInstanceDecisionItem objects will always reflect the last decisions recorded across all stages at that given time, regardless of the status of the stages. |
Stop-MgBetaUserSolutionWorkingTimeScheduleWorkingTime |
Trigger the policies associated with the end of working hours for a specific user. Note To view the v1.0 release of this cmdlet, view Stop-MgUserSolutionWorkingTimeScheduleWorkingTime |
Suspend-MgBetaUserManagedDeviceConfigurationRefresh |
Initiates a command to pause config refresh for the device. |
Sync-MgBetaUserManagedDevice |
Invoke action syncDevice Note To view the v1.0 release of this cmdlet, view Sync-MgUserManagedDevice |
Test-MgBetaUserCloudPcBulkResize |
Validate that a set of cloudPC devices meet the requirements to be bulk resized. |
Test-MgBetaUserDriveItemPermission |
Invoke action validatePermission Note To view the v1.0 release of this cmdlet, view Test-MgUserDriveItemPermission |
Test-MgBetaUserDriveRootPermission |
Invoke action validatePermission Note To view the v1.0 release of this cmdlet, view Test-MgUserDriveRootPermission |
Test-MgBetaUserInformationProtectionDataLossPreventionPolicy |
Invoke action evaluate |
Test-MgBetaUserInformationProtectionPolicyLabelApplication |
Compute the information protection label that should be applied and return the set of actions that must be taken to correctly label the information. This API is useful when a label should be set manually or explicitly by a user or service, rather than automatically based on file contents. Given contentInfo, which includes existing content metadata key/value pairs, and labelingOptions as an input, the API returns an informationProtectionAction object that contains one of more of the following: |
Test-MgBetaUserInformationProtectionPolicyLabelClassificationResult |
Using classification results, compute the information protection label that should be applied and return the set of actions that must be taken to correctly label the information. This API is useful when a label should be set automatically based on classification of the file contents, rather than labeled directly by a user or service. To evaluate based on classification results, provide contentInfo, which includes existing content metadata key/value pairs, and classification results. The API returns an informationProtectionAction that contains one of more of the following: |
Test-MgBetaUserInformationProtectionPolicyLabelRemoval |
Indicate to the consuming application what actions it should take to remove the label information. Given contentInfo as an input, which includes existing content metadata key/value pairs, the API returns an informationProtectionAction that contains some combination of one of more of the following: |
Test-MgBetaUserInformationProtectionSensitivityLabel |
Invoke action evaluate |
Test-MgBetaUserInformationProtectionSensitivityLabelSublabel |
Invoke action evaluate |
Test-MgBetaUserJoinedGroupDynamicMembership |
Invoke action evaluateDynamicMembership |
Test-MgBetaUserPassword |
Check a user's password against the organization's password validation policy and report whether the password is valid. Use this action to provide real-time feedback on password strength while the user types their password. |
Test-MgBetaUserProperty |
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. For validating properties of an existing group, use the validateProperties function for groups. The following 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 the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with 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. Note To view the v1.0 release of this cmdlet, view Test-MgUserProperty |
Test-MgBetaUserSecurityInformationProtectionSensitivityLabelApplication |
Compute the sensitivity label that should be applied and return the set of actions that must be taken to correctly label the information. This API is useful when a label should be set manually or explicitly by a user or service, rather than automatically based on file contents. Given contentInfo, which includes existing content metadata key-value pairs, and labelingOptions as an input, the API returns an informationProtectionAction object that contains one of more of the following: |
Test-MgBetaUserSecurityInformationProtectionSensitivityLabelClassificationResult |
Use the classification results to compute the sensitivity label that should be applied and return the set of actions that must be taken to correctly label the information. This API is useful when a label should be set automatically based on classification of the file contents, rather than labeled directly by a user or service. To evaluate based on classification results, provide the contentInfo, which includes existing content metadata key-value pairs, and classification results. The API returns an informationProtectionAction that contains one of more of the following: |
Test-MgBetaUserSecurityInformationProtectionSensitivityLabelRemoval |
Indicate to the consuming application what actions it should take to remove the label information. Given contentInfo as an input, which includes existing content metadata key-value pairs, the API returns an informationProtectionAction that contains some combination of one or more of the following: |
Unblock-MgBetaUserManagedApp |
Unblocks the managed app user from app check-in. |
Undo-MgBetaUserChatMessageReplySoftDelete |
Undo soft deletion of a single chatMessage or a chat message reply in a channel or a chat. Note To view the v1.0 release of this cmdlet, view Undo-MgUserChatMessageReplySoftDelete |
Undo-MgBetaUserChatMessageSoftDelete |
Undo soft deletion of a single chatMessage or a chat message reply in a channel or a chat. Note To view the v1.0 release of this cmdlet, view Undo-MgUserChatMessageSoftDelete |
Unpublish-MgBetaUserDriveListContentType |
Invoke action unpublish Note To view the v1.0 release of this cmdlet, view Unpublish-MgUserDriveListContentType |
Update-MgBetaUserChatInstalledApp |
Upgrade an app installation within a chat. Note To view the v1.0 release of this cmdlet, view Update-MgUserChatInstalledApp |
Update-MgBetaUserManagedDeviceWindowsDeviceAccount |
Invoke action updateWindowsDeviceAccount Note To view the v1.0 release of this cmdlet, view Update-MgUserManagedDeviceWindowsDeviceAccount |
Update-MgBetaUserOnenotePageContent |
Invoke action onenotePatchContent Note To view the v1.0 release of this cmdlet, view Update-MgUserOnenotePageContent |
Update-MgBetaUserPassword |
Update the signed-in user's password. Any user can update their password without belonging to any administrator role. Note To view the v1.0 release of this cmdlet, view Update-MgUserPassword |