{"id":2789,"date":"2023-02-14T20:42:52","date_gmt":"2023-02-14T20:42:52","guid":{"rendered":"https:\/\/modern-workplace.uk\/?p=2789"},"modified":"2023-03-07T11:38:19","modified_gmt":"2023-03-07T11:38:19","slug":"teams-virtual-sbc-closing-azure-network-ports-warnings-for-azureloadbalancer-and-virtualnetwork-2-2-2-2-3-2-3-2-2-2-2-2-3-2-2-3-2-3-2-2-2-4","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=2789","title":{"rendered":"Microsoft Teams – What to Do Before March 2023 if You Use Phone Number Extensions (MC487014)"},"content":{"rendered":"\n
\n\n\n\n

MC487014 (as reported by Tom Arbuthnot<\/a>) has an impact on all the organizations that use Extensions in their phone numbers. If you already know what the change is all about, just jump to the What to do? <\/strong>paragraph.<\/p>\n\n\n\n

What Happens?<\/strong><\/p>\n\n\n\n

There are two ways to manage phone extensions:<\/p>\n\n\n\n

    \n
  1. The extension is just the last digits of a unique telephone number (like for Megan Bowen that has +44 161 240 2399 and extension 399)<\/li>\n<\/ol>\n\n\n\n
    \"\"<\/a><\/figure>\n\n\n\n
      \n
    1. The extensions use the same base number and add some digits to distinguish two different users (like for Johanna Lorenz and Miriam Graham that have +44 161 240 200 as a base phone number and have a specific extensions each, 374 and 375)<\/li>\n<\/ol>\n\n\n\n
      \"\"<\/a><\/figure>\n\n\n\n

      Previously, Teams was doing a number reverse lookup if the incoming phone number was not matched exactly.<\/p>\n\n\n\n

      After the change has been applied from Microsoft (due Feb\/March 2023), the user will get the phone call only if incoming phone number is exactly formatted like in the user properties. In our example the incoming calls must be exactly \u201ctel:+441612402399;ext=399\u201d for Megan Bowen \u201ctel:+44161240200;ext=374\u201d for Johanna Lorenz and \u201ctel:+44161240200;ext=375\u201d for Miriam Graham<\/p>\n\n\n\n

      So, the incoming phone numbers should be formatted accordingly by a SBC or by a normalization rules.<\/p>\n\n\n\n

      What to do?<\/strong><\/p>\n\n\n\n

      First of all, use the following to identify all the Teams users that have a phone number with an extension <\/p>\n\n\n\n

      # Connect to Microsoft Teams\nConnect-MicrosoftTeams\n# Retrieve all Teams users in the tenant enabled to Enterprise Voice\n$TeamsUsers = Get-CsOnlineUser | Where-Object {$_.EnterpriseVoiceEnabled -eq $true}\n\n# Create an array to store Teams users with a phone number\n$TeamsUsersWithPhone = @()\n\n# Loop through each Teams user\nforeach ($User in $TeamsUsers) {\n    # Check if the LineURI property is not empty\n    if ($User.LineURI -ne $null -and $User.LineURI -ne \"\") {\n        # Check if the LineURI property contains the string \"ext\"\n        if ($User.LineURI -like \"*ext*\") {\n            # Create a custom object with the display name and phone number of the user\n            $TeamsUser = [PSCustomObject]@{\n                DisplayName = $User.DisplayName\n                PhoneNumber = $User.LineURI\n            }\n            # Add the custom object to the array of Teams users with a phone number\n            $TeamsUsersWithPhone += $TeamsUser\n        }\n    }\n}\n\n# Display the results in a table format\n$TeamsUsersWithPhone | Format-Table DisplayName,PhoneNumber<\/code><\/pre>\n\n\n\n
      The result will be similar to the one below<\/p>\n\n\n\n
      \"\"<\/a><\/figure>\n\n\n\n
        \n
      • For users with a unique phone number, removing the extension is the suggested solution<\/li>\n<\/ul>\n\n\n\n
          \n
        • For users with the same base number and different extensions, check that the calls are sent to Teams with the phone number formatted correctly including the extension <\/li>\n<\/ul>\n\n\n\n
          Note<\/strong>: if your Teams Enterprise Voice is managed by a provider, get in touch with them to check that the Microsoft change has been already managed.<\/p>\n","protected":false},"excerpt":{"rendered":"
          Microsoft has announced a change (MC487014) that will impact all organizations using extensions in their phone numbers on Microsoft Teams. Previously, Teams would perform a number reverse lookup if the incoming phone number was not matched exactly. However, after the change is implemented (expected in February\/March 2023), users will only receive the call if the incoming phone number is exactly formatted like in the user properties. For example, incoming calls must be formatted as \u201ctel:+441612402399;ext=399\u201d
          \nTo ensure incoming phone numbers are formatted correctly, organizations should consider implementing a Session Border Controller (SBC) or normalization rules.<\/p>\n","protected":false},"author":1,"featured_media":2795,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":"","footnotes":""},"categories":[810,753,752,757],"tags":[762,759,751,77,755,83],"class_list":["post-2789","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-810","category-microsoft365","category-microsoft-teams","category-office-365","tag-microsoftteams","tag-microsoft-365","tag-microsoft-teams","tag-office-365","tag-teams","tag-voice"],"_links":{"self":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2789","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2789"}],"version-history":[{"count":4,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2789\/revisions"}],"predecessor-version":[{"id":2801,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2789\/revisions\/2801"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/media\/2795"}],"wp:attachment":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2789"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2789"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2789"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}