April 12, 11:21am ADT

User impact: Users recently migrated to Microsoft Teams may not see the dial pad for up to 72 hours after being migrated.
More info: This issue is intermittent and specifically impacts users migrated from an on-premises environment to the cloud, and users that were assigned a new number or changed numbers in Microsoft Teams. The issue occurs in all Microsoft Teams connection methods.
As a workaround, admins are able to use the following script to manually implement the Voice Policy change: $UserSip = $policy = Get-CsOnlineUser -Identity $UserSip Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip $null Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip -PolicyName Enabled Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip $policy.TeamsMediaLoggingPolicy
Current status: We've developed, validated and are now working on final approvals and preparations prior to the deployment of the fix, which we anticipate will succeed in remediating the impact.
Scope of impact: Any Microsoft Teams user who was recently migrated from an on-premises environment to the cloud, or that recently received a new number or whose number was recently changed, may intermittently experience delays of up to 72 hours in accessing the Microsoft Teams dial pad.
Root cause: An update to optimize cache processing on the underlying infrastructure responsible for supporting Microsoft Teams functionality subsequently increased the length of time that the dial pad takes to become visible to users after migrations, number assignments, and number changes.
Next update by: Thursday, April 13, 2023, at 10:30 AM UTC