Teams Policy Settings Take Forever To Reflect On The Teams Client
When making a change in the Teams admin portal to a user policy (messaging, calling, meeting) for specific users the change can take hours to take affect on the client. This is so frustration as an admin when you want to create new policies and apply them for testing purposes. Nothing like having to wait upwards of hours to see how a policy changes the user experience on the Teams client.
What is the hold up?
Corey M. Caruso
shared this idea
17 comments
-
Med Dlela
commented
Workaround solution:
After updating Teams policy settings and If you’re getting the settings in the web client but not in the desktop client then you can either wait for 24 hours for the cache to refresh itself (may be done sooner) or clear the Teams client cache.You can do this by closing Teams app then browsing in Windows Explorer to %appdata%\Microsoft\Teams and deleting the Application Cache and Cache folder and logging back into Teams ( or deleting the Teams folder on %appdata%\Microsoft\)
-
Anonymous
commented
It's not just the client machine that's taking forever -- it's the client server as well. For instance -- yesterday, I assigned Audio Conferencing in the 365 Admin Portal. 20 hours later, the Teams admin portal isn't showing Audio Conferencing. That's got to update before the client will...
-
Fitz Stewart
commented
You should add a "Refresh Policy Now" button in the UI to accomplish this. Very frustrating. Or put an option on the client to refresh policy
-
Anonymous
commented
Yep agree with everyone here, bit of a joke how long it takes apply simple policy changes.
-
Anonymous
commented
It has always been the problem with a web/cloud tool vs a local application. But with this Office 365/Teams tools its even worse. We must wait days to see a setting applied...
-
Anonymous
commented
There must be a defined time for applying a change in policy to users. It is random from few minutes to multiple hours.
-
VM
commented
Looks like the issue is still present in June 2020. Is there a plan to fix this? Or a work around?
-
Ghion
commented
We setup a custom meeting policy to block recording from org-wide and allow only some users. After adding a user to the custom policy , for some users recording radio button start showing after two hours for some after 4 hours for some takes full 24 hours or worse you've to manually update client ...Toggle switch options should not be designed to take hours to just do a YES/NO option on a client. Please please improve the change effects propagation time to clients !
-
Daniel Ferreira
commented
takes to long time to aply a policy in Teams. Please send a powershell to force update or a simple web option.
-
Don
commented
Glad to see I'm not the only one. I wish I had found this blog before I had been beating my head against the wall all day. I'll just see if it works itself out over the weekend.
-
Anonymous
commented
Very frustrating indeed. I have now been waiting for more than 36 hours and policies are still not fully implemented. And we all think that moving to the cloud speeds up things. Our internal IT-Organization would implement this in minutes.
-
Anonymous
commented
Takes 24h to only enable anonymous in Teams....... Its really bad
-
John-Paul
commented
I'm trying to set up a Virtual camera club as ours has closed for maybe 4-6 months. I'm learning as I go. I found the Teams admin site today as I needed to allow guest entry, It is really frustrating that changes such as these can't be reflected in minutes.
-
Anonymous
commented
yeah it would be nice to be able to change policy more quickly. I just changed a global policy for apps and made a mistake... now I have to wait up to 24 hours or some unknown interval before I can get a simple app working again? Crazy. Make the update populate quicker.
-
Terrence
commented
I have the same issue. it sometimes takes hours, sometimes takes a day. The version I have is 1.3.00.362.
-
morgz
commented
I'm experiencing a different issue rather than Calling Policies only taking the Global (Org-wide Default) policy into effect.
-
Anon Y. Mous
commented
I've just recently experiernce this same problem. The MS Teams client (v1.2.00.17057) has virtually no predictable pattern as to when a policy will be updated. I've seen it take minutes, hours and now days for a simple policy adjustment to propogate down to the client. There needs to be a setting that controls this from the server side, and a means fromthe client to force a policy update. I have proven that a logout does not work nor does exiting the app completely and restarting. A policy change I made three days ago just appeared now.