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 Office 365, every user can change their preferred language through the Office 365 settings.
Except when you are a synced user.
For synced users (your on-premise AD account is synced to Office 365), the language set in the on-premise AD will be used in Office 365 as well. With no way to change the language in Office 365.
Even if you would want to force it with PowerShell, you would get an exception.
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.
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?
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.
- You can only use your domainname on one tenant, how to handle the other tenants?
- What to do with multiple SharePoint Online, OneDrive for Business and Yammer tenants, thinking in terms of replicating data?
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.