Default
Type: N/A
| Cmdlet | Role | Cmdlet Description |
|---|---|---|
| Add-VivaModuleFeaturePolicy | N/A | Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a specific feature in Viva. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. To learn more about assigned roles at the feature level, see Features Available for Feature Access Management (https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Add-VivaOrgInsightsDelegatedRole | N/A | To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - Insights Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Add-WorkforceInsightsDelegationAccess | N/A | To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - AI Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Connect-ExchangeOnline | N/A | This cmdlet creates a PowerShell connection to your Exchange Online organization. Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, $). The workaround is to connect using a different account that doesnt have special characters in the profile path. |
| Connect-IPPSSession | N/A | For detailed connection instructions, including prerequisites, see Connect to Security & Compliance PowerShell (https://learn.microsoft.com/powershell/exchange/connect-to-scc-powershell). |
| Disconnect-ExchangeOnline | N/A | This cmdlet is the counterpart to the Connect-ExchangeOnline and Connect-IPPSSession cmdlets. This cmdlet disconnects any connections and clears the cache. After a successful disconnect, you cant successfully run any cmdlets for your organization. Disconnect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, $). The workaround is to connect using a different account that doesnt have special characters in the profile path. |
| Get-ConnectionInformation | N/A | The Get-ConnectionInformation cmdlet returns the information about all active REST-based connections with Exchange Online in the current PowerShell instance. This cmdlet is equivalent to the Get-PSSession cmdlet thats used with remote PowerShell sessions. The output of the cmdlet contains the following properties: - ConnectionId: A unique GUID value for the connection. For example, 8b632b3a-a2e2-8ff3-adcd-6d119d07694b. - State: For example, Connected. - Id: An integer that identifies the session in the PowerShell window. The first connection is 1, the second is 2, etc. - Name: A unique name thats based on the PowerShell environment and Id value. For example, ExchangeOnline_1 for Exchange Online PowerShell or ExchangeOnlineProtection_1 for Security & Compliance PowerShell. - UserPrincipalName: The account that was used to connect. For example, laura@contoso.onmicrosoft.com. - ConnectionUri: The connection endpoint that was used. For example, https://outlook.office365.com for Exchange Online PowerShell or https://nam12b.ps.compliance.protection.outlook.com for Security & Compliance PowerShell. - AzureAdAuthorizationEndpointUri : The Microsoft Entra authorization endpoint for the connection. For example, https://login.microsoftonline.com/organizations for Exchange Online PowerShell or https://login.microsoftonline.com/organizations for Security & Compliance PowerShell. - TokenExpiryTimeUTC: When the connection token expires. For example, 9/30/2023 6:42:24 PM +00:00. - CertificateAuthentication: Whether certificate based authentication (also known as CBA or app-only authentication) was used to connect. Values are True or False. - ModuleName: The filename and path of the temporary data for the session. For example, C:\Users\laura\AppData\Local\Temp\tmpEXO_a54z135k.qgv - ModulePrefix: The value specified using the Prefix parameter in the Connect-ExchangeOnline or Connect-IPPSSession command. - Organization: The value specified using the Organization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA or managed identity connections. - DelegatedOrganization: The value specified using the DelegatedOrganization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command. - AppId: The value specified using the AppId parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA connections. - PageSize: The default maximum number of entries per page in the connection. The default value is 1000, or you can use the PageSize parameter in the Connect-ExchangeOnline command to specify a lower number. Individual cmdlets might also have a PageSize parameter. - TenantID: The tenant ID GUID value. For example, 3750b40b-a68b-4632-9fb3-5b1aff664079. - TokenStatus: For example, Active. - ConnectionUsedForInbuiltCmdlets - IsEopSession: For Exchange Online PowerShell connections, the value is False. For Security & Compliance PowerShell connections, the value is True. |
| Get-DefaultTenantBriefingConfig | N/A | The default Briefing email configuration for the organization affects only new users and existing users who havent already updated their user settings to opt-in or opt-out of the Briefing email. This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator For more information, see Microsoft Entra built-in roles (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-DefaultTenantMyAnalyticsFeatureConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator For more information, see Microsoft Entra built-in roles (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-EXOCasMailbox | N/A | This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4. |
| Get-EXOMailbox | N/A | By default, this cmdlet returns a summary list (a minimum set of properties) of all mailboxes in your organization. |
| Get-EXOMailboxFolderPermission | N/A | Use this cmdlet to retrieve folder level permission in the mailbox. |
| Get-EXOMailboxFolderStatistics | N/A | A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-EXOMailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. Dont confuse Get-EXOMailboxFolderStatistics cmdlet (folders) with the Get-EXOMailboxStatistics cmdlet (mailboxes). |
| Get-EXOMailboxPermission | N/A | The output of this cmdlet shows the following information: - Identity: The mailbox in question. - User: The security principal (user, security group, Exchange management role group, etc.) that has permission to the mailbox. - AccessRights: The permission that the security principal has on the mailbox. The available values are ChangeOwner (change the owner of the mailbox), ChangePermission (change the permissions on the mailbox), DeleteItem (delete the mailbox), ExternalAccount (indicates the account isnt in the same domain), FullAccess (open the mailbox, access its contents, but cant send mail) and ReadPermission (read the permissions on the mailbox). Whether the permissions are allowed or denied is indicated in the Deny column. - IsInherited: Whether the permission is inherited (True) or directly assigned to the mailbox (False). Permissions are inherited from the mailbox database and/or Active Directory. Typically, directly assigned permissions override inherited permissions. - Deny: Whether the permission is allowed (False) or denied (True). Typically, deny permissions override allow permissions. By default, the following permissions are assigned to user mailboxes: - FullAccess and ReadPermission are directly assigned to NT AUTHORITY\SELF. This entry gives a user permission to their own mailbox. - FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users mailboxes. - ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. - FullAccess is inherited by NT AUTHORITY\SYSTEM and ReadPermission is inherited by NT AUTHORITY\NETWORK. - FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Microsoft 365). |
| Get-EXOMailboxStatistics | N/A | You can use the detailed move history and a move report output from this cmdlet to troubleshoot a move request. To view the move history, you must pass this cmdlet as an object. Move histories are retained in the mailbox database, are numbered incrementally, and the last run move request is always numbered 0. You can only see move reports and move history for completed move requests. |
| Get-EXOMobileDeviceStatistics | N/A | This cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. |
| Get-EXORecipient | N/A | Get-EXORecipient cmdlet can be used to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). |
| Get-EXORecipientPermission | N/A | This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox appears to be sent by the mailbox owner. However, this permission doesnt allow a delegate to sign in to the users mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate appears to be sent by the group. |
| Get-MyAnalyticsFeatureConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-UserBriefingConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-VivaInsightsSettings | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Teams Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-VivaModuleFeature | N/A | Use the Get-VivaModuleFeature cmdlet to view the features in a Viva module that support feature access controls. You can view all features in a particular Viva module that support feature access controls. To view a specific feature, you can include the FeatureId parameter. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. |
| Get-VivaModuleFeatureEnablement | N/A | Use the Get-VivaModuleFeatureEnablement cmdlet to view whether or not a feature in a Viva module is enabled for a specific user or group. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. Currently, you need to be a member of the Global Administrators role to run this cmdlet. To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-VivaModuleFeaturePolicy | N/A | Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a specified feature in a Viva module in Viva. You can view all policies for a specified feature in a Viva module in Viva. To view a specific policy, you can include the PolicyId parameter. The cmdlet can filter policies based on MemberIds, allowing admins to view policies specific to certain users or groups. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. To learn more about assigned roles at the feature level, see Features Available for Feature Access Management (https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-VivaOrgInsightsDelegatedRole | N/A | Typically, you use this cmdlet with the Remove-VivaOrgInsightsDelegatedRole cmdlet to find the Microsoft Entra ObjectId values of the delegate accounts. To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - Insights Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Get-WorkforceInsightsDelegationAccess | N/A | Typically, you use this cmdlet with the Remove-WorkforceInsightsDelegationAccess cmdlet to find the Microsoft Entra ObjectId values of the delegate accounts. To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - AI Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Remove-VivaModuleFeaturePolicy | N/A | Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. To learn more about assigned roles at the feature level, see Features Available for Feature Access Management (https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Remove-VivaOrgInsightsDelegatedRole | N/A | Use the Get-VivaOrgInsightsDelegatedRole cmdlet to find the Microsoft Entra ObjectId values of delegate accounts that were given the capabilities of delegator accounts. To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - Insights Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Remove-WorkforceInsightsDelegationAccess | N/A | Use the Get-WorkforceInsightsDelegationAccess cmdlet to find the Microsoft Entra ObjectId values of delegate accounts that were given the capabilities of delegator accounts. To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: - Global Administrator - AI Administrator [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Set-DefaultTenantBriefingConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator For more information, see Microsoft Entra built-in roles (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Set-DefaultTenantMyAnalyticsFeatureConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator For more information, see Microsoft Entra built-in roles (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Set-MyAnalyticsFeatureConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Set-OwaMailboxPolicy | N/A | In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Exchange Online, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default. Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-PartnerApplication | N/A | You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see Plan Exchange 2016 integration with SharePoint and Skype for Business (https://docs.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the ExchangeInstallPathScripts folder to configure partner applications. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-PerimeterConfig | N/A | If you have an on-premises email system, you can use the Set-PerimeterConfig cmdlet to add the IP addresses of your gateway servers to cloud-based safelists (also known as whitelists) to make sure that messages sent from your on-premises email system arent treated as spam. |
| Set-PhishSimOverridePolicy | N/A | |
| Set-Place | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-PlaceMailbox | N/A | |
| Set-PolicyTipConfig | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-ProtectionServicePolicy | N/A | |
| Set-PublicFolder | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-PublicFolderMailboxMigrationRequest | N/A | |
| Set-QuarantinePermissions | N/A | |
| Set-QuarantinePolicy | N/A | |
| Set-RegulatoryComplianceUI | N/A | You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center (https://docs.microsoft.com/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center). |
| Set-RemoteDomain | N/A | When you set a remote domain, you can control mail flow with more precision, specify message formatting and policy and specify acceptable character sets for messages sent to or received from the remote domain. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-ReportSchedule | N/A | |
| Set-ReportSubmissionPolicy | N/A | |
| Set-ReportSubmissionRule | N/A | |
| Set-ResourceConfig | N/A | After you use this cmdlet to create custom resource properties, you use the ResourceCustom parameter on the Set-Mailbox cmdlet to add one or more of those properties to a room or equipment mailbox. For more information, see the ResourceCustom parameter description in Set-Mailbox. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-RetentionPolicy | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-RetentionPolicyTag | N/A | Retention tags are used to apply message retention settings to folders and items in a mailbox. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-RMSTemplate | N/A | RMS templates exist in one or more trusted publishing domains (TPDs) that have been imported from an on-premises server running Active Directory Rights Management Services (AD RMS). |
| Set-RoleAssignmentPolicy | N/A | You can use the Set-RoleAssignmentPolicy cmdlet to change the name of an assignment policy or to set the assignment policy as the default assignment policy. For more information about assignment policies, see Understanding management role assignment policies (https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-RoleGroup | N/A | If you want to add or remove members to or from an existing role group, use the Add-RoleGroupMember or Remove-RoleGroupMember cmdlets. If you want to add or remove management role assignments to or from a role group, use the New-ManagementRoleAssignment or Remove-ManagementRoleAssignment cmdlets. If you want to add or remove members to or from a linked role group, you must add or remove the members to or from the foreign universal security group (USG) in the foreign forest. To find the foreign USG, use the Get-RoleGroup cmdlet. If the ManagedBy property is populated with role group managers, the user configuring a role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. For more information about role groups, see Understanding management role groups (https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SafeAttachmentPolicy | N/A | Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see Safe Attachments in Defender for Office 365 (https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-attachments). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SafeAttachmentRule | N/A | Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see Safe Attachments in Defender for Office 365 (https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-attachments). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SafeLinksPolicy | N/A | Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SafeLinksRule | N/A | Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SecOpsOverridePolicy | N/A | |
| Set-ServicePrincipal | N/A | |
| Set-SharingPolicy | N/A | Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesnt have a specific sharing policy assigned, a default policy enforces the sharing options for the mailbox. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SmimeConfig | N/A | The Set-SmimeConfig cmdlet can change several important parameters than can reduce the overall level of message security. Review your organizations security policy before you make any changes. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-SweepRule | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-TeamsProtectionPolicy | N/A | |
| Set-TeamsProtectionPolicyRule | N/A | |
| Set-TenantAllowBlockListItems | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-TenantAllowBlockListSpoofItems | N/A | |
| Set-TenantMailFromAddress | N/A | |
| Set-TenantSettingCrossTenantAccessPolicy | N/A | |
| Set-TextMessagingAccount | N/A | When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. To clear the text messaging settings from your own mailbox, use the Clear-TextMessagingAccount parameter. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-TransportConfig | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-TransportRule | N/A | In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules arent shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role. The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You cant use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-UnifiedAuditSetting | N/A | |
| Set-UnifiedGroup | N/A | Microsoft 365 Groups are group objects that are available across Microsoft 365 services. The HiddenGroupMembershipEnabled parameter is only available on the New-UnifiedGroup cmdlet. You cant change this setting on an existing Microsoft 365 Group group. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-User | N/A | The Set-User cmdlet contains no mail-related properties for mailboxes or mail users. To modify the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Set-Mailbox or Set-MailUser). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Set-UserBriefingConfig | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Insights Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Set-VivaInsightsSettings | N/A | This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: - Global Administrator - Exchange Administrator - Teams Administrator To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |
| Start-AuditAssistant | N/A | |
| Start-HistoricalSearch | N/A | A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are aged between 1-4 hours (depending on your environment) and 90 days old. There is a limit of 250 historical searches that you can submit in a 24 hour period; youll be warned if youre nearing the daily quota. Cancelled searches count against the daily quota. Also, in each CSV file there is a limit of 50000 results or lines. If you specify a distribution group, all messages might not be returned in the results. To ensure that all messages are returned, specify the individual recipient. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Start-ManagedFolderAssistant | N/A | The Managed Folder Assistant uses the retention policy settings of users mailboxes to process retention of items. This mailbox processing occurs automatically. You can use the Start-ManagedFolderAssistant cmdlet to immediately start processing the specified mailbox. In Exchange Server 2010 release to manufacturing (RTM), the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process. In Exchange 2010 Service Pack 1 (SP1) and later, the Mailbox parameter has been removed, and the Identity parameter accepts the mailbox or mail user to process. If you use these parameters in scheduled commands or scripts, we recommend that you review them and make any necessary changes. For more information, see KB4032361 (https://support.microsoft.com/help/4032361). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Start-MigrationBatch | N/A | The Start-MigrationBatch cmdlet starts a pending migration batch that was created, but not started, with the New-MigrationBatch cmdlet. The Start-MigrationBatch cmdlet also will resume a Stopped migration batch or retry failures within a Failed or Synced with Errors migration batch. In the cloud-based service, the Start-MigrationBatch cmdlet can also retry failures within a Completed with Errors migration batch. In the cloud-based service, the Start-MigrationBatch cmdlet can be run at any time to retry failed users within the batch. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Start-MigrationUser | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Start-TransportAsyncReport | N/A | |
| Stop-HistoricalSearch | N/A | A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old. After you start a historical search by using the Start-HistoricalSearch cmdlet, the search is queued, but not actually running. While the search is queued and has the status value of NotStarted, you can use the Stop-HistoricalSearch cmdlet to stop it. After the search is actively running, and has a status value of InProgress, you cant stop it. When you stop a historical search, its given a status value of Cancelled. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Stop-MigrationBatch | N/A | The Stop-MigrationBatch cmdlet stops the migration batch thats being processed in your on-premises Exchange organization or by the cloud-based migration service running in Microsoft 365. You can only stop migration batches that have mailboxes that are still in the process of being migrated or are waiting to be migrated. Stopping a migration wont affect mailboxes that have been migrated already. The migration of mailboxes that are being actively migrated is stopped immediately. If all migration requests in a migration batch are completed or failed, this cmdlet wont run. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Stop-MigrationUser | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Suspend-MailboxRestoreRequest | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Suspend-MoveRequest | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Suspend-PublicFolderMailboxMigrationRequest | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Sync-CrossTenantAccessPolicy | N/A | |
| Test-ApplicationAccessPolicy | N/A | This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Test-ArchiveConnectivity | N/A | |
| Test-ClientAccessRule | N/A | Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. Note : Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list: - OutlookWebApp:BasicAuthentication and AdfsAuthentication. - ExchangeAdminCenter:BasicAuthentication and AdfsAuthentication. - RemotePowerShell:BasicAuthentication and NonBasicAuthentication. - ExchangeActiveSync:BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Test-DatabaseEvent | N/A | |
| Test-DataClassification | N/A | This cmdlet lets you know the classification results that are returned by the Microsoft classification engine in specific text. The classification results include the sensitive type, its count, and confidence. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Test-DataEncryptionPolicy | N/A | |
| Test-DlpPolicies | N/A | |
| Test-InformationBarrierPolicy | N/A | |
| Test-IRMConfiguration | N/A | The Test-IRMConfiguration cmdlet performs a series of steps to test IRM configuration and functionality, including availability of an Active Directory Rights Management Services (AD RMS) server, prelicensing and journal report decryption. In Exchange Online organizations, it checks connectivity to RMS Online and obtains and validates the organizations Trusted Publishing Domain (TPD). You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Test-M365DataAtRestEncryptionPolicy | N/A | You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if theyre not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| Test-MailboxAssistant | N/A | |
| Update-VivaModuleFeaturePolicy | N/A | Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module in Viva. This cmdlet updates the attributes of the policy that you specify. These attributes include: - The policy name (Name parameter). - Whether or not the policy enables the feature (IsFeatureEnabled parameter). - Whether or not the policy enables user controls (IsUserControlEnabled parameter, only applicable to a feature policy). - Who the policy applies to (the UserIds and GroupIds parameters or the Everyone parameter). You can update these attributes independently of each other. For example, if you specify the Name parameter but not the IsFeatureEnabled parameter, the name of the policy is updated but whether or not the policy enables the feature remains unchanged. Important : Values that you specify for the UserIds and/or GroupIds parameters or the Everyone parameter overwrite any existing users or groups. To preserve the existing users and groups, you need to specify those existing users or groups and any additional users or groups that you want to add. Not including existing users or groups in the command effectively removes those specific users or groups from the policy. For more information, see the examples. You need to use the Connect-ExchangeOnline cmdlet to authenticate. This cmdlet requires the .NET Framework 4.7.2 or later. Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. To learn more about assigned roles at the feature level, see Features Available for Feature Access Management (https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). To learn more about administrator role permissions in Microsoft Entra ID, see Role template IDs (https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). [!IMPORTANT] Microsoft strongly advocates for the principle of least privilege. Assigning accounts only the minimum permissions necessary to perform their tasks helps reduce security risks and strengthens your organizations overall protection. Global Administrator is a highly privileged role that you typically limit to emergency scenarios or when you cant use a different role. |