Teams Admin Centre

[mf13tch]

Hey folks,

 

I work across a number of schools with different MS365 tenancies and have to sign in and out of these pretty regularly as I go about my days work (hooray for private browsing)....

 

I have multiple browsers installed on my Win10 machine to help with this (new Edge, Chrome, Brave, Firefox and IE 11). No matter what I do though I'm constantly getting this problem when I try to sign into any tenancy Teams admin centre. The page starts to load but then fails with the MSAL IFrame message on the tab header as shown in the graphic.

 

It's driving me absolutely bananas as sometimes I need to make a change to Teams quickly and I just can't unless I go and find a machine that hasn't been into the Teams admin centre before. I know all my browsers are based on Chrome (except IE 11) but nothing I've done with any of them (clearing cache, private browser etc) seems to sort this out.

 

Has anyone else experienced this and if so did you fix it / how?

 

I know one of our customers was also getting this problem a month or two ago and he only works for one school however he confirms that the problem has resolved itself for him without his doing anything so I'm not sure it relates to the fact that I have to go in and out of multiple tenancies but it feels likely.

 

 

As always - thanks in advance for any assistance....

 

[mf13tch]

Screen shot didn't load in - sorry....

 

[LeMarchand]

Firefox isn't based on Chrome AFAIK.

 

Can't help directly, as I only have one MS admin school so don't get this problem (doesn't seem to happen with my Workspace Admin accounts). However, a possible workaround might be to set up a bunch of Firefox Portable instances, 1/site and create shortcuts with appropriate names for each somewhere. It may be that separate instances cause enough separation to alleviate the problem.

 

IIRC you may need to delve into about:config to allow multiple instances of Firefox, but I've noticed that I could start a new non-portable one a different virtual desktop at work and I don't think I made the about:config change. (I have it at home to keep my personal and work browser separate).

 

Thinking about it, maybe a different virtual desktop may be enough...

[TechMonkey]

Sounds like a cache issue. Have you tried, in Chrome or Edge, opening the DevTools (F12) and then right click the refresh button and choose "Empty cache and hard refresh"?

[DaveTheTech]

Should be able to use a different browser profile to help with this.

I have one for my user account and a seperate one for my admin account - works well.

[skyline_17]

Have you third party cookies disabled as this can cause the issue

 

https://answers.microsoft.com/en-us/msteams/forum/all/cannot-access-microsoft-teams-admin-centre/9ceb1571-686b-429b-b529-198f10ab2b10?page=2

[mf13tch]

Thanks everyone for the quick replies....

 

I'll have a go at these and let you all know how I get on.

[mf13tch]

Sorry for my slow reply.

 

I didn't need to try the resolutions offered in the end since a couple of days after posting this last message and using the Teams Admin Centre I haven't been seeing the problem any longer.

 

It was very frustrating and I wish I could've helped to give a definitive answer but I can't.

 

Thanks everyone for the suggestions and help.

[Norphy]

Sorry for my slow reply.

 

I didn't need to try the resolutions offered in the end since a couple of days after posting this last message and using the Teams Admin Centre I haven't been seeing the problem any longer.

 

It was very frustrating and I wish I could've helped to give a definitive answer but I can't.

 

Thanks everyone for the suggestions and help.

 

Teams is one of those products which uses an agile development method; chances are what you saw was a bug in that particular build of the product that got fixed in an updated release. It probably wasn't anything you did and I expect there wasn't anything you could do to fix it apart from wait.