It might be useful from time to time, and depending on the business requirements, to create custom permissions in SharePoint. Best practice would want to copy (or duplicate) a default permission already in SharePoint (and not modify any built-ins), and then add/remove whatever you don’t need. In this blog post, we are going to use SharePoint PowerShell PnP to create custom permissions for multiple Sites in SharePoint Online. Before… For brand new sites, this is what we’ve got as built-in permissions under Site Permissions –> Permission Levels (in the ribbon):
Recently, I had a request to find every files in a specific SharePoint Online site that are 50Mb or bigger. Which I thought “this should be straight forward with conditions in my script“. Well, turned out it wasn’t that straight forward after all. And I needed to be a bit “creative”. When using the PowerShell PnP module, a few outputs are either not the ones you expect, or the type is different.
Recently, I had to create a SharePoint folder structure extracted from a file share. I only wanted the structure, and not the files. So I had the local part to extract what I needed, and then I thought “sure I’ll use PowerShell PnP with a foreach loop, and done!” Well, surprisingly (or not), that didn’t work as expected 😟 So after a few hours trying and trying again, I decided to ask for help… (Never be afraid to ask for help, because you’ll 100% learn something!
When creating a Microsoft Teams team, you can choose Private, Public, or even Org-wide. For the purpose of this blog post, we’re going to talk about Private and Public teams. Create a Private Team So, I create a Teams, set it up as Private, and add only one member. As we know, when creating a Microsoft Teams, a SharePoint site is automatically created as well, and the membership should reflect what’s in Teams.
With the new Microsoft Teams admin center, administrators can control policies, tenant-wide settings, and also create Teams directly. Create a Team from the Admin Center First thing first, log into the Office 365 portal, then access the Teams admin center (left pane). Under the “Teams” section, click on “+ New team” Fill the info for your new team: a Name a Description Choose the privacy (Private or Public) Then, click on “Create team“.
Hubsites have been announced at Microsoft Ignite in 2017, and provide a way to display content from multiple sites (once they’re connected) with same branding, and also a search functionality across all connected sites. In today’s post, we’ll see how to use PowerShell PnP (Patterns & Practices) to associate teams and/or communication sites to a hubsite. You can have a total of 100 hubsites per tenant, and there’s no maximum in the number of sites that can be connected.
Group-based licensing for security groups in Office 365. This is something that will reduce clicking, scripting, and admin burden overall. If this fits your organisation requirements and governance, then go for it! It’s a great feature. Let’s see how we can start using it. Minimum requirements: Global Admin or User Management permissions Office 365 trial/paid subscription (E3 in my case) Enough licences in the tenant for users In my scenario, I have 2 fake users as follows:
If you created a modern Team Site in SharePoint Online (SPO) and decided back then, not to connect it to an Office 365 group, it’s totally possible to create this group, and ‘link‘ it to an Office 365 group. You’ve changed your mind, and you want to take advantage of what the Office 365 groups have to offer. Shared mailbox, Planner, and even Microsoft Teams! So let’s get started, and see how we can accomplish that.