After reviewing the amazing article of Emanuele Bartolesi about customizing the new terminal for Windows which looks amazing and then I asked myself – how about configuring it with the logo of the PnP or the famous mascot of Parker? Let’s make it so I’ve built a customized terminal with the PNP media logos. I’ve added it to the GIT so everyone can copy this configuration or improve it.
SharePoint Framework is growing in a daily bases and the solutions built for it are in always evolving with new features or improvements. However, it can be necessary to restore the older solution on your SharePoint Online due to some requirements of the projects or even issues.
When you are creating a SharePoint Online, by default the owners of that specific site will manage all the request access to the SharePoint site. If the user doesn’t have permissions to access to the SharePoint site these owners will receive an email to authorize or not these users to access the site. On the following article, we will use PNP Powershell to add an extra email to the default configuration.
SharePoint sites have by default the possibility to be shared by any member belonging to the site and with it, they can share with anyone of your organization or external. With this, you can end with the site being shared with a lot of users without you realizing that happened.
When we create a Modern Team site, we have the possibility to create with a simple click, since we have an Office 365 group, a Team inside the Microsoft Teams. However, if that message was dismissed by any admin of the site and you need to create the group, they need to do other type configurations to activate that group.
When we are starting or doing development on SharePoint online most of the time, and since the introduction of the Hub Site (hubify), projects are done with this new structure. Adding a new user as admin on each site of the Hub will be very time consuming. With the PowerShell Script shared here, this task can be done in a few seconds.
The SharePoint Framework solutions (SPFx) are most of the times deployed at the Tenant APP Catalog and external users don’t have access to that resource by default. They will see an error message and that is related with Permission of App Catalog. You need to make the solutions files available for yours External Users and because of that, you need to configure your SharePoint Tenant to grant access for those users.
Since the Introduction of Connect-PnPOnline -UseWebLogin, sometimes there were issues where the authentication method is somehow being stored on your desktop with the current session for some reason, and when trying to connect to another tenant, we cannot enter the new credentials and the stored ones are used.
Installing SharePoint cmdlets it’ll most likely be a requirement when you’re developing on SharePoint either Online or On-prem. In this article, we’ll explain how to install, update, check the current version and uninstall these PowerShell solutions.
In the past, the Sandbox Solutions were the easiest way to add custom solution added to your SharePoint Classic sites and usually, we can just deactivating the solution and that will not be activated on the SharePoint site anymore but will always be there on the solutions list unless we delete the package.