While trying to set up a new Home Site, I discovered that there is a tool (browser extension) called Page Diagnostics for SharePoint. After running this, I tried that command again and it was smart enough to detect the problem the tool discovered. Also Network Trace is available. Network trace Page Diagnostics Tool is defnitely a tool to have in the troubleshooting toolbelt for SharePoint. Setting up a Home Site Here is the script:

In this post I would like to share some findings from setting a deployment of SPFx. In my work: I need to deploy SPFx solutions using Azure Pipelines I need to use the least privileges/permissions I cannot use Legacy Authentication First of all, big thanks to @waldekm and the whole community of @office365cli and @m365pnp for the quick help, and that outside working hours. Let’s take a look at the setup piece by piece

Honestly, Power Automate is great for automating repetetive stuff. But I think there is room for one-time flows as well. I’ll give you an example. I’ve got an excel file with quite a few rows. And I need to convert it to a SharePoint List. I know there is a couple of options, such as Quick Edit in Classic View, Import an Excel file as a list (it also requires the classic view), there will be Excel import in Modern as well.

These are my findings around Modern Sites without Office 365 Groups. It is, of course, a subject to change. Today (2020-02-21) when you create a Modern Team Site without a group, you will get a site with the template STS#3. This oldie has been around for a while, hasn’t it? I would always recommend creating Office 365 Group Connected sites. How it is created Through PowerShell/REST or from SharePoint Home, if your account is not allowed to create Office 365 Groups, it will automatically create a site without a group.

Want to translate your MS Forms into other languages? Create a form, not a quiz. It is available in both Forms and Forms Pro licenses. Today I want to share one of my findings. One of those that seem obvious once you know, but that take time to find out. Unfortunately, there is no official comparison of what is included in MS Forms vs. MS Forms Pro. So I thought that the ability to have forms in multiple languages was connected to the license.

Sometimes all you need is just a simple static web page: instructions, a landing page, a collection of links. I think I have a perfect use case for Sway. Consider a scenario similar to what Laura Kokkarinen writes in her blog post: How to build a guest user self-service registration for office 365 with azure An external user invitation needs an inviteRedirectUrl. Usually it is myapps.microsoft.com. In Laura’s case it was a given extranet url.

Dags för ett svenskt inlägg igen. Idag vill jag titta på kalenderfunktionaliteten i SharePoint Online. Fortfarande gammalt (classic) utseende Tyvärr är det gammalt utseende som gäller och det finns inga planer från Microsoft att modernisera kalendern: SharePoint UserVoice: Modern Calendars Jag förstår att det är väldigt mycket kod för att få till kalendervyn och att det inte är så lätt omvandla till ett modernt utseende, men det ställer till eftersom det upplevs som gammalt och inte användarvänligt ute i verksamheten.

If you want to remove the Microsoft Teams Banner on your SharePoint Site, the only thing you need is to set a web property on a site: TeamifyHidden=TRUE. I’ll give you some guidance below. But before you do that, consider following: If there is already a team created for a group connected site, the prompt won’t show up. Why fix something that is not a problem? Only group owners will get the prompt, if they are few and they know what it is, it is better to let them to decide whether to create or not to create a team.

This is a guide for how to handle secrets in a logic app in a secure way. It combines three resources: Accessing Key Vault from Logic App with Managed Identity Get Secrets Key Vault API Hide your logic apps secrets from prying eyes First, enable a Managed Identity for your Logic App: In the KeyVault, add a new Access Policy for the new Managed Identity (from the previous step). Use the least priviliges.

Instead of filtering values from an Azure Storage Table, you can do it directly in the bindings. It might not be a solution for everything, but in the right place, it is fantastic. I was very surprised to see how little code was needed after this binding change: For that to work, define the filter attribute in the bindings: “filter”: “(PartitionKey eq ‘{package}’)” To try it out, add a new row in a table defined in the bindings (“metadata” in my case):