Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell

Hairyken ,

I found the same thing for the -DelegatedOrganization  parameter as well! If you use the Customer Tenant ID you get the same error:

Get-Mailbox -ResultSize Unlimited

Returns: "Write-ErrorMessage : Expired or Invalid pagination request. Default Expiry time is 00:30:00"

But if you use the Customer's .onmicrosoft.com domain it works. If you use the Customer's Primary Domain Name (which is often the onmicrosoft domain, but is sometimes their custom/vanity domain, eg. abccompany.com) it will work ... BUT many ExO V3 cmdlets that write/change/delete data will throw an error. So you'll need to connect to AzureAD / MS Graph to find the Customer's .onmicrosoft.com domain and use that.

This is for MSP's / CSPs using the Partner Center and using DAP or GDAP (delegated privileges), which is important as the https://learn.microsoft.com/en-us/partner-center/announcements/2023-january#exchange-online-automation-affecting-change-on-march-31-2023. And unfortunately the official https://learn.microsoft.com/en-ca/powershell/partnercenter/exchange-online-gdap-app?view=partnercenterps-3.0 is wrong, it says use the Customer Tenant ID. Hopefully it gets fixed soon, I'll submit feedback and see.

There's a thread about this over on the https://www.microsoftpartnercommunity.com/t5/Secure-Application-Model/Retirement-of-the-Legacy-Exchange-Online-Public-Client-ID-app-ID/m-p/84770.  Which also means my comment to this thread from Jan 10th, 2023 has been solved: the App-only auth for unattended Exch Online PowerShell works using the ExO V3 module (3.1.0+) and our Secure App Refresh Token.

Also wanted to add: I noticed the "Get-DistributionGroupMember" cmdlet (and maybe others) no longer supports the -ErrorAction parameter. Any idea why and if that can be fixed?

Commenting in case anyone else runs into this.

   --Saul