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
2 comments
-
morgz
commented
I'm experiencing a different issue rather than Calling Policies only taking the Global (Org-wide Default) policy into effect.
-
Anon E Mousse
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.