Unified Communication Techies

Find the LOAs for T eams Calling migration Following URL will be the listed every LOA and LOA format will be different from each market/country and also requirement will be different from telco to telco.   Phone number management for Canada - Microsoft Teams | Microsoft Docs This article will have all the LOA for Subscriber Numbers (DID), Service Numbers (AA, CQ) and Toll-free.  When you submit a LOA it will be important to filled it correctly and include correct information to reduce number rejections from the telco. In this case it will be Microsoft TN support team (PTN) team (which mention in my previous article).  - BTN (Billing Telephone Number) mentioned in the ER (Equipment Record) or  CSR (Customer Service Record).  - Account Number can be found on the bill or ER/CSR - Signatory Name of the person of the organization and this can be change when person is left organization via direct email from the client to respective telco.  - Service Addre...

This started with MC780743 change and following will explain as a summary, Summary The message details an update on the rollout timeline for changes to Teams administrator permissions required for creating and managing Teams Phone Resource Accounts. The change, rolling out in December 2024, will require Microsoft 365 Global Admin or User Admin roles for these tasks, affecting Teams Administrator, Teams Communications Administrator, and Teams Telephony Administrator roles. Organizations should prepare by adjusting processes accordingly. However this was pushed to some of my client tenant recently or many notice recently :).  Issue Before change people able to create Resource Accounts without having User Administrator Roles in Tenant and also able to modify those accounts. After  MC780743  change, everyone required to have User Administrator Role and i had that attached to my admin account too. However, even after Teams administrator and User administrator both active i cou...

During my time at Microsoft I did not have a chance to migrate any customer since Microsoft Calling plan was not available for Asia Pacific. The list of articles here are all my experiences with migrations to Teams calling plan and also from Teams calling plan to Telco porting. I searched in several places for documentations by individuals about the process and how to proceed, and I did not have much luck in my search. Hence, I thought why not I give back to the community about my daily hustle in summary. Number porting can be very simple to complex, this completely depends on the environment, the type of numbers available in that environment, their usage, and the level of knowledge the customer has about their own environment. Prior to submitting any order (be it Microsoft or any Telco around the world), number planning is required, and the entire process can consume many hours. Porting request submission  Porting request(s) can be submitted from two locations: 1.   Teams Adm...

Many companies are migrating to Teams Voice, transitioning from legacy PBXs such as Cisco, Avaya, and Coral. In the past, for Hunt and IVR voice prompts, they would reach out to professionals or companies that specialize in these prompts, or they would record them internally as a low-cost option. Option #1 : You can convert speech to text and use it for Teams CQ/AA greetings and menus. Option #2 : You can use existing WAV or MP3 files and upload them as they are. I decided to write this article based on my own experiences with various failures, such as the following: Error:  Microsoft Teams Auto Attendant/Call Queue - We can't upload the audio file. Verify the contents of the file and try again. Solution: Change the sampling rate to something Teams CQ&AA supported.  https://techcommunity.microsoft.com/t5/microsoft-teams/phone-system-upload-wav-greeting-to-call-queue/m-p/1525267   How it is been done:  I had heard about this tool before, but I was recently convinc...

Use of Teams AA External Forwarding options I had a scenario where porting is almost completing but customer end devices at reception is are not ready/late delivery to the location. This example is applying only to Service Number deliver to reception. Just to give glimpse of porting, i didn't port everything but partial porting and this is one of the number +1 365 xxx 421 and since it is "ServiceNumber" from Local telco.  Due to the device not availability delay i have to look for an option asap. Option #1 - Convert this number to user number and add forwarder to reception number. it can be Teams client or may be number forwarded. Option #2 - Do the option#1 part of it and forward immediate Voicemail but for how many days? This wont be an option :D  Option #3 - Create new Teams Auto Attendant immediately and adding the greeting (just like other reception number) so no one feel a difference or changes. Then all the call forwarded to existing to reception number: +1 ...

If your environment has Privileged Identity Management (PIM) enabled, you may be familiar with the following error. This article is not about PIM itself, but organizations use this feature to minimize the number of individuals who have access to secure information or resources. This reduces the chances of a malicious actor gaining access and helps prevent an authorized user from inadvertently impacting a sensitive resource. For more information, refer to this article: Privileged Identity Management . https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure You will usually encounter the following error if PIM is enabled but has expired, or if you forgot to enable PIM while trying to use an existing open window, such as in Power BI. (Voice professionals will be familiar with CQD/QER.) Fix or Best practice:   Enable PIM and wait 30 to 60 seconds before trying again. In most cases, this will help you avoid the error. However, if you try to acc...

Overview  Admin experience when he/she try to assign a number to an user, "No results were found"  1.  Replication delay &  License status  To address the delay in license assignment and replication from Microsoft, connecting to PowerShell is indeed a practical approach. Here’s a step-by-step guide to help you figure out the status of the license assignment: Check License Status, Open PowerShell : Start by opening PowerShell with administrative privileges, Connect to Microsoft Teams : Use the  Connect-MicrosoftTeams  cmdlet to establish a connection to your Teams environment  and try following, Wait for Replication: Keep in mind that after assigning a Microsoft Calling Plan to a user, it can take up to 24 hours before they’ll see the dial pad in their Teams client, Get-csOnlineUser -Identity "madushkadias@deployskypeforbusiness.com" | fl  Output shows following and Provisioned plan missing, and so, my assumption become valid.   ...