Site Collection App Catalogs are great for special cases (like developing apps or site unique apps), but using them on scale would be a mess. I got a question: Why should we use the Tenant App Catalog at all when we could enable a Site Collection App Catalog on every teamsite? So the suggestion here is to install SharePoint Framework Packages on many Site Collection App Catalogs, instead of the Tenant App Catalog.

Once you approve a permission request from an SPFx app, it will grant the same permission to all other apps in the same tenant. Nothing new, but I want to emphasize that in that blog post only dedicated to that. You can read it here: MS Docs. Connect to Azure AD-secured APIs in SharePoint Framework solutions A simple sketch over the permissions. Here is a simple FAQ to explain what it means:

Using Azure Key Vault in a Pipeline is cool, but it is less secure. The Key Vault setup Have you tried the Key Vault Step in an Azure DevOps Pipeline? If you haven’t, please follow these awesome guides: Azure DevOps Labs. Using secrets from Azure Key Vault in a pipeline Tobias Zimmergren. Using Azure Key Vault Secrets in Azure DevOps pipelines The steps described in these guides are easy, but that effort made me think about the first pair of pros and cons.

I have read and followed this awesome post: Getting SPFx working in Visual Studio Online by SPDavid. I got my fingers and tried that guide out. This worked good, I spent some time, though, googling (binging) around to get rid of the SSL Warnings for the remote “localhost” on my Mac. I would like to share this simple instruction on how to trust a self signed certificate from gulp-connect on Mac OS.

Allowing custom script has its security implications. But what exactly does it mean? Is it dangerous? My colleauge Daniel and me have done a little experiment. There are two implications stated on MS Docs: Scripts have access to everything the user has access to. Scripts can access content across several Office 365 services and even beyond with Microsoft Graph integration. To summarize, we can look at that picture: So the risk that user 1 (the Blue User) intentionally or unintentionally places a script and lets user 2 (the Red User) run this script by linking to the page that has this script.

This post is my summary and my conclusions on the Path Length Limit in SharePoint Online and OneDrive. How the path length is calculated Path Length is not the same as the URL length. It is the relative Url. /sites/site-url/documenlibrary/folder1/folder2/filename.fileextension Calculations rules Only the server relative url part is counted. The “https://[tenant].sharepoin.com” has no impact on that. It starts from the foward slash: “/sites” (or /teams). An encoded value such as a blankspace (%20) is treated as one character, not three.

I saw a demo of it on the European SharePoint Conference in Copenhagen in 2018. Sebastian Fouillade, who showed this, compared this big change with brain surgery. All the urls, all the connections. But now it is possible. Today I have seen it even in my standard release tenant. It is really appreciated. Soon it will be possible to rename misspelled sites, like “devlepment” to “development” etc. To rename you need to go the SharePoint Admin, find your site among Active sites and click on “Edit” in the site url area.

A non-admin user can create no more than 250 resources in Azure AD. That is one of the many Azure AD service limits and restrictions. A “resource” can be an app registration, an Office 365 Group etc. But I would like to discuss Groups more in detail. Imagine the following scenario: Your organization has disabled Office 365 Group Creation. Only IT can create new groups. A service account has been set up for creation of team sites.

Ett nytt tips på svenska: det finns en webpart i SharePoint Online: snabbdiagram. När du har lagt till ett snabbdiagram, kan du skriva välja mellan stapel och cirkeldiagram Du kan bara välja mellan stapel- och cirkeldiagram. Data går att mata in direkt. Resultatet får du direkt: Använd data från en lista Det går att visualisera data från en SharePoint-lista. Det är inte så mycket mer komplicerat, men det öppnar nya möjligheter.

This is my personal list of links and thoughts on troubleshooting performance in SharePoint Online. Resources @MSFT365Status, a twitter flow on the incidents and resolutions connectivity service Service Status (open for all), Service Health (for admins) Health info in Response Headers Every response from SharePoint Online contains some health information: Diagnosing performance issues with SharePoint Online (MSDocs) Troubleshooting SharePoint Performance Issues with F12 (blog post) Following Response Headers could reveal the health: