Enable-PushNotificationProxy

 

Applies to: Exchange Server 2016

This cmdlet is available only in on-premises Exchange Server 2016.

Use the Enable-PushNotificationProxy cmdlet to enable a push notification proxy between an on-premises Microsoft Exchange organization and a Microsoft Office 365 organization.

importantImportant:
In order for event notifications to be successfully delivered, you also need to configure OAuth authentication between your on-premises Exchange organization and your Office 365 organization.

For information about the parameter sets in the Syntax section below, see Syntax.

Enable-PushNotificationProxy [-Confirm [<SwitchParameter>]] [-Organization <String>] [-Uri <String>] [-WhatIf [<SwitchParameter>]]

This example displays the status of the push notification proxy in the on-premises Exchange organization.

Enable-PushNotificationProxy -WhatIf

This example enables the push notification proxy in the on-premises Exchange organization by using the Office 365 organization contoso.com.

Enable-PushNotificationProxy -Organization contoso.com

The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Office 365 to OWA for Devices on the user's device.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Push notification proxy settings" entry in the Clients and mobile devices permissions topic.

 

Parameter Required Type Description

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • 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.

Organization

Optional

System.String

The Organization parameter specifies the domain name of the Office 365 organization. For example, contoso.com.

Uri

Optional

System.String

The Uri parameter specifies the push notification service endpoint in Office 365. The default value is https://outlook.office365.com/PushNotifications.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Show: