> You must temporarily enable WinRM to run the following commands. You can enable WinRM by running the command: `winrm quickconfig`.

To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in PowerShell):

```dos

If you don't see the value `Basic = true`, you need to run this command **in a Command Prompt** (not in PowerShell) to enable Basic authentication for WinRM:

```dos

```

**Note**: If you'd rather run the command in PowerShell, enclose this part of the command in quotation marks: `'@{Basic="true"}'`.

If Basic authentication for WinRM is disabled, you'll get this error when you try to connect:

This cmdlet updates the mailbox object that's specified by the Identity parameter.

This example shows details about the compliance search action named "Case 1234\_Preview"

- Name: The compliance search action name uses the syntax `"Compliance Search Name\_Action"`. For example, `"Case 1234\_Preview"`.

Use the Get-RMSTrustedPublishingDomain cmdlet to view the settings of an existing trusted publishing domain (TPD) in your organization.

**Note**: We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell).

A trusted publishing domain contains the settings needed to use RMS features in your organization. For example, users can apply RMS templates to email messages.

This example lists all the trusted publishing domains that are configured in your organization and shows detailed information for each trusted publishing domain.

The Default switch filters the results by the default trusted publishing domain. You don't need to specify a value with this switch.

The default trusted publishing domain displays RMS templates and provides rights protection to all new content. There can be only one default trusted publishing domain in an organization.

Type: SwitchParameter

Position: Named

Accept pipeline input: False

Type: RmsTrustedPublishingDomainIdParameter

Position: 1

Accept pipeline input: True

Use the Import-RMSTrustedPublishingDomain cmdlet to import a trusted publishing domain (TPD) from an on-premises server running Active Directory Rights Management Services (AD RMS) or from RMS Online into your cloud-based organization.

**Note**: We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell).

A TPD contains the settings needed to use RMS features in your organization. For example, users can apply RMS templates to email messages. After you export the TPD from an on-premises AD RMS server to an XML file, you can import the XML file into your cloud-based organization.

If the InternalLicensingEnabled parameter value is $true on the Set-IRMConfiguration cmdlet, all TPDs require a private key. If the InternalLicensingEnabled parameter value is $false, TPDs don't require a private key. However, the only RMS feature available to the organization is Outlook protection rules. Typically, TPDs without private keys are created when the AD RMS server uses a hardware-based cryptographic service provider (CSP) or a custom CSP.

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 they're 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).

This example imports a TPD from an AD RMS server into a cloud-based organization. The TPD uses the following values:

- Path to exported XML file: C:\\My Documents\\Contoso.xml

- Password of exported XML file: Pa$$word1

- External licensing URL: `https://rms.contoso.com/_wmcs/licensing`

- Internal licensing URL: `https://RMS01/_wmcs/licensing`

- TPD name: Contoso TPD

The ExtranetLicensingUrl parameter specifies the external licensing URL of the on-premises AD RMS server that's stamped into the publishing license. The publishing license specifies the users that can open the rights-protected content, under which conditions the content may be opened by the user, and the rights that each user will have to the rights-protected content.

By default, the value of the ExtranetLicensingUrl parameter is `https://<FQDN>/_wmcs/licensing`.

Type: Uri

Parameter Sets: IntranetLicensingUrl, ImportFromFile

Position: Named

- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.

- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.

When you add, modify, or remove RMS templates in a TPD on the AD RMS server, you export the updated TPD to a new XML file, and import the new XML file in your cloud-based organization. The RefreshTemplates switch uses the following rules:

- Only the FileData, Password, and Name parameters are required. The value of the Name parameter must match the name of the previously imported TPD.

- If the new XML file doesn't contain an RMS template that was defined in the previously imported TPD, the RMS template is removed from the cloud-based organization.

- If the new XML file contains an updated RMS template that was defined in the previously imported TPD, the RMS template settings are updated in the cloud-based organization. However, the RMS template isn't changed from Archived to Distributed or vice versa.

- If the new XML file contains an RMS template that wasn't imported in the original TPD, the RMS template is added to the cloud-based organization in the Archived state. To make the new RMS template usable, you must change its state from Archived to Distributed using the Set-RMSTemplate cmdlet.