In this post I like to notify about a neat feature for all Teams users which are often on the move and need to join an online meeting while being in transit.
Microsoft Teams provides a feature called “Call me”. It allows you to make an online meeting call you on a phone number of your choice. E.g. before or during an online meeting you can select that you want to be called for that meeting. You can select this as you join an online meeting. You can do this upfront, before the online meeting starts or during it takes place.
Conclusion, opinion and summary
The feature might be already known from Skype for Business online meetings. It’s really handy if you are just about to leave a place and maybe go to your car/public transport/… and want to have your hands free, so you can pre-join an online meeting and set a call me. Finally, you only need to answer the incoming call on your cell and your in the online meeting.
In this post I like to describe how you can manage group calling and call delegation in Microsoft Teams as admin.
First of all, I’d like to explain what these two features can do for you or your users:
Group call pickup allows a Teams (phone system) user to select other Teams users to answer his/her call. E.g. Erik Doe get’s a call on his Teams phone number and his other co-workers which he added previously to his group pickup get a notification about the incoming call and can answer it instead.
Call delegation allows to configure delegation for your telephony, similar to what you might know for mail delegation. I.e. this enables you for typical and lightweight boss/admin or manager/assistant or chef/sek (de) capabilities. E.g. Erik Doe can add one ore more other Team (phone system) user as delegates so that Erik Doe does not need to deal with all calls himself.
Configure group call pickup as an user
Users can configure this on the Teams settings \ call settings page.
Configure group call pickup as an admin
In the Teams Admin Center you can configure group call pickup per user. You can add/remove users to a users group call pickup, you can set the notification mode (mute, ring, banner) and you can configure the order and when group call pickup to listed users in a users group kicks in.
Teams Admin Center \ Users \ <user> \ Voice \ Group call pickup
Configure call delegation (boss/admin, manager/assistant, chef/sek) as an user
Users can configure this on the Teams settings \ general \ delegation settings page.
Configure call delegation (boss/admin, manager/assistant, chef/sek) as an admin
Also in the Teams Admin Center you can configure call delegation per user. You can add/remove delegates, you can define what permissions a delegate gets and if a delegate can change this setting (or need to call you to change it via Teams Admin Center).
Teams Admin Center \ Users \ <user> \ Voice \ Call delegation Teams Admin Center \ Users \ \ Voice \ Call delegation \ permissions
Conclusion, opinion and summary
Compare to Skype for Business (Server) this is a very nice administration capability because it’s easy to access and manage. In the past with Skype for Business (Server) you had to use Sefautil, related Sefautil tools or even third party software for an more comfortable way of administrate user call settings. It’s very helpful from time to time to have a ability as admin to change these two settings for an user which might be unable to do this.
Managing Teams Call delegation and group call pickup via the Teams Admin Center works like a charm in my opinion.
Microsoft rolls out a new capability which enables administrator to automatically mount / add a specific SharePoint Team Site Library being synced for users (cp. M365 Roadmap).
M365 Roadmap – Feature ID 27031 (June 2019)
Configure SharePoint Team Site Libraries Auto-mount
To configure the auto-mount you need to configure a group policy which configures the users OneDrive sync settings. (cp. link “Configure team site libraries to sync automatically”)
Prereqs, requirements and limitations
Please note that there are certain prereqs, requirements and limitations before you can start.
Windows 10 1709 or later
Library must have below 5000 files/folders.
Not for 1000+ devices
Sync is applied next time the user signs in but it can take some time until the sync starts.
A user cannot stop the sync.
You need the OneDrvie GPO Template (OneDrive.adml, ..admx) in your central GPO store (e.g. erik-klefeldt.de\sysvol\domain\Policies\PolicyDefinition) …
This might be subject to change (June 2019).
Configuration steps overview
Create a new GPO
Configure the GPO based on your needs, applied to a OU and add WMI-filtering for a more granular scoping, if needed
Add the SharePoint Team Site Library ID to the GPO
Verify that the GPO is applied
(Verify the reg key [HKCU\Software\Policies\Microsoft\OneDrive\TenantAutoMount]”LibraryName”=”LibraryID”)
Verify that it syncs on the devices
Conclusion, opinion and summary
Easy to configure, isn’t it? In my opinion it might help you to move and simplify a migration from legacy files shares to SharePoint Online. It enables you as administrator to manage a smooth transition from file shares/services towards SharePoint Online and really adds a convenient way and comfortable user experience because your users do not need to manually add the library to their OneDrive sync and “map” the SharePoint Online Team Site Library on their device.
In this post I like to share a nice info graphic from statista which depicts where data is and will be stored.
In 2015 most data was stored locally (66 %) and only around a third (31 %) was in the cloud. The graph shows that, of course, storing data online in the cloud increases. By 2020 more data is stored online in the cloud instead of locally / offline / onpremise.
The author of the statista article also quickly mentioned the pros and cons, he says, that it is more comfortable and faster. Hence, he also says, that it poses risks, e.g. data breaches or leaks can cause high costs for people and companies which are subject to these.
Conclusion, opinion and summary
First of all, I’m a big fan of statista’s info graphics. Nicely illustrated and easy to understand figures.
Based on my personal and professional experience I’d assume that these above figures and trends regarding data storage locations seems to be comprehensible. I guess that cloud service adoption statistics would also draw similar trends.
There are many options for licensing Microsoft Teams depending on the capability requirements for users, devices and rooms. In this post I like to point out some “special” licensing options besides the normal ones for Teams in enterprises.
The hereinafter described license options might be subject to change. Moreover not all licenses or subscriptions are available in every country around the globe, especially calling plans and audio conferencing (shortened: Audioconf.).
Teams Licensing Basics
Microsoft Teams is just a single service of the massiv Microsoft 365 services stack which it tightly linked and integrated within this service stack.
Microsoft Teams is part of a “packaged” Microsoft Office 365 subscriptions by default.
Microsoft Teams replaces Skype for Business (Online). The Skype for Business Desktop Client within Office 365 ProPlus is also obsolete, meaning that new (full) Office 365 ProPlus installation will get a Teams instead of a Skype for Business Client.
The following slides and drawing are intended to provide you with an overview on licensing options. I also point out what you should take into account in case of Teams Direct Routing (TDR), in this post and following drawings I call a TDR scenario a “hybrid” scenario.
Telephony with Teams (for users)
Overview (May 2019)
Call Queues (CQ) and Auto Attendants (AA)
Call Queues (CQ) and Auto Attendants (AA)
Teams Common Area Phone (CAP)
Teams Common Area Phone
Teams Meeting Room
Teams Meeting Room
Conclusion, opinion and summary
The above drawings quickly depict how you can license users, common area phones, meeting room devices and even call queues or auto attendants for Microsoft Teams.
Microsoft is working on an enhanced licensing model for applications like cloud CQ/AA [as you can read in “Manage resource accounts”]. Still, at present user licensing applies for cloud CQ/AA.
Microsoft initiated a webinar series by Microsoft communication leaders and HR to share insights and challenges regarding modern communication and cultural transformation. There are several webinars from May, 16 to June, 26, 2019. The contents are, for instance, communicating better, storytelling, empower employees, effective internal communication, employee feedback and optimized communication on employee feedback.
Microsoft released a very important update in case you are planning or already operating Microsoft Teams Direct Routing. I’m very excited about this recent service update. The Call Queue (CQ) and Auto Attendant (AA) Services for call flows and call automation were updated for Teams Direct Routing.
What’s new with Teams Direct Routing (May 2019)?
Let me recap and point out the capabilities which were announced via the Teams blog by Microsoft:
Manage CQs and AAs via Teams Admin Center (instead of the legacy SFB Online Admin Center)
(Preview May 2019) Support for Teams Direct Routing Telephone Numbers in Call Queues (for Teams-only users)
(Preview May 2019) Support for Teams Direct Routing Telephone Numbers in Auto Attendants (for Teams-only users)
Centralized holiday tables (to cope with calls differently during holidays)
Multiple telephone numbers for an CQ or AA
Round robin call distribution for CQ
(planned, not yet there) Transfer a CQ/AA call to a PSTN phone number
(planned, not yet there) Dial extensions from AA
(planned, not yet there) Voicemail shared mailbox for CQ and AA
Please note, in case you utilize SFB Online CQ/AA capabilities already: There are some details for as-is CQ/AA which will be automatically migrated/transferred from the SFB Online Admin Center to the Teams Admin Center.
Conclusion, opinion and summary
I’m really thrilled and excited about these updates. Why? Well, if you were still on Skype for Business Server with Enterprise Voice there were some limitations especially regarding SFB Response Groups which now seem to be addressed with this update for Teams Direct Routing.
What does this mean for you? If you have loads of SFB response groups, e.g. Sales hotline, Support hotline, department … hotlines or else you can start to plan to migrate those to Teams with Teams Direct Routing. I.e. you can assign your onpremise phone numbers for this which you use via Teams Direct Routing (an SBC) which will route incoming PSTN phone numbers from your PSTN link via qualified /certified Session Border Controller (SBC) to Microsoft Phone System and Teams.
Isn’t it amazing? I was waiting quite some time on these capabilities. Well, online you could find some workaround to get this working via SBC SIP message manipulation (no big deal), however these workarounds were not support by Microsoft, so if there would have been any minor change on the Cloud Backend it could break things. And I’m sure you don’t want to have a workaround solution for important or even business critical hotlines which might not work all of a sudden? But now, there are the required capabilities to plan for shifting onpremise SFB Response Groups to (Teams Direct Routing) without any workaround (SIP message manipulations, call forwarding…).
