When creating a Microsoft Teams private channel by default, it creates a brand new SharePoint site which will store all the information related to that private channel. This is a special site that contains a couple of settings. I will leave at reference an article that you can check to check those settings. I will share some PnP PowerShell commands that will help us to get this information.
A couple of days ago I come across a SharePoint feature that is very useful to check who view the file that is a SharePoint document library. This feature can be very useful to check who viewed that particular file. This feature will allow you do understand you saw your meeting records if you’re saving then on SharePoint.
A few weeks ago, I was playing with the Microsoft Teams creation using Microsoft Graph endpoint and as expected, a couple of teams were created because of that. Using these endpoints can be extremely useful to automate a process on our organization. However, when you’re doing this it will create a lot of “testing” teams. This is also applicable to Teams that are not “testing”.
There are some scenarios where the document libraries on SharePoint are used only to upload files. For example, let’s say that you have a sales team that need to upload to a document library an excel every week. Therefore, maybe the new button to have an option to create a new folder or create a new document doesn’t make much sense.
A few days ago, I had a request to add multiple users in a SharePoint site but using the default interface, I can only add one by one. If we have a long list of users that need to be added to the site this tasks can take a while. So I come up with a PowerShell that will do this task based on a CSV file that contains the email that will make this process faster
Microsoft Graph has a lot of commands that you can use to do some tasks. That will require you to manage and built the OAuth and from there make the request to Graph. But you can use the PnP PowerShell to perform this task. The commands will enable all of this and you don’t have to manage anything.
When you sharing PnP PowerShell scripts with someone, sometimes these users don’t have the option to install cmdlets on their machines and that will lead to some questions back and forth about the script not working as expected. So, we can save the modules required to perform our task on the PC and then execute from there the code.
In my last blog post, I shared a PowerShell script that allows you to export a term set to a CSV file. This script has similar purposes but with fewer lines of code. This will extract the complete term group instead of the Term set as well. If you which, you can edit the file created and delete the unwanted term set that was created by this command.
This is one of the most used features of SharePoint and sometimes, we may create this term set on a testing site and we need to transfer this term set to other sites. I’ve created a PowerShell script that allows you to export this to a CSV file. You can then use SharePoint OOTB functionality to import the term set to your taxonomy somewhere else.
When creating new pages with News Post often we don’t know exactly the images. Same happen with some document that you may want your company to have access on when creating the new pages. So a couple of days I cross with the feature on SharePoint Online that allows you to create these
Organization Assets. To enable this, it’s needed to run a couple of cmdlets.