Deprecation of Remote PowerShell in Exchange Online – Re-enabling or Extending RPS support

Hello Nino_Bilic 

I've run the self service tool today, I've seen that the RPS status changed from "blocked to "not blocked" but I still cannot connect.

I have an hybrid environment and I need to finish the migration of public folders from Exchange 2013 installed on Windows server 2012 R2 which is using .NET framework 4.8 with CU23. So I cannot update to .NET Framework 5 because it's not supported and I cannot run the sync anymore because the scripts must run on Exchange servers (https://learn.microsoft.com/en-us/exchange/hybrid-deployment/set-up-modern-hybrid-public-folders).

I found that there 3 commands used by this script New-syncmailpublicfolder, remove-syncmailpublicfolder and Set-MailPublicFolder but the first 2 ones are clearly mentioned on Microsoft support site that they should not be used directly (https://learn.microsoft.com/en-us/powershell/module/exchange/new-syncmailpublicfolder?view=exchange-ps)

One workaround solution is to install a new exchange server on prem but I'm near the end so I don't want to install a new one right now

My first point is why I still cannot use RPS connections even after using the self service tool ? 

and the second one is how can I do the move of PF if I cannot use RPS ?

Thanks in advance

Joseph