SharePoint Localization - You can have your content in different languages for different users.

SharePoint Localization – a (somewhat) comprehensive how-to!

This article describes the localization / multilingual capabilities of SharePoint, and your options as an organization using it to achieve a seamless and user-friendly experience for your end-users and content editors. SharePoint’s definitely a powerful platform, but its multilingual features might leave a bit to be desired – and using them successfully requires some understanding of the platform! Background of Multilingual SharePoint Localization – or showing users with different language preferences content in their preferred language – is not SharePoint’s strongest suite. It never was,…Continue reading SharePoint Localization – a (somewhat) comprehensive how-to!

SharePoint just denied your custom script from running. What do?

5 ways to enable Custom Scripts for a SharePoint site collection

This article explains how to enable custom scripting for any SharePoint site collection. This is functionally equivalent with setting setting “-DenyAddAndCustomizePages 0” or disabling the NoScript feature. Different instructions and solutions apply to SharePoint Online, and on-premises scenarios (SharePoint Server 2013, 2016 and probably 2019) – so see below for all of them. Different solutions are required to resolve the issue for different target sites: Modern SharePoint Team Sites (attached to Office Groups if on SharePoint Online, and without one if On-Premises) Modern SharePoint Communication…Continue reading 5 ways to enable Custom Scripts for a SharePoint site collection

Azure Active Directory (Azure AD)

Fixing issue “AADSTS70005” by enabling the implicit authentication flow for your Azure AD app

Another day, another Azure Active Directory error! So what’s this AADSTS70005 all about? While either developing or just trying to use an application that authenticates against Azure AD, you might get an error message that contains error code “AADSTS70005“. This means that you’re trying to use implicit authentication flow, but it isn’t allowed for your app. If you have access to the Azure AD you’re authentication against, it’s easy to fix! See more below… Reason You might get an error, somewhat like this: AADSTS70005: response_type ‘token’…Continue reading Fixing issue “AADSTS70005” by enabling the implicit authentication flow for your Azure AD app

SharePoint doesn't work as intended

How to show more than 30 categories in SharePoint blog/news sites?

Imagine this: you’re using a good old SharePoint blog site, and have a bunch of categories in use. That’s nice and easy – SharePoint offers the categorization functionality natively, and it works decently. Problems arise when you have a lot of categories, though – not all of them will be shown. Even if you tweak the web part to show more items on a page, this isn’t reflected on the whole blog site! This post article explains how to fix this. Problem For background info…Continue reading How to show more than 30 categories in SharePoint blog/news sites?

"Publishing Failed" for an Azure Function

Fixing the error “Web Deploy cannot modify the file on the Destination because it is locked by an external process.”

This post describes how to fix the error, where when publishing Azure Functions or Azure App Services you get an error like this: “Web Deploy cannot modify the file on the Destination because it is locked by an external process.” This is luckily another straightforward fix!  Problem Azure Function Publish fails with a message: “Web Deploy cannot modify the file on the Destination because it is locked by an external process.” It is, indeed, caused by some of your files at the target of your publishing being…Continue reading Fixing the error “Web Deploy cannot modify the file on the Destination because it is locked by an external process.”

AADSTS50011: The reply address ... does not match the reply addresses configured for the application.

How to fix “AADSTS50011: Reply address did not match because of case sensitivity.”

So, you got an error with a code AADSTS50011? It’s just Azure AD’s authentication acting up because of invalid reply address! here’s a bunch of different reasons that lead to this error. This post describes the variant where the URL’s case sensitivity differns from what’s configured. For me, the most typical scenario where I run into this error is accessing the app from SharePoint. Problem So, you’re getting an error somewhat like this: AADSTS50011: The reply address <…> does not match the reply addresses configured…Continue reading How to fix “AADSTS50011: Reply address did not match because of case sensitivity.”

Azure Active Directory (Azure AD)

How to fix “AADSTS50011: The reply address does not match the reply addresses configured” -error

So, you got an error with a code AADSTS50011? That’s ok – it’s just Azure AD’s authentication acting up because of invalid reply URLs! Since there might be a couple of different reasons for this error, this post also describes a couple of different solutions, that might help you overcome the issues. Problem So, you’re getting an error somewhat like this: But why? Did you mess something up? Well, if you’re the person who configured the app you’re trying to use, you probably did! Although…Continue reading How to fix “AADSTS50011: The reply address does not match the reply addresses configured” -error

Microsoft Stores Backups For 14 Days, But Restores Them in 15

A cautionary tale of relying on the automatic backups in SharePoint Online

So Microsoft keeps 14-day rolling backups of your SharePoint Online sites. That’s awesome – no need to take backups anymore, right? Not so fast. It’s not always so easy, and by just relying on these backups, you risk losing your data. Forever, I might add. This cautionary tale is about SharePoint Online, but I’d say you’ll need to take caution anytime you’re dealing with Microsoft’s automatic backups. The story starts with the client doing something unwise – a prime example would be them removing the…Continue reading A cautionary tale of relying on the automatic backups in SharePoint Online

MFW another API just stops working without returning any errors

How to fix Twitter embed in SharePoint

Twitter embed has a stupid, built-in failure condition: if the User Agent contains IE10 or older, the embed script will not load. This causes SharePoint embeds to fail. This post describes how to fix that.

Microsoft Azure logo

Solving Azure Web Application’s first load perfomance issues

Is your Azure Web Application suffering from absolutely horrible load times every time someone accesses it for the first time every 15 minutes or so? Mine was. It was pitiful. I was developing a web-based service using EF6 and ASP.NET MVC 5, where all the assets were hosted in the Azure. Even though the app was reasonably lightweight and usually responded very fast, the first time someone accessed it in a while it took 20-60 seconds to load AND sometimes even timed out (especially with…Continue reading Solving Azure Web Application’s first load perfomance issues

AADSTS90013: Invalid input received from the user. (header thumbnail)

Solving error “AADSTS90013: Invalid input received from the user”

I stumbled upon a customer, that complained about some pages in their intranet throwing weird errors with authentication. Those pages seemed to have one thing in common – there was a Yammer embed (or a SharePoint script webpart with Yammer embed script in it, to be precise) there. The error code they got was “AADSTS90013: Invalid input received from the user”. Below, you can see an example of the error screen. Okay – this is going to be extremely specific, and probably won’t solve the…Continue reading Solving error “AADSTS90013: Invalid input received from the user”

Let me explain SharePoint...

Don’t remove the root web of your classic SharePoint Site Collection!

A quick heads-up – if you remove the root site (or RootWeb, like it’s called in the code) of your classic SharePoint Site Collection, that’s going to cause you some grey hairs. It might even, in some rare cases, be unrecoverable! The following post describes what kind of issues you might run into, if you remove the root web instead of the whole site collection, and how to remove the site collection instead. Update 13.7.2019:SharePoint Online keeps evolving, and at least on some tenants, removing…Continue reading Don’t remove the root web of your classic SharePoint Site Collection!

SharePoint is not broken - it just does't work

How to fix “The web site does not support SharePoint Online credentials. The response status code is ‘Unauthorized'”

While running some SharePoint Online -PowerShell commandlets, or connecting to a SharePoint Online site from your app, you get a following (or similar) error about your SharePoint Online credentials being unauthorized for something you should definitely be authorized to do: Cannot contact web site ‘https://[tenant]-admin.sharepoint.com/’ or the web site does not support SharePoint Online credentials. The response status code is ‘Unauthorized’. And that’s not all – by digging into the full error message, you find the underlying internal error: MSDAVEXT_Error=917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically. What awakens my curiosity,…Continue reading How to fix “The web site does not support SharePoint Online credentials. The response status code is ‘Unauthorized’”

Unified Groups aren't supported.

How to solve “Unified Groups aren’t supported.” -error

When trying to use some functionality, that relies on Unified Groups, you’re getting errors in the console, similar to this: “Unified Groups aren’t supported.” In truth, this most likely means, that Unified Groups (that’s the internal/technical name for Office 365 Groups) is not enabled for this particular user. That breaks a bunch of different features for them, since the Graph API for Groups of course won’t work. This post describes one way to fix this issue! How to solve this? Posts Related to “How to solve “Unified Groups…Continue reading How to solve “Unified Groups aren’t supported.” -error

How to SharePoint?

Using “DetectedLanguage” to return only localized results from SharePoint Search index

Localization and targeting of content in multilingual SharePoint installations is always an issue. SharePoint offers a multitude of ways profile content based on user language (or other properties), but none of the solutions are fool proof. This post describes how to fetch only localized results from SharePoint Search index, which solves at least some of the issues. Description  SharePoint Search index can be used in quite a few different ways. Probably the most typical way is by searching on SharePoint, or using webparts like Content…Continue reading Using “DetectedLanguage” to return only localized results from SharePoint Search index

Office 365 Planner logo

How to form links to Planner tasks

Office 365 Planner is a neat tool for task management. However, when you, for whatever use case, need to form urls that point you towards a single task (or a bucket, or a plan for that matter), you might run into trouble with how the url is formed. Custom domains actually make it a bit complicated, but luckily there’s a workaround! Description of the issue If you have multiple domains in your Azure AD, your Planner might end up using your custom domain in its…Continue reading How to form links to Planner tasks

SharePoint Search No Results

Alternative Languages in SharePoint forcing the (cumbersome) use of localized Managed Properties

Localization and multilingual environments in SharePoint are an endless source of interesting issues and blog post topics. In one case, we had a tenant created originally in English, and a site collection created in Finnish. In this particular case, SharePoint somehow messed up the language settings, and ended up requiring the use of localized managed properties on the search center of that site collection. That ended up being unexpected, unituitive and unusable for the end-users. Description of the issue Typically, when you use SharePoint Search,…Continue reading Alternative Languages in SharePoint forcing the (cumbersome) use of localized Managed Properties

SharePoint is not broken - it just does't work

Web part title changes not reflected to some users in multilingual SharePoint environment

I encountered another, interesting issue – this time in a SharePoint environment, where multiple display languages were in use. When changing the web part title on a web part on a classic SharePoint page, it seems like SharePoint saves the changes for you. In reality, only some users see the changes. So, in short: Some other users, on some devices, see the old title, whereas some see the new one. It’s a confusing situation and difficult to debug. Why do web part titles get changed…Continue reading Web part title changes not reflected to some users in multilingual SharePoint environment

Azure AD Login error

4 ways to fix error AADSTS65001 (The user or administrator has not consented to use the application)

Have you run into error AADSTS65001 with your application, that tries to authenticate against Azure AD? I sure have – seems to happen at least every other time when I’m building something that uses AAD to authenticate against SharePoint. Fixing issues with Azure AD authentication for Enterprise applications can be tricky. But a lot of the time, this is just another Azure Active Directory error that we can fix easily. This article contains multiple different solutions to the issue, where granting admin consent has somehow…Continue reading 4 ways to fix error AADSTS65001 (The user or administrator has not consented to use the application)