Ever wanted to explain Office 365 to someone, and all of its features, not knowing where to start? I find the infographic below very useful to share with customers.
I like to think of Office 365 as an actual ecosystem. It’s a living environment. Applications might change of name, icons change, they might disappear, others get introduced. The features within applications are always enhancing as well. No one can ever say “I know everything in Office 365”. It’s an endless changing – maybe evolving is the better word here – cloud solution.
Hence the need for continuous change and training of end users. But that’s content for some other blogpost, back to the awesome infographic!
In a lot of cases you need to assign, remove or select which services in a license to assign to all of your users in one shot. Thru the UI it is a huge amount of work, consider environments with more than 5k users, which can easily be automated with Powershell.
In order to assign, remove and select which services to assign to all your users, you can use the script here-under.
When enabling the Teams license in Office 365, every member within the organisation can create Teams. To prevent uncontrolled growth of Teams, it is a best practice to disable the creation of Teams and put in place a provisioning engine instead.
What are citizen developers? Citizen developers are non-IT professionals that take business application development into their own hands. They utilize applications, productivity tools and low-code platforms to make up for a lack of programming languages.
In SharePoint Online, for a list or document library, it is possible to define default metadata values based on the folder where an item or document is added.
As with a lot of cases in SharePoint, the defaults are set on subfolders with inheritance. On every folder-level it is possible to break the inheritance and define other default values for your metadata.
In the example below we work with a Managed Metadata field, called customer, we need to default. This way our co-workers don’t need to specify the value everytime they create or upload a document to the document library.
There are two ways to make the magic happen. Through the user interface, and with Powershell.
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.