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.

Manipulation on Microsoft Word Documents grammatically are very actual. Microsoft does not support "Word Object Model" on unattended scenarios, and Microsoft always make reference to OpenXMLSDK and Sharepoint Word Automation Services.

There is problem OpenXMLSDK is a library, Word Automation Services is not.

In many cases we developers besides manipulation of docx files, we also need convert them to other word supported format.

For that we have to install Windows 2016, Full SharePoint Server to have ability convert files. You may agree, this is too have for just for conversion tasks.

Please make Word Automation Services as Standalone Library (Even not open Source).

I just wanted to share my thoughts about that the Microsoft Will No Longer Offer A Public Site Option in Office 365 (SPO).
In this case I have to looking for a SP based provider for extra money.
This is not the first time when a service/option disappear from the O365 – of course we got extra storage and another new features.

In the past (in my old/previous tenant) I had a connection between Intra, OneDrive and the Public Site. I used it for SP List (Anonymous) sharing and complete Folder (Anonymous) sharing – without duplications.
Now, this is not possible at all. If I want to share a folder including files I have to copy them to the new place and I do not want o share files one-by-one or duplicate them.

In 2013 I left the Google Apps because the MS provided something great, a complex Service including everything. I have just only one tenant for my business and this is not so important for MS.
I am extremely disappointed!!!

The new document library experience looks great but it has couple of issues.

1. User gets the old experience when clicking on a document set. This is a bit disappointing as we are
suggesting the clients do not use folders and use document sets with metadata instead.

2. The top navigation within the new document library experience does not display the site navigation correctly. I would expect it to
display the same Global Navigation as the Site which the user has just come from.

I hope Microsoft update the document set experience soon so that we can guide our clients in the right direction.

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

Need the document deletion policy to run as advertised in the MS Article -->

https://support.office.com/en-us/article/Overview-of-document-deletion-policies-55e8d858-f278-482b-a198-2e62d6a2e6e5?ui=en-US&rs=en-US&ad=US&fromAR=1

At the moment there's no way to guarantee it would run, when would it run, even if it runs whether it would delete items as mentioned in the criteria etc. The first time it runs it indexes and expires the data. The second time it runs (which could be in 1 week, 2 weeks, God knows when) it would delete the data - that too there's no guarantee. I mean this is damn stupid & really lame. Why create a feature that doesn't work at all like it should especially when its advertised.

MS says that its a low priority job & that there's no way to guarantee its execution. Why the heck would do something like that? The priority of the job should be basis the customer's requirement and not what MS thinks it should be. Why should the customer pay for extra storage that he doesn't want to pay for. Aren't you cheating your customer's when you do that???