In this blog post, I will show you how to customize the app bar in Microsoft Teams.
In the past, the app bar on the left was static and not editable. Since a few weeks, Microsoft provides a new policy in your Microsoft Teams admin centre, called Setup Policy. With Setup Policy, you can customize the pinned apps in the left navigation bar in your Microsoft Teams soft client. Also, it provides the option to define different policies for your users.
If you followed the security recomendations in Office 365 and disabled the ability for users to consent for apps, iPhone users will be facing the message “iOS accounts needs permission to access resources in your organization” during native mail account setup for Exchange Online.
I had this situation and find some articles to solve the problem. I would like to give you a short summary of these articels.
I had the situation where Microsoft Teams is configured for Direct Routing and calls are dropped unexpectedly. We are using an Audiocodes SBC in Microsoft Azure and a SIP Trunk from Deutsche Telekom for the PSTN connection.
Sometimes an inbound call is signaled by Microsoft Teams for a second and then, it is dropped. In the Microsoft Teams activity feed a missed call is visible. Also, a missed call was shown in the activity feed even there was no ringing.
At first, I thought I could bring it down to cell phone calls only. But after asking my colleagues some users reported the same behaviour for calls coming from PBX systems.
Microsoft Teams is the teamwork hub with several communication modalities. You can initiate Peer-2-Peer Audio or Video calls, invite to online meetings. If you already deployed Microsoft Phone System or have installed Microsoft Teams Direct Routing, initiate or get PSTN calls.
But what is the call handling if you are away or you are logged off from Microsoft Teams?
Few weeks ago I had to implement Microsoft Exchange Online for a customer who didn’t used Exchange in the past. For a simple user management, I decided to install and configure Azure AD Connect. So the user accounts from local Active Directory will be synchronized to Azure AD.
There are several advantages of this scenario:
you have a single point for user management, your local Active Directory
if configured, user passwords (or better to say password hash values) are automatically synchronized to Azure AD
the user has a Single-Sign-On Experience for Office 365 services
Office 365 license assignment based on local AD groups
After setting up Azure AD Connect and enabling all users for Exchange Online, I started to configure some Exchange settings: configure distribution lists, shared mailboxes and second mail addresses. But wait, what’s that? After submitting the change and error message pops-up:
What da hack? After some research in the web and reading several blog entries, it was clear: When using AAD Connect and synchronized accounts in Office 365, you have to install an on-premises Exchange Management server for changing some Exchange Online settings. Even you don’t have an on-premises Exchange server installed yet. Very disappointing and frustating. That’s why a customer decides to use cloud service: they wan’t have to install and maintain the system on-premises.
Some days ago I had a request from a customer about missing Music on Hold on Polycom VVX Phones and an Audiocodes SBC. The customer infrastructure:
Mixed Lync 2013 and Skype for Business infrastructure on-premises
Audiocodes Mediant 2600 SBC
Enterprise SIP Trunk by Deutsche Telekom
5.000 Users are enabled for Enterprise Voice features
Some are using Polycom VVX IP Phone (411 and 601)
Most users are using the Microsoft Skype for Business Client 2015 or C2R (2016)
The customer reported me, that for PSTN calls by Polycom VVX users the Music on Hold (MoH) was missing. When the same user calls someone in the company, the MoH is played to the other user. So, only PSTN calls are facing this issue. Furthermore, the customer told me that for users with Skype for Business softclient the problem doesn’t exist.
So, in consequence it seems that we have to do a
deeper look onto the Polycom VVX configuration because only these users are
facing the problem. And only if the call was routed to or from the PSTN.