Calling Icon missing in Teams after Direct Routing is activated

You can support this issue:

Configuration Requirement
SfB Online + CloudPBX + PSTN Calling

Download Weblogs
VoiceSettingsService: isTeamsPreferredClient updated.
UserAppsStore: Finished adding/filtering static apps
UserAppsStore: Calling app removed
UserAppsStore: Attempting to add calling with the following flags: isCallingEnabledByTenant=true, isSfbCloud=true, isEvEnabled=true, disableCallingForHybridVoice=true, pstnType=OnPrem, isBusinessVoicePath=false

Clear Teams Cache:Clear those locations:
%AppData%\Microsoft\teams\application cache\cache%AppData%\Microsoft\teams\blob_storage%AppData%\Microsoft\teams\databases%AppData%\Microsoft\teams\cache%AppData%\Microsoft\teams\gpucache%AppData%\Microsoft\teams\Indexeddb%AppData%\Microsoft\teams\Local Storage%AppData%\Microsoft\teams\tmp%LocalAppData%\Google\Chrome\User Data\Default\Cache%LocalAppData%\Google\Chrome\User Data\Default\Cookies%LocalAppData%\Google\Chrome\User Data\Default\Web DataInternet Explorer Temporary Internet FilesInternet Expl…

Certificate Requirements Teams Direct Routing SBC

Running Microsoft Teams with Direct Routing for Cloud Voice, you have to deploy a certificate on your SBC. This certificate is used for encryption with TLS. Often there is the question how the certificate must be configured.

SBC Public Certificate Requirements

All deployed SBCs must have a public certificate from a trusted/supported Public CA, there are 3 options to create a certificate.

Security Note:
When generating the CSR, the private key size should be at least 2048.

Support Note: domain for certificates is not support.

Option 1 - Single SBCA certificate with a single SBC FQDN.
The SBC FQDN must be in the subject, common name and the Subject Alternate name.

SN/CN SAN {Public FQDN of SBC }  {Public FQDN of SBC }

Option 2 - Multiple SBC A certificate with a multiple SBC FQDN’s.
The SBC FQDN must be in the subject, common name and the Subject Alternate name, which includes the additional SBCs too.

SN/CN SAN {Public FQDN of SBC } {Public FQDN of SBC },
{Public FQDN of Additional …

Teams Direct Routing with SBC Simple Setup

If you want to quickly setup a Microsoft Teams Direct Routing with your own hosted SBC connected to the PSTN. For a smaller, simple scenario you can use this few commands and will be ready within minutes.

New-CsOnlinePSTNGateway -Identity -SipSignallingPort 5068 -ForwardCallHistory $true -ForwardPai $true -MaxConcurrentSessions 60 -Enabled $true

(-Enabled $true will instantly enable the GW for outbound calling allowed)

Set-CsOnlinePstnUsage -Identity Global -Usage @{Add="Unrestricted"}

New-CsOnlineVoiceRoute -identity "Unrestricted" -NumberPattern ".*" -OnlinePstnGateway -Priority 1 -OnlinePstnUsages "Unrestricted"


You create the Online PSTN Gateway, your own SBC and define the SIPSignaling Port and some more parameters, e.g. the maximum concurrent sessions (here 60)

Create an unrestricted PSTN Usage, enabling the user, for allowed callings to anywhere 

Create a Voice route, so the Teams Direct Routing knows w…

Office 365 Subscription ID and Tenant ID

Hi all,

I'll very often ask where to find the tenant ID and further the subscription ID in Office 365 

Find your Tenant IDRequirements:
PowerShell 6.x
.NET Framework 4.7.2 Power Shell:Install-Module -Name Az -AllowClobber
Update-Module -Name Az

 Azure Portal:

Find your Subscription ID:PowerShell: Set-ExecutionPolicy RemoteSigned $credential = Get-Credential
Connect-MsolService -Credential $credential
Get-MsolAccountSku | FL

Get Members from Unified Groups

If you wish to read the members from an Office 365 Group/ Unified group you have to use the Get-UnifiedGroupLinks cmdlet.
Get-UnifiedGroupLink {GroupName} -LinkType Members
$UG = Get-UnifiedGroup Sales
Get-UnifiedGroupLinks $UG.Id -LinkType Members

Cannot join/ see Office 365 Groups in Outlook 365

This might be happen either if an Azure AD Account is corrupted or it was incorrectly migrated during Azure AD Sync.

If the user can access or see the Unified Group, you have to manually remove and re-add the account to the group.

The error message, if a user try to add/ join the group is:
Your request could not be sent. Please try again later.