Your migration itself looks successful since the batch is completed and the public folder hierarchy is visible in PowerShell. The issue is most likely configuration-related. The key problem is that PublicFoldersEnabled is still set to Local, which tells Exchange that public folders are on-premises, so Outlook and OWA won’t load them from Exchange Online. If you’ve fully migrated to Exchange Online, this should be set correctly (typically to Remote in hybrid scenarios). Also make sure users have a DefaultPublicFolderMailbox assigned, otherwise the folders won’t appear. The “well-known domain missing” error only affects mail-enabled public folders and is not critical if you don’t need external mail flow. You can check this guide for more information.
