Problem

Microsoft has not behaved consistently many times. Generally, this is related to the slow propagation of changes made into Microsoft Admin portals or via PowerShell. Unfortunately, the solution is to wait for Microsoft and build processes that consider this unpredictability.

Solution

The solution is to know what to expect in the many instances where slow propagation can affect you:

1. When you assign and/or change User or Phone System licenses to Enterprise Users, e.g., I changed my license, immediately made a test call, and it failed.
   1. Microsoft Propagation of assigned licenses can take time, especially during peak U.S. Business hours. 
   2. Applying these changes during lean hours is best to allow propagation and prevent downtime.
   3. It is sometimes necessary to re-provision the user entirely after a license change. 
2. When you kick off a Direct Routing setup
   1. A DirectRouting User is set up in Microsoft Enterprise, and this User is assigned licenses. The assignment has to be completed before the Direct Routing process can continue. Solution: Confirm the assignment is complete and restart the Direct Routing setup.
3. When you delete a Teams Application you would like to replace.
   1. Microsoft will cache the deleted Application for 15-30 minutes. Please wait for the Microsoft cache to clear before reinstalling the Teams application, or it will fail.