Exchange Online provides an Online interface, in the Exchange Admin Center, to run, manage and track mailbox migrations. In it you define endpoints and upload (CSV) migration batches. The status of these batches, which run unattended, is then viewable from the Exchange Admin Center no matter from where you are. This is vastly superior to the way the SharePoint Migration Tool currently works, as installed on a desktop client.

With regards to defining a SharePoint Migration endpoint on-premises, from the SharePoint Admin Center, please consider the Azure AD Application Proxy scenario, where you can download a black-box installer which you install on an on-premises machine, which creates a reverse proxy to Azure/Office 365. The user doesn't need to configure anything on-premise, just log in with the Azure AD Global Admin and it downloads the information automatically. Again, this tool is managed from the Online interface.

I would LOVE a SharePoint Migration tool in the Online Admin Center, where I can manage the batches Online. If I need connectivity to on-premise fileshares or SharePoint, all I would have to do is install a 'generic black-box' exe, log in with the SharePoint Online Admin account which configured the Migration... and all the settings and batches start to run through the reverse proxy automatically!

I love the layout of the new Site Page content type, with end-user friendly editing options, super easy and intuitive document and video embedding options and easier than ever picture inserting. It is perfect solution for when end-users (even not power users) have to author wiki pages in a SharePoint site. When inserting a picture, you do not need to choose in which library it will be uploaded and you don't have to fill any meta-data. The same with attaching documents. Even more - Office documents get automatically embedded in the page. Now you can have some text and embedded PowerPoint presentation together and ANY end-user is able to do this in just few moments.

HOWEVER, this functionality is ONLY available when clicking on gear and choosing to "Add a new page". When going directly to Site Pages or having a web-part of Site Pages and clicking on New, you still get the old site page edit layout.

Furthermore, when trying to add Site Page to custom document library or Wiki library (in SP Designed) and then trying to create a new page, it gets saved in Site Page library. No matter what. Tried copying site page from Site Pages library to custom document library with the same content type added, result was that the page was copied, but when opening it, it was empty. Tried creating a new site content type inheriting from Site Page, that did not help. Tried to fool SharePoint in all ways I could think off. Not possible.

In the end, we will not use this new site page layout, because we do not need end-users creating new pages in Site Page library, because they are not able to find them afterwards, we can not provide separate libraries for each department, team or project. Therefore we can not use specific library permissions, target audiences, and so on.

It looks and feels nice, but everything around this new update makes it useless. If this would be fixed, it would one of the best things for end-user experience.

Other things not working good:
* after saving the page does not show the title.
*It is not possible to view the canvas column in a list view, like it is possible to do with Wiki content column of Wiki page.

Monitoring and troubleshooting hybrid search is difficult and near impossible. Can we get more visibility into the hybrid connection and try to answer some of these questions?
1) How many items are in my O365 index, internal vs external? Did you know there's a 1M items from an external search limit per 1TB of SPO storage? Am I close? How much do I have now?
2) Why aren't my items showing up in the cloud search? Is this farm connected? When was the last successful push? What else might I need to know to fix this?
3) Can I remove orphaned items? Currently have to submit a support ticket

A useful addition to the SharePoint Migration Tool would be to support the option for excluding paths in a file share to SharePoint migration scenario. It would be very useful to put an exclude symbol "-" in front of a mapping while building the .csv. In this way you are able to migrate the only what you really need. Example: a library with 50 folders and you need 48 of them. In the current version you migratie everything and in a post migration step you need to manually find and delete these 2 folders. Or I need to add 48 mappings within the .csv.

Our goal is to enable Extranet connectivity for SharePoint 2019 with support for the OneDrive Synchronization client (also known as the Next Generation Synch Client - NGSC).

During our investigation we found that, while the NGSC worked successfully with NTLM authentication worked, it did not work with SAML claims authentication.

SharePoint 2019 supports the use of SAML 1.1 but the NGSC does not. The product group is investigating the possibility of adding that feature but currently there is no ETA.
During our call with MS Support we verified that the NGSC does not even pass cookies;
However when we are using persistent cookies, we successfully mapped a network drive to the OneDrive share but this is not the desired user experience.

Currently you can create an Office 365 Group for a project and it comes with a "Files" section to share files. Well, the group's project is done and you want to move or copy those files to a more public repository on Office 365 Sharepoint. However, there is no may to multi-select files/folders and move/copy from the Groups to Sharepoint. This is a huge need as it exposes the file to the whole company for discovery whereas Groups are usually a limited audience. If you are a Mac user, you don't have the Windows Explorer option either. This should be easy and all web based on every browser.