In some scenarios it is required to put a site in read only-mode, for example a project site, or to simply just remove access to it.
From the SharePoint Online Admin Center there is no way to lock your site, or to put it in read-only. There are two ways to achieve this, one is through Powershell, the other one through the Site Settings of your Site Collection.
A customer of mine had the need to get an overview of all the checked out documents for a given Site Collection, and to check them in afterwards prior to a content migration from SharePoint 2013 to SharePoint Online.
Since no out of the box features exist to accomplish this goal, I had to write a Powershell-script to find all the checked out documents in a Site Collection.
You can find the script here. It works for SharePoint Online as for SharePoint 2013. I did not test it with SharePoint 2010.
Recently I had the requirement to embed an external website onto a modern page on a SharePoint Online site. Fine, that’s no problem at all. This is available out-of-the-box on a modern page, right?
While Microsoft has been promoting the usage of metadata and views above folders in SharePoint document libraries, Microsoft Teams lacks these possibilities. It gives you a full list of documents in that document library, but with no metadata, no views and no filtering.
As technology is evolving into a more and more client-side experience, JavaScript is becoming a substantial part in SharePoint implementations. With JavaScript you can build rich, fast, interactive user experiences on the client with responsive interfaces that run in browsers as well as a hybrid, native HTML experience on phones.
SharePoint fully embraces this trend, and has released the SharePoint Framework (SPFx). A Page and Part model that enables fully supported client-side development, easy integration with the Microsoft Graph and support for open source tooling. The new experiences for the new mobile app, SharePoint Online and OneDrive for Business, including the new document library and list experiences are built using the SharePoint Framework.
Recently I cam across an unsupported scenario with Microsoft Teams. I logged in with an Office 365-account on which Teams is not enabled, giving me the following screen:
Translated, that is: “You’re missing out! Ask your IT administrator for access to Microsoft Teams.”
Microsoft Teams brings together the full breadth and depth of Office 365 to provide a true hub for teamwork. Word, Excel, PowerPoint, SharePoint, OneNote, Planner, Power BI and Delve are all built into Microsoft Teams so people have all the information and tools they need at their fingertips. It is available for Office 365 Business Essentials, Business Premium, and the Enterprise E1, E3, and E5 plans.
It puts itself in a strong competitive position against Slack.
You’re looking to set up an international Office 365 environment, and cannot find anything about it? That’s correct, because there is nothing like that at all. Neither a guide with best practices.
Some people suggest to set up a tenant on each continent. Give this a thought for a minute, and you can come up with even more questions.
From my point of view, setting up only one tenant is just fine. The only thing you might take in mind is setting one up on the continent on which the biggest part of your users reside.
© 2017 Laurent Schoenaers