Office365

Solving Microsoft Teams Licensing Error “errorCodeTeamsDisabledForTenantForbidden”

Launching Microsoft Teams

This post explains how to fix the “errorCodeTeamsDisabledForTenantForbidden” error when trying to add guest users to Microsoft Teams channel. This issue might arise when a user is invited to a channel in your organization’s Microsoft Teams for the first time. Fixing it usually just requires a flip of a switch, but might also include some waiting.

Symptoms

You get an error screen like this, when trying to join a Teams channel as a guest user.

Teams Guest access error

Teams Guest access error

No fear, though – likely an easy fix!

Continue reading

Related Posts:

SharePoint-Teams -integration using a tab

Microsoft Teams Logo

This post describes one possible scenario for SharePoint-Teams -integration, how to achieve that, and what kind of issues there might be.

Teams? What’s that?

At Blue Meteorite, we at the Valo team have been leveraging Teams since early 2017 as our main communications channel. For us, it complements Yammer, email and Skype for Business quite nicely, although to be fair, it’s not always 100% clear which channel would be optimal for a certain piece of communication… 🙂

The Redmond Magazine calls Teams Microsoft’s response to Slack, and for someone who has used both, the source of inspiration is rather obvious. Built for “high-velocity teams”, it’s yet another collaboration/communication tool, but in a way more flexible than either Skype for Business or Yammer. First and foremost I’d position it as a challenger to services like Slack – and hence at least partially a new addition to Microsoft’s ecosystem.

Continue reading

Related Posts:

Fixing the “For security reasons DTD is prohibited in this XML document.” issue

"For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."

This post describes a couple of ways to fix the issue “For security reasons DTD is prohibited in this XML document”. At least for me, it appeared when trying to access SharePoint Online using Powershell or a console program using OfficeDev.PnP (which in turn uses CSOM).

Error

When running any piece of code, whether in PowerShell, .exe console or anything else than in the code behind relies on .NET Framework, you get an error like this:

Continue reading

Related Posts:

Tweaking the SharePoint list view search box to filter on managed metadata fields

SharePoint List View With enterprisekeywords searchable

This post contains minor but nifty tweak to search box in SharePoint list views. Applies to 2013, and Office 365 (for now). Pretty basic stuff, but had to figure this out for a customer so can just as well document it here 🙂

Okay – so a customer needed to be able to filter view items in a SharePoint list by values in a ke

SharePoint list search

SharePoint list search

yword-field (managed metadata, with values added by editor users), and wanted to use the SharePoint’s searchbox. The problem was, out of the box this field does not search from “Enterprise Keywords”-field (or any similar field). This searchbox does, however, use search index, so anything that’s there, is also searchable in the view, after a few simple configuration steps.

Continue reading

Related Posts:

How to log in to SharePoint as a different user?

SharePoint Online site menu

SharePoint 2013 and 2016 don’t have that old and familiar “sign in as a different user” -option in the site menu, and for the time being, nor does SharePoint Online. However, sometimes it’s very useful functionality to have, so it’s a bit weird Microsoft chose to get rid of the option. This post outlines a method that I’ve found to work quite well for making SharePoint ask for credentials, so that you can use another account to then log in!

Solution for logging in as a different user

There’s an url you can use to automatically log the current user out, and prompt for new credentials.

Continue reading

Related Posts:

Identifying IE11 compatibility mode in SharePoint

IE11 compatibility view emulator

This post describes how to figure out if IE11 has jumped in the compatibility mode and therefore screws up your CSS.

Compatibility view now and before

Microsoft has been pretty keen on introducing new ways to handle browser compatibility and make IE behave in even stranger ways that it usually does by switching it to compatibility mode. There are a few reasons this could happen, but perhaps the most usual one in SharePoint’s case is that IE identifies the SharePoint site to be located in intranet zone, or it’s set to that zone or the list of sites to display in compatibility mode via a group policy.

Before IE11 the switch was reasonably easy to notice – there would be a button/icon similar to this on the address bar, when the browser was in compatibility mode:

IE 10 compatibility mode

IE 10 compatibility mode

However, in IE11 Microsoft has removed the icon leaving us in the dark about whether the page is in compatibility mode or not. We COULD check the compatibility view and security zone settings to find out the mode, but there’s a better way, too. Now, we must check the developer tools (F12 brings them up) to see, which document mode is activated. IE11 in compatibility view may show us something similar to this:

IE11 compatibility view emulator

IE11 compatibility view (emulator)

But wait a minute – what if you can’t access the end user browsers yourself? Before it was pretty easy – you could just ask the end user to check for the compatibility view icon, as it was easily visible on the address bar, but nowadays you’re mostly out of luck – instructing the end users to actually use developer tools is probably going to be difficult. However, there’s a workaround for this.

Continue reading

Related Posts: