Teams Real Simple with Pictures: Resolving Allow Third Party Cookies in the Teams Web App with Edge

This blog is part of a series on Teams. For more articles, check back often.

Written: 19/07/2020 | Updated: N/A

Every Sunday I typically write a blog. Now in order to write that blog I typically use a test tenant set up on the CDX platform at https://demos.microsoft.com. Why? It’s what we call a Ring 4 tenant which means that everything within it – all of the functionality in Teams has been released and is generally available. Since my corp tenant is TAP (Ring 3) I can’t just take pictures of it or use it in blogs as I may accidently infringe on NDA and the things I am working on with the team at Microsoft. So reviewing the Ring 4 tenant this morning in order to find something to write on, and logging onto the web app via Edge (https://teams.microsoft.com) I was blocked from accessing it which said I needed to allow third party cookies. Ok. Now, this article will focus on a fix for it – not the semantics of whether third party cookies ought to be a prerequisite of the web app experience. Some articles argue that third party cookies need to be on for the browsing experience to be optimal. Others state that third party cookies are a security and privacy risk given they harvest behavioural data. Wherever you fall on this spectrum the fact remains that Teams needs to allow it. I am sure Microsoft will provide an official reason for this in time

Since the issue of third party cookies is browser specific then this only impacts the web app experience. One immediate workaround is to use the desktop app or mobile app however like me I am sure you want the flexibility to use all the apps however you need where possible. This works within the InPrivate browsing mode too.

WHY WOULD WE DO IT?

PREREQUISITES

Teams – usually via an Office/Microsoft 365 licence. Edge browser. This article is based on Edge Version 86.0.580.0 (Official build) canary (64-bit). I have also tested it in the latest standard version Version 84.0.522.40 (Official build) (64-bit)

REMEDIATION STEP 1: RETRY/SIGN BACK IN

The first step to resolving is to always follow the recommendations. Select Try Again and if this doesn’t work, try signing out and back in to https://teams.microsoft.com

TCK1

REMEDIATION STEP 2: ENSURE THIRD PARTY COOKIES ARE NOT BLOCKED

The second step is ensuring that third party cookies are not blocked in the Edge browser settings. Select More Options in the browser

TCK2

Select Settings

TCK3

Select Site Permissions, then Cookies and Site Data

TCK4

Ensure that Block Third Party Cookies is set to off

TCK5

Then try and log back in Teams again

REMEDIATION STEP 3: CLEAR BROWSER CACHE

If steps 1 and 2 did not resolve, try clearing the browser cache. Select More Options in the browser

TCK2

Select Settings

TCK3

Select Privacy and Services and then under Clear Browsing Data select Choose What to Clear

TCK6

It is recommended to clear everything for all time. Select Clear now

TCK7

Try logging in again

REMEDIATION STEP 4: ADD TEAMS EXCEPTIONS TO THE EDGE ALLOW LIST

If methods 1, 2 and 3 do not work and you are still having issues and stuck, try adding the following URL’s to the allow list in the browser which will allow these sites to save cookies to your machine

  • [*.]microsoft.com
  • [*.]microsoftonline.com
  • [*.]teams.skype.com
  • [*.]teams.microsoft.com
  • [*.]sfbassets.com
  • [*.]skypeforbusiness.com

Select More Options in the browser

TCK2

Select Settings

TCK3

Select Site Permissions, then Cookies and Site Data

TCK4

Add the URL’s to the allow list

TCK8

Try logging in again

STILL WANT TO BLOCK THIRD PARTY COOKIES?

By adding the exceptions to the allow list, you can now re-enable blocking third party cookies in the edge browser. The Teams web app should still work – this is shown by the fact that the icon for third party cookie blocking is active in the address bar

TCK9

TCK10

TCK13

PREVENTING TEAMS COOKIES FROM BEING WIPED WHEN THE EDGE BROWSING CACHE IS CLEARED ON CLOSE

Sometimes, users want to clear elements of their browser history after they have completed their browsing session. This could be because of space, performance or keeping the browsing history clean. In order to prevent the Teams’ sites cookies being wiped when you clear the edge browsing data on close, do the following

Select More Options in the browser

TCK2

Select Settings

TCK3

Select Site Permissions, then Cookies and Site Data

TCK4

In the Allow List select the hyperlink clear browsing data on close

TCK9

TCK11

If cookies and other site data has been set to on, add the Teams URL’s which were added to the allow list to Do Not Clear

TCK12