Teams dial pad is missing - 5 items to check!

In my personal experience even you Move users (Move-CsUser) it doesnt mean it will be all activate in the Microsoft Teams backend. It will take time to replicate microservices and sometimes it goes up to 24hrs. 

Following 4 items are important  

- Phone system license attached with the user 

- SfB Online Plan 2 License 

 -EnterpriseVoiceEnabled

 - Hosting provider change to sipfed.online.lync.com 

 - CsOnlineVoicePolicy is assigned to the user or calling plan

 

 

  

How to check this using PowerShell, Connect to Teams using PowerShell and 

Get-CsOnlineUser -identity <mailaddress@abc.com> | ft *LineUri, HostingProvider, EnterpriseVoiceEnabled

In my personal experience make sure above items are in checked. 

and addition to above items you can check this tool too - Dial pad in missing in Teams - Microsoft Teams | Microsoft Docs 

M365 Secure score - Turn on the common attachments filter setting for Anti-malware on EOP

This filter will help us to prevent certain types of files that are risker to send and receive via emails. To make sure these file types don't get through, enable the common attachment filter.  

How to access -  https://security.microsoft.com/ then go to Policies & Rules > Threat policies > Anti-Malware

It will have a long list 

You can use the default list of file types or customize it. 

Messages with the specified attachments types are treated as malware and are automatically quarantined. 

Change notification status to different organization requirement. 

Teams Calling | Number porting diary - Day 2

Find the LOAs for Teams 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 Address mentioned correctly (it can be multiple service address)

- Company Name without a mistake not even a dot :)  

I got many LOA rejected for very simple things but it is not simple because its purely security purpose they validate those.

ER - Term mostly used by Canada telecom providers/ISP

Teams Calling number porting diary - Day 3

 

DNS Suffix , Internal DNS zones, External DNS (M365_UCTechiLab#5) - AD and Exchange 2016

DNS Suffix , Internal DNS zones, External DNS (M365_UCTechiLab#5) - AD and Exchange 2016

Access the AD Server and DNS and Create new DNS Zone. 

I would suggest to fix the it/DNS suffix add then you can verify by accessing the ADUC and create user 

For DNS work in the Exchange and also AADConnect to verify UPNSuffix we should have domain in the both side of the ADs. AAD will have the automatically when we verify part of the tenant verification by adding a CNAME in public domain where you have domain records. Addition to that if you dont have this in AD DNS (On-Prem) then you will required to add. 

Follow the steps and it will be straight forward in new environment and if you already using this domain in your exchange then this wont be a problem or not required to create. 

Go to Active Directory Server (AD) > AD Domains and Trusts 

 

Right click on top Active Directory Domains and Trust > UPN Suffixes and Add the UPN you required 

Once you save above settings. When you try to create users you able to see that. 

for DNS zone we will be creating new zone under this name 

next step

 

Add the domain you which you created in the DNS Suffix

Do not allow dynamic updates 

Completed

Zone will be created 

Adding Exchange A records on all new zones