To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet.

Use the Set-MailboxImportRequest cmdlet to change import request options after the request has been created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. Use the Set-MailboxPlan cmdlet to modify the settings of mailbox plans in the cloud-based service.

Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request has been created. You can use this cmdlet to recover from failed restore requests. Use the Set-Place cmdlet to update room mailboxes with additional metadata, which provides a better search and room suggestion experience.

To modify these properties except GeoCoordinates on synchronized room mailboxes, use the Set-User or Set-Mailbox cmdlets in on-premises Exchange. Use the Set-ResourceConfig cmdlet to create custom resource properties that you can add to room and equipment mailboxes. Use the Set-UserPhoto cmdlet to configure the user photos feature that allows users to associate a picture with their account. User photos appear in on-premises and cloud-based client applications, such as Outlook on the web, Lync, Skype for Business, and SharePoint.

Use the Suspend-MailboxExportRequest cmdlet to suspend an export request any time after the request was created, but before the request reaches the status of Completed.

You can resume the request by using the Resume-MailboxExportRequest cmdlet. Use the Suspend-MailboxImportRequest cmdlet to suspend an import request any time after the request was created, but before the request reaches the status of Completed. You can resume the move request by using the Resume-MailboxImportRequest cmdlet.

Use the Suspend-MailboxRestoreRequest cmdlet to suspend a restore request any time after the request was created, but before the request reaches the status of Completed. You can resume the restore request by using the Resume-MailboxRestoreRequest cmdlet. Use the Test-MapiConnectivity cmdlet to verify server functionality by logging on to the mailbox that you specify.

If you don’t specify a mailbox, the cmdlet logs on to the SystemMailbox on the database that you specify. Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. Mailboxes can be recovered within 30 days of being deleted. Use the Add-ResubmitRequest cmdlet to add requests to replay redundant copies of messages from Safety Net after a mailbox database recovery.

Use the Export-Message cmdlet to copy a message from a queue on a Mailbox server or an Edge Transport server to a specified file path in your organization. Use the Get-AcceptedDomain cmdlet to view the configuration information for the accepted domains in your organization. Use the Get-AddressRewriteEntry cmdlet to view an existing address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server.

Use the Get-DeliveryAgentConnector cmdlet to retrieve information about a specific delivery agent connector in your organization. Use the Get-EdgeSubscription cmdlet to retrieve information about Edge Subscriptions in your organization.

Use the Get-EdgeSyncServiceConfig cmdlet to retrieve the edge synchronization services settings that control the general synchronization behavior shared by all Microsoft Exchange EdgeSync services. Use the Get-ForeignConnector cmdlet to view the configuration information for a Foreign connector in the Transport service of a Mailbox server. Use the Get-InboundConnector cmdlet to view the settings for an Inbound connector in your cloud-based organization. Use the Get-Message cmdlet to view the details of one or more messages in queues on Mailbox servers or Edge Transport servers.

Use the Get-MessageTrace cmdlet to trace messages as they pass through the cloud-based organization. Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message.

Note that these detailed results are returned less quickly than the Get-MessageTrace results. Use the Get-MessageTrackingLog cmdlet to search for message delivery information stored in the message tracking log. Use the Get-MessageTrackingReport cmdlet to return data for a specific message tracking report. This cmdlet is used by the delivery reports feature. Use the Get-NetworkConnectionInfo cmdlet to view the network configuration information for all network adapters configured on the local server.

Use the Get-OutboundConnector cmdlet to view the configuration information for an Outbound connector in your cloud-based organization. Use the Get-Queue cmdlet to view configuration information for queues on Mailbox servers or Edge Transport servers.

Use the Get-QueueDigest cmdlet to view information about message delivery queues across database availability groups DAGs Active Directory sites, or Active Directory forests in your organization. By default, the Get-QueueDigest cmdlet displays delivery queues that contain ten or more messages, and the results are between one and two minutes old. For instructions on how to change these default values, see Configure Get-QueueDigest. Use the Get-RemoteDomain cmdlet to view the configuration information for the remote domains configured in your organization.

You can view the remote domain configuration from inside the Exchange organization or from an Edge Transport server in the perimeter network. Use the Get-ResubmitRequest cmdlet to view requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. Use the Get-RoutingGroupConnector cmdlet to view the configuration details of the routing group connectors in a Microsoft Exchange Server organization.

Use the Get-SystemMessage cmdlet to view default or custom system messages. System messages are delivery status notifications also known as DSNs, non-delivery reports, NDRs or bounce messages and quota messages. Use the Get-TransportServer cmdlet to view settings that are associated with the Hub Transport server role or the Edge Transport server role.

For more information about how to configure an X. Use the New-AcceptedDomain cmdlet to create an accepted domain in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. Use the New-AddressRewriteEntry cmdlet to create an address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server.

Use the New-EdgeSyncServiceConfig cmdlet to create edge synchronization service settings that control the general synchronization behavior shared by all EdgeSync services.

Use the New-InboundConnector cmdlet to create a new Inbound connector in your cloud-based organization. Use the New-OutboundConnector cmdlet to create a new Outbound connector in your cloud-based organization. Use the New-RemoteDomain cmdlet to create a managed connection for a remote domain.

When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies and specify acceptable character sets for messages sent to and received from the remote domain. Use the New-RoutingGroupConnector cmdlet to establish a connection between a Microsoft Exchange Server routing group and an Exchange Server routing group when the organization is running more than one version of Exchange. Use the New-SystemMessage cmdlet to create custom system messages.

The X. Use the Redirect-Message cmdlet to drain the active messages from all the delivery queues on a Mailbox server, and transfer those messages to another Mailbox server. Use the Remove-AcceptedDomain cmdlet to remove an accepted domain. When you remove an accepted domain, the accepted domain object is deleted. Use the Remove-AddressRewriteEntry cmdlet to remove an existing address rewrite entry that’s no longer needed on an Edge Transport server.

The Remove-DeliveryAgentConnector cmdlet removes a specific delivery agent connector configured in your organization. Use the Remove-InboundConnector cmdlet to delete an Inbound connector from your cloud-based organization.

Use the Remove-Message cmdlet to delete a message from a queue on a Mailbox server or an Edge Transport server. Use the Remove-OutboundConnector cmdlet to delete an Outbound connector from your cloud-based organization. Use the Remove-RemoteDomain cmdlet to remove a remote domain.

When you remove a remote domain, the remote domain object is deleted. Removing a remote domain doesn’t disable mail flow to that domain. Use the Remove-ResubmitRequest cmdlet to remove requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. Use the Remove-RoutingGroupConnector cmdlet to remove a routing group connector between a Microsoft Exchange Server routing group and an Exchange Server routing group.

Use the Remove-SystemMessage cmdlet to remove custom system messages. When you remove an X. Use the Resume-Message cmdlet to enable delivery of a previously suspended message in a queue on a Mailbox server or Edge Transport server. Use the Resume-Queue cmdlet to restart processing for a suspended queue on a Mailbox server or an Edge Transport server.

Use the Retry-Queue cmdlet to force a connection attempt for a queue on a Mailbox server or an Edge Transport server. Use the Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information.

For more information, see Get-MessageTrackingReport. The message tracking report cmdlets are used by the delivery reports feature. Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. Use the Set-AddressRewriteEntry cmdlet to modify an existing address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server.

Use the Set-DeliveryAgentConnector cmdlet to configure a specific delivery agent connector in your organization.

Use the Set-EdgeSyncServiceConfig cmdlet to modify the configuration of edge synchronization service settings that control the general synchronization behavior shared by all EdgeSync services. Use the Set-ForeignConnector cmdlet to modify an existing Foreign connector in the Transport service of a Mailbox server. Use the Set-InboundConnector cmdlet to change an existing Inbound connector in your cloud-based organization. Use the Set-OutboundConnector cmdlet to modify an existing Outbound connector in your cloud-based organization.

Use the Set-ResubmitRequest cmdlet to enable or disable requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. Use the Set-RoutingGroupConnector cmdlet to modify the properties of an existing routing group connector between a Microsoft Exchange Server routing group and an Exchange Server routing group. You can also use this cmdlet to configure the maximum message size that can pass across a routing group connector.

Use the Set-SystemMessage cmdlet to modify custom system messages. Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Exchange organization.

Use the Set-TransportServer cmdlet to modify settings that are associated with the Hub Transport server role or the Edge Transport server role.

Use the Set-TransportService cmdlet to modify the settings of the Transport service on Exchange or later Mailbox servers or Edge Transport servers. Use the Start-EdgeSynchronization cmdlet to immediately start synchronization of configuration data from Active Directory to the subscribed Edge Transport servers.

Use the Stop-HistoricalSearch cmdlet to stop an existing historical search that has a status value of NotStarted. Use the Suspend-Message cmdlet to prevent delivery of a particular message in a queue on a Mailbox server or an Edge Transport server. Use the Suspend-Queue cmdlet to stop processing for a queue on a Mailbox server or an Edge Transport server.

Use the Test-EdgeSynchronization cmdlet to diagnose whether the subscribed Edge Transport servers have a current and accurate synchronization status. Use the Test-Mailflow cmdlet to diagnose whether mail can be successfully sent from and delivered to the system mailbox on a Mailbox server. You can also use this cmdlet to verify that email is sent between Mailbox servers within a defined latency threshold. Use the Test-SmtpConnectivity cmdlet to diagnose whether an SMTP connection can successfully be established to the Receive connectors on a specific server.

Although you can run this cmdlet manually to verify SMTP connectivity for a specified server, it’s primarily used by Microsoft System Center Operations Manager to test your transport servers’ ability to receive SMTP connections to each of the bindings on all the Receive connectors on those servers. Use the Validate-OutboundConnector cmdlet to test the settings of Outbound connectors in Microsoft Note : This cmdlet does not set the validation status or timestamp on the connector.

Use the Complete-MigrationBatch cmdlet to finalize a migration batch for a local move, cross-forest move, or remote move migration that has successfully finished initial synchronization. The Export-MigrationReport is used by the Exchange migration process to enable an administrator to download a CSV file that contains migration errors for a selected migration batch.

This cmdlet isn’t run by an administrator in Windows PowerShell. Use the Get-MigrationBatch cmdlet to retrieve status information about the current migration batch. Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers. Use the Get-MigrationEndpoint cmdlet to retrieve migration endpoint settings for source or destination servers for cutover or staged Exchange migrations, IMAP migrations, and remote moves.

Use the Get-MigrationUserStatistics cmdlet to view detailed information about the migration requested for a specific user. Use the Get-MoveRequest cmdlet to view the detailed status of an ongoing asynchronous mailbox move that was initiated by using the New-MoveRequest cmdlet. Some of the failure messages that are returned by this cmdlet are temporary and don’t indicate that a request has actually failed.

If the Status value is Queued or InProgress, then the request is proceeding normally. Use the Get-PublicFolderMailboxMigrationRequest cmdlet to view the status of individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet.

Use the Get-PublicFolderMailboxMigrationRequestStatistics cmdlet to view the detailed status of individual jobs in a public folder migration batch created using New-MigrationBatch cmdlet.

Note : Support for serial migration of public folders ended in Exchange Cumulative Update 8 CU8 , and the cmdlets are no longer available in Exchange Online. Use the New-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and Google Workspace formerly G Suite migrations.

Use the New-MoveRequest cmdlet to begin the process of an asynchronous mailbox or personal archive move. You can also check mailbox readiness to be moved by using the WhatIf parameter. Note : After April 15, , you shouldn’t use this cmdlet to manually move mailboxes within an Exchange Online organization. You can only use this cmdlet for migrating to and from Exchange Online.

If you have issues with a mailbox and want to fix it by moving the mailbox within your Exchange Online organization, please open a Microsoft Support request instead. Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn’t change the logical hierarchy.

When the move request is completed, you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until the time specified in the CompletedRequestAgeLimit parameter has passed.

The request must be removed before you can run another move request. Be aware that the target public folder mailbox will be locked while the move request is active. See the Detailed Description section below for more details. Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn’t running or has been completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it.

Use the Remove-MigrationEndpoint cmdlet to remove existing migration endpoints for source or destination servers for cutover or staged Exchange migrations, IMAP migrations and remote moves. Use the Remove-PublicFolderMailboxMigrationRequest cmdlet to remove individual jobs from public folder migration batches that were created by using the New-MigrationBatch cmdlet. You need to use this cmdlet to remove an existing serial public folder migration request before you can create another one. After the move has been finalized, you can’t undo the move request.

Use the Resume-MoveRequest cmdlet to resume a move request that has been suspended or has failed. Use the Resume-PublicFolderMigrationRequest cmdlet to resume serial public folder migration requests requests created by the New-PublicFolderMigrationRequest cmdlet that have failed or have been suspended manually or automatically.

Use the Resume-PublicFolderMoveRequest cmdlet to resume a public folder move request that has been suspended or has failed. Use the Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see New-MigrationBatch. Use the Set-MigrationUser cmdlet to modify the migration settings of a user in an existing migration batch.

Use the Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. You can use this cmdlet to recover from failed migration requests. Use the Set-PublicFolderMoveRequest cmdlet to change a public folder move request after the move request has been created.

Use the Start-MigrationBatch cmdlet to start a move request or migration batch that was created with the New-MigrationBatch cmdlet.

Use the Start-MigrationUser cmdlet to start the migration of a user in an existing migration batch. Use the Stop-MigrationBatch cmdlet to stop the processing of a migration batch that’s in progress.

Use the Stop-MigrationUser cmdlet to stop the migration of a user in an existing migration batch. Use the Suspend-MoveRequest cmdlet to suspend a move request any time after the move request was created, but before it reaches the status of CompletionInProgress.

You can resume the move request by using the Resume-MoveRequest cmdlet. Use the Suspend-PublicFolderMailboxMigrationRequest cmdlet to suspend individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet. You can suspend active requests before they reach the status CompletionInProgress. Use the Suspend-PublicFolderMoveRequest cmdlet to suspend a move request any time after the move request was created, but before it reaches the status of CompletionInProgress.

Use the Test-MigrationServerAvailability cmdlet to test the availability of the target server in preparation to perform cross-forest mailbox moves, migration of on-premises mailboxes to Exchange Online, or to migrate on-premises mailbox data from an IMAP server to Exchange Online mailboxes.

For all migration types, the cmdlet attempts to verify the connection settings used to connect to the target server. You may be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization.

Note : Customer Lockbox is included in the Microsoft E5 plan. If you don’t have a Microsoft E5 plan, you can buy a separate Customer Lockbox subscription with any Microsoft Enterprise plan.

Use the Get-AuthenticationPolicy cmdlet to view authentication policies in your organization. Use the Get-AuthServer cmdlet to view the settings of authorization servers in the Exchange organization.

Use the Get-ExchangeDiagnosticInfo cmdlet to return information about processes that are running on Exchange servers. When you run the Get-ExchangeServer cmdlet with no parameters, it returns the attributes of all the servers in the Exchange organization. To return specific server properties including domain controller information where the Get-ExchangeServer cmdlet has to contact servers directly or perform a complex or slow calculation, make sure you use the Status parameter.

This refers to the specific legal name of the license, as defined in the Microsoft Product List and is representative of your licenses when you run this cmdlet. Use the New-ExchangeSettings to create the settings object, and the Set-ExchangeSettings cmdlet to define the actual settings. Use the Get-Notification cmdlet to view notification events that are shown in the notification viewer in the Exchange admin center EAC. These notification events are related to:.

Use the Get-PerimeterConfig cmdlet to view the list of gateway server and internal mail server IP addresses that have been added to the cloud-based safelists.

Use the Get-ServicePrincipal cmdlet to view information about service principals in your cloud-based organization. Caution : Incorrect usage of the setting override cmdlets can cause serious damage to your Exchange organization. This damage could require you to reinstall Exchange. Only use these cmdlets as instructed by product documentation or under the direction of Microsoft Customer Service and Support.

Use the Get-SettingOverride cmdlet to view existing setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. These policies are complementary to the permission scopes that are declared by the application. Exchange honors tokens issued by the authorization server for access by a partner application. Use the New-ExchangeSettings cmdlet to create customized Exchange setting objects that are stored in Active Directory.

Use the Set-ExchangeSettings cmdlet to configure the actual settings. Use the New-PartnerApplication cmdlet to create partner application configurations in on-premises Exchange organizations. Use the New-ServicePrincipal cmdlet to create service principals in your cloud-based organization.

Use the New-SettingOverride cmdlet to create setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes may take up to 30 minutes to go live. Use the Remove-AuthenticationPolicy cmdlet to remove authentication policies from your organization. Use the Remove-ServicePrincipal cmdlet to remove service principals from your cloud-based organization.

Use the Set-AccessToCustomerDataRequest cmdlet to approve, deny, or cancel Microsoft customer lockbox requests that control access to your data by Microsoft support engineers.

Note : Customer lockbox is included in the Microsoft E5 plan. If you don’t have a Microsoft E5 plan, you can buy a separate customer lockbox subscription with any Microsoft Enterprise plan. Use the Set-ApplicationAccessPolicy cmdlet to modify the description of an application access policy. Use the Set-AuthConfig cmdlet to modify the authorization configuration for your Exchange organization.

Use the Set-AuthServer cmdlet to configure an authorization server that partner applications can use to obtain tokens recognized by Microsoft Exchange. Use the Set-CmdletExtensionAgent cmdlet to modify cmdlet extension agents. Use the Set-Notification cmdlet to modify notification events that are shown in the notification viewer in the Exchange admin center EAC.

Use the Set-PartnerApplication cmdlet to configure partner application configurations in on-premises Exchange organizations. Use the Set-PerimeterConfig cmdlet to modify the list of gateway server IP addresses that have been added to the cloud-based safelists. Use the Set-SettingOverride cmdlet to modify setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. Use the Test-SystemHealth cmdlet to gather data about your Microsoft Exchange system and to analyze the data according to best practices.

Use the Update-ExchangeHelp cmdlet to find, download and install the latest available help topics for the Exchange Management Shell on the local computer. If an available version is found based your installed version and languages of Exchange, the cmdlet downloads and integrates the updated version of Help in the Exchange Management Shell.

This cmdlet is a required substitute for the Update-Help cmdlet that’s available in Windows PowerShell. Use the Disable-JournalArchiving cmdlet to disable journal archiving for specific users. Microsoft journal archiving uses mailboxes in Exchange Online to record or journal messages for mailboxes in on-premises organizations. Use the Disable-TransportRule cmdlet to disable transport rules mail flow rules in your organization.

Use the Enable-TransportRule cmdlet to enable transport rules mail flow rules in your organization. This allows the application of sensitivity labels to Microsoft Teams sites, Microsoft Groups, and SharePoint sites. This cmdlet is required if you were using sensitivity labels before September Use the Export-TransportRuleCollection cmdlet to export the transport rules in your organization. Use the Get-ActivityAlert cmdlet to view activity alerts in the Microsoft Defender portal or the Microsoft Purview compliance portal.

Activity alerts send you email notifications when users perform specific activities in Microsoft Use the Get-AdministrativeUnit cmdlet to view administrative units, which are Azure Active Directory containers of resources. You can use administrative units to delegate administrative permissions and apply policies to different groups of users. Use the Get-AutoSensitivityLabelPolicy cmdlet to view auto-labeling policy rules in your organization.

Use the Get-InformationBarrierPoliciesApplicationStatus cmdlet to view the application status of information barrier policies.

Use the Get-InformationBarrierPolicy cmdlet to view information barrier policies in the Microsoft Purview compliance portal. Use the Get-InformationBarrierRecipientStatus cmdlet to return information about recipients and their relationship to information barrier policies. Use the Get-MessageClassification cmdlet to view existing message classifications in your organization. Use the Get-OrganizationSegment cmdlet to view organization segments in the Microsoft Purview compliance portal.

Use the Get-OutlookProtectionRule cmdlet to retrieve Microsoft Outlook protection rules configured in an organization. Use the Get-ProtectionAlert cmdlet to view alert policies in the Microsoft Purview compliance portal.

Use the Get-TransportRuleAction cmdlet to view the actions that are available for transport rules mail flow rules. Use the Get-TransportRulePredicate cmdlet to view the predicates conditions and exceptions that are available for transport rules mal flow rules. You can import a journal rule collection you previously exported as a backup, or import rules you exported from an older version of Exchange.

Use the Import-TransportRuleCollection cmdlet to import a transport rule collection. You can import a rule collection you previously exported as a backup, or import rules that you’ve exported from an older version of Exchange. The Compliance Policy Center is a site collection that’s used by the Microsoft Purview compliance portal to store preservation policies that act on content in SharePoint Online sites.

Typically, you don’t need to run this cmdlet. You use this cmdlet for troubleshooting and diagnostics. Use the New-ActivityAlert cmdlet to create activity alerts in the Microsoft Defender portal or the Microsoft Purview compliance portal. Create auto-labeling policy rules using the New-AutoSensitivityLabelRule cmdlet and assoicate them with the policy to complete the policy creation. Use the New-AutoSensitivityLabelRule cmdlet to create auto-labeling rules and associate then with auto-labeling policies in your organization.

Use the New-InformationBarrierPolicy cmdlet to create information barrier policies in the Microsoft Purview compliance portal. Use the New-MessageClassification cmdlet to create a message classification instance in your organization. Use the New-OrganizationSegment cmdlet to create organization segments for use with information barrier policies in the Microsoft Purview compliance portal. Organization Segments are not in effect until you apply information barrier policies.

Use the New-ProtectionAlert cmdlet to create alert policies in the Microsoft Purview compliance portal. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries in the Microsoft Purview compliance portal. Use the New-SupervisoryReviewRule cmdlet to create supervisory review rules in the Microsoft Purview compliance portal.

Use the New-TransportRule cmdlet to create transport rules mail flow rules in your organization. Use the Remove-ActivityAlert cmdlet to remove activity alerts from the Microsoft Defender portal or the Microsoft Purview compliance portal.

Use the Remove-AutoSensitivityLabelPolicy cmdlet to remove auto-labeling policies from your organization. Use the Remove-AutoSensitivityLabelPolicy cmdlet to remove auto-labeling policy rules from your organization. Use the Remove-InformationBarrierPolicy cmdlet to remove information barrier policies from the Microsoft Purview compliance portal.

Use the Remove-MessageClassification cmdlet to delete an existing message classification instance from your organization. Use the Remove-OrganizationSegment cmdlet to remove organization segments from the Microsoft Purview compliance portal.

Use the Remove-ProtectionAlert cmdlet to remove alert policies from the Microsoft Purview compliance portal. Use the Remove-TransportRule cmdlet to remove transport rules mail flow rules from your organization. Use the Set-ActivityAlert cmdlet to modify activity alerts in the Microsoft Defender portal or the Microsoft Purview compliance portal. Use the Set-AutoSensitivityLabelPolicy cmdlet to modify auto-labeling policy rules in your organization.

Use the Set-InformationBarrierPolicy cmdlet to modify information barrier policies in the Microsoft Purview compliance portal. Use the Set-MessageClassification cmdlet to configure an existing message classification instance in your organization. Use the Set-OrganizationSegment cmdlet to modify organization segments in the Microsoft Purview compliance portal. Use the Set-ProtectionAlert cmdlet to modify alert policies in the Microsoft Purview compliance portal.

Note : You can’t use this cmdlet to edit default alert policies. You can only modify alerts that you created using the New-ProtectionAlert cmdlet. Use the Set-SupervisoryReviewRule cmdlet to modify supervisory review rules in the Microsoft Purview compliance portal. Use the Set-TransportRule cmdlet to modify existing transport rules mail flow rules in your organization. If you delete all conditions and exceptions from a rule, the rule action is applied to all messages. This can have unintended consequences.

For example, if the rule action is to delete the message, removing the conditions and exceptions could cause the rule to delete all inbound and outbound messages for the entire organization. Use the Start-InformationBarrierPoliciesApplication cmdlet to apply active information barrier policies in the Microsoft Purview compliance portal. Use the Stop-InformationBarrierPoliciesApplication cmdlet to stop the process of applying information barrier policies in the Microsoft Purview compliance portal.

Use the Get-AdminAuditLogConfig cmdlet to view the administrator audit logging configuration settings. Use the Get-AuditConfig cmdlet to view the auditing configuration in the Microsoft Purview compliance portal. The Get-AuditLogSearch cmdlet also returns audit log searches that are initiated whenever an administrator uses the Exchange admin center EAC to export audit logs.

Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts on-premises Exchange and the cloud and computer accounts on-premises Exchange only. You use the Set-MailboxAuditBypassAssociation cmdlet to enable this property to bypass mailbox audit logging. Use the Get-UnifiedAuditLogRetentionPolicy cmdlet to view the properties of the audit log retention policies in the Microsoft Defender portal or the Microsoft Purview compliance portal.

Use the New-AdminAuditLogSearch cmdlet to search the contents of the administrator audit log and send the results to one or more mailboxes that you specify. Use the New-MailboxAuditLogSearch cmdlet to search mailbox audit logs and have search results sent via email to specified recipients.

Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization in the Exchange admin center or by using cmdlets. Use the Search-MailboxAuditLog cmdlet to search mailbox audit log entries matching the specified search terms.

Use the Search-UnifiedAuditLog cmdlet to search the unified audit log. Pretty lame! Furthermore, just like its predecessor it also supports MFA so you can ensure your security remains intact. Using the -Scope CurrentUser parameter allows Powershell to install the module without administrator access.

As mentioned this was going to be a really quick note to show you how to Install Exchange Online Powershell Module so hopefully this articles explains that. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. If you don’t have the Exchange management tools installed on your local computer, you can use Windows PowerShell to create a remote PowerShell session to an Exchange server.

It’s a simple three-step process, where you enter your credentials, provide the required connection settings, and then import the Exchange cmdlets into your local Windows PowerShell session so that you can use them. We recommend that you use the Exchange Management Shell on any computer that you use to extensively administer Exchange servers.

You get the Exchange Management Shell by installing the Exchange management tools. We recommend that you use the Exchange Management Shell instead to get all the properties of this cmdlet. After you connect, the cmdlets and parameters that you have or don’t have access to is controlled by role-based access control RBAC.

For more information, see Exchange Server permissions. To use this version of Windows, you need to install the Microsoft. NET Framework 4. For more information, see Install the. Windows PowerShell needs to be configured to run scripts, and by default, it isn’t. You’ll get the following error when you try to connect:. Files cannot be loaded because running scripts is disabled on this system.

Provide a valid certificate with which to sign the files.

Meetio – Connect to Exchange Online using Powershell

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. The rest of this article explains how the module works, how to install and maintain the module, and the optimized Exchange Online cmdlets that are available in the module. When you report an issue at exocmdletpreview[at]service[dot]microsoft[dot]com , be sure to include the log files in your email message. The best way to avoid this issue is to use the CommandName parameter on the Connect-ExchangeOnline cmdlet to limit the cmdlets that are used in the session.

The module contains a small set of exclusive Exchange Online PowerShell cmdlets that are optimized for bulk data retrieval scenarios think: thousands and thousands of objects.

When you first open the module, you’ll only see these exclusive cmdlets. After you connect to your Exchange Online organization , you’ll see all of the familiar cmdlets that are available in Exchange Online PowerShell. The module use modern authentication for all cmdlets.

You can’t use Basic authentication in the EXO V2 module; however, you still need to enable the Basic authentication setting in WinRM as explained later in this article. The Exchange Online cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents, but the equivalent cmdlets are still available after you connect.

The connection-related cmdlets that are available in the EXO V2 module are listed in the following table:. Version 2. This Preview version improves upon the historical capabilities of the module with the following features:. This switch routes the command directly to the required Mailbox server, and might improve overall performance.

When you use the UseCustomRouting switch, you can use only the following values for identity of the mailbox:. Use the UseCustomRouting switch experimentally and report any issues that you encounter.

Specifically, version 2. If you have trouble using the EXO V2 module on other distributions of Linux, send email to the following address: exocmdletpreview[at]service[dot]microsoft[dot]com. The email address is purposefully obfuscated to avoid spam. If you connect to Exchange Online PowerShell from a network that’s behind a proxy server, v2. You need to use v2. PowerShell 7 on Windows requires version 2. Only version 2.

NET Framework 4. For more information, see Windows Management Framework 5. The settings described in this section are required in all versions of PowerShell on all operating systems.

PowerShell needs to be configured to run scripts, and by default, it isn’t. You’ll get the following error when you try to connect:. Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated PowerShell window a PowerShell window you open by selecting Run as administrator :.

For more information about execution policies, see About Execution Policies. As described earlier in this article , v2. WinRM needs to allow Basic authentication.

We don’t send the username and password combination, but the Basic authentication header is required to send the session’s OAuth token, since the client-side WinRM implementation has no support for OAuth. The following commands require that WinRM is enabled. To enable WinRM, run the following command: winrm quickconfig. If Basic authentication for WinRM is disabled, you’ll get one of the following errors when you try to connect:.

The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.

Having problems? Ask for help in the Exchange forums. Typically, you’ll want the latest public version of the module, but you can also install a Preview version if one is available. To install the latest public version of the module, run one of the the following commands:. For detailed syntax and parameter information, see Install-Module. If the module is already installed on your computer, you can run the following commands to see the version that’s currently installed and update it to the latest version from the PowerShell Gallery:.

Typically, you’ll want the latest public version of the module, but you can also upgrade to a Preview version if one is available. To upgrade to the latest public version of the module, run one of the following commands based on how you originally installed the module in an elevated PowerShell window vs.

Scope CurrentUser :. To upgrade to a Preview version of the module, you can upgrade to the latest available Preview version, or you can use the RequiredVersion parameter to upgrade to a specific Preview version.

Run one of the following commands based on how you originally installed the module in an elevated PowerShell window vs. To confirm that the update was successful, run the following commands to check the version information of the module that’s installed:. For detailed syntax and parameter information, see Update-Module. Be sure to close and re-open the PowerShell window before you attempt to update the ExchangeOnlineManagement module again.

To check your current settings in the Microsoft. To permanently enable strong cryptography in the Microsoft. NET Framework version 4. For more information, see SchUseStrongCrypto. No match was found for the specified search criteria and module name ‘ExchangeOnlineManagement’.

Try running Get-PSRepository to see all available registered module repositories. To fix this error, run the following command:. To uninstall the module, run one of the following commands based on how you originally installed the module in an elevated PowerShell window vs. For detailed syntax and parameter information, see Uninstall-Module. Traditional Exchange Online cmdlets return all possible object properties in their output, including many properties that are often blank or aren’t interesting in many scenarios.

This behavior causes degraded performance more server computation and added network load. You rarely if ever need the full complement of properties in the cmdlet output.

Instead of giving all properties equal importance and returning them in all scenarios, we’ve categorized specific related properties into property sets. Simply put, these property sets are buckets of two or more related properties on the cmdlet. You can use the PropertySets and Properties parameters together in the same command.

We’ve also included a Minimum property set that includes a bare minimum set of required properties for the cmdlet output for example, identity properties. Either way, the cmdlet output will contain far fewer properties, and the time it takes to return those results will be much faster. For example, after you connect to Exchange Online PowerShell , the following example returns only the properties in the Minimum property set for the first ten mailboxes.

In contrast, the output of the same Get-Mailbox command would return at least properties for each of the first ten mailboxes.

Although the PropertySets parameter accepts the value All, we highly discourage using this value to retrieve all properties, because it slows down the command and reduces reliability.

Always use the PropertySets and Properties parameters to retrieve the minimum number of properties that are required for your scenario. Unless otherwise noted, the current release of the EXO V2 module contains all features of previous releases. Although the cmdlets are available in the module, the feature is only available to members of a Private Preview. For more information, see PowerShell 7 log in experiences. Additionally, you can configure access at feature level. For more information, see Configure MyAnalytics.

Real-time policy and security enforcement in all user based authentication. Read more about CAE here. The interactive sign-in process now uses a more secure method to fetch access tokens using safe reply URLs. Cannot invoke the pipeline because the runspace is not in the Opened state.

Current state of the runspace is ‘Closed’. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode. Table of contents. Note The settings described in this section are required in all versions of PowerShell on all operating systems.

Note As described earlier in this article , v2. Note The following commands require that WinRM is enabled. Tip Having problems? Note Although the PropertySets parameter accepts the value All, we highly discourage using this value to retrieve all properties, because it slows down the command and reduces reliability. Note Although the cmdlets are available in the module, the feature is only available to members of a Private Preview.

Submit and view feedback for This product This page. View all page feedback.