For market observers, in this post I want to notify about Microsoft Build 2019. The event takes place in Seattle, WA from May 6th – 8th, 2019. It’s all about development around Microsoft products and services, e.g. containers, artificial intelligence, machine learning, DevOps, IoT and mixed reality.
Conclusion, opinion and summary
At the time I wrote this post there were no details regarding live streams available. Nevertheless, I’m pretty sure there will be a live stream at least for certain sessions available. I guess on the Build 2019 page and Channel 9 you might be able to watch the keynotes and later, after the event you could find recordings of certain sessions there. So, stay tuned for more details on the below pages as the event comes closer.
I stumbled upon a new feature which is under development for Microsoft Teams. Belief it or not but on the official Microsoft 365 (M365) roadmap “Microsoft Teams: Busy on Busy” (short, abbr. BoB) appeared in the list. It’s planned for May 2019.
What’s “Busy on Busy”?
Well, this feature gives a caller a busy ton or sound in case the callee is busy with another call/meeting. So, you as a caller then now “Ah, well the person I’m calling is busy, right now. I’ll try it later, send an IM or mail …”
Do you need this?
It depends. It’s a frequently and common feature in Germany. Most people are used to it. In US and other countries it is not so widely used as far as I’m aware of. There is a little different “telephony mindset”, e.g. “If I cannot get a call because I’m busy the caller can leave a voicemail… or it is forwarded to my delegates/assistant …” or “The caller can try another communication option…” That’s why it depends if you need it or not. In general to have it is a good idea so you can decide if you enable it for all or a few users (depending on how the feature can be configured after it’s development).
Conclusion, opinion and summary
I remember, in the past, that the announcement of Busy-on-Busy for Skype for Business Server was a big deal. Many customers in Germany were waiting for this nativ feature for SFB. It was released as part of a SFB Server 2015 cumulative update. The busy-on-busy implementation was not 100% as some customers expected it to be. Compared to their known and legacy busy-on-buy feature by their legacy PBX. However it was adopted partially. And third party app and tools for this previously SFB Server 2015 feature gap vanished. Finally, I’m sure Microsoft Teams Busy on Busy will be adopted by some Team users instead of or even supplementary to voicemail, call forwarding or else depending on the configuration and assignment options for BoB.
Please note that this post and its contents might be subject to change. Especially, because it was added and last modified on April 1, 2019.
In this post I’d like to note a recent announcement which improves the admin experience to manage apps and integrations in Microsoft Teams. To keep it short and simple, the following configuration options were announced by Microsoft:
Teams App Setup Policies – Who get’s which apps displayed?
Teams App Permission Policies – Define who can install which apps
Bulk Assignment via PowerShell – Assign the above policies by using a PowerShell (Script and CSV)
Conclusion, opinion and summary
To me, these two options for managing apps and integration will help to enable what Teams users need or don’t need. Plus it’s another step in the right direction towards a more comprehensive and granular management of Microsoft Teams as a hub for modern teamwork.
In this post I’d like to highlight and share resources about Teams devices and IP Phones. Does one of the following questions or even both apply to you?
Are you planning to transition your conference rooms to collaborative spaces and rooms?
Are you planning to migrate telephony completely or partially to Microsoft Teams?
In both cases, to begin planning, I recommend to browser to and do not miss to check the below links. Microsoft as well as third-party vendors offer a wide range of devices to cover your needs by leveraging the Microsoft Teams platform. The best place to go and check for (certified) devices is the “Microsoft Teams Devices Marketplace”. There you’ll find …
Conference phones and
Conclusion, opinion and summary
I recommend to take a look on the linked pages to get an overview on available certified devices.
If you are about to start your journey towards Microsoft Teams it might help you assess your users/rooms /spaces requirements and to create suited personas (e.g. 6-Seat-Room –> Surface Hub, Office Information Worker –> Notebook + wired Headset, Assistant –> Notebook + Mobile + Teams IP Phone xyz).
In this blogpost I’d like to describe on a high level what you can do regarding backup (and restore) Microsoft Teams chats and files (January 2019, this might be subject to change). Do you need backups of Teams (data) stored within a global hyperscaler cloud infrastructure? Shouldn’t it be resilient and highly available based on the SLAs …? Well, there is no one-size-fits-all-answer. It depends on your requirements and needs. However, in my opinion, it’s not a bad idea to have a (working) backup in place in case data was deleted or became inaccessible, anyhow.
Where are my Teams conversations and files located?
We need to
differentiate between actual Teams and Chat (see screenshot below, I’ll call it
hereinafter “Personal Chat”). “Personal Chat” are direct
one on one (1:1) as well as one to many (1:m) chats or conversations. The
difference is what’s being used under the hood. Let’s dig in a bit deeper.
Your chats are stored on your Exchange Online (EXO) Mailbox in an hidden folder (not on Exchange Server). The hidden folder “TeamChat” on your EXO mailbox is underneath of the “Conversation history”-folder. By default the chat copies are available for 14 days in the Deleted Items folder in Outlook.
Teams are Office
365-based, i.e. Office 365 Groups with SharePoint Online and Exchange Online
For Teams Chats almost the same as for “Personal Chat” applies: Due to the fact that we therefore have Office 365 Groups, its mailbox hidden folder on EXO (not Exchange Server) are the storing the chats.
If you exchange files it will be stored in your OneDrive For Business\Microsoft Teams Chat Files.
If you share files
in a Teams Channel it will be stored in its associated SharePoint
Online Document Library Folder of the Teams channel.
By default deleted files on SharePoint online are available for 93 day to be restored if no other configuration was set or quotas are applied and excceeded.
What backup and restore limitations do I have (after a “soft-delete”period)? (January 2019)
If a Team was
deleted and you notice this or get requested to restore a Team after the
“soft-delete” period of 30 days (default) the content is permanently
deleted and cannot be restored, see link at the bottom “Restore a deleted
Office 365 Group”.
You cannot restore a
Team 1:1 after its 30 days “soft-delete” period.
Chat even if you have the data cannot be restored or at least I did not find a way to accomplish this easily. I was thinking about importing chats based on scripts in a newly re-created Team and it’s channels but it seemed to be a way to cumbersome to quickly test it with some lines of ps script code.
backup options are there?
1: Archive Teams
Archiving is not backup. However if you archived instead of deleting it, you can restore it easily via the Teams Admin Center or via the Teams Client, see link at the bottom “Archive or restore a team”.
2: Office 365 Security and compliance
center (eDiscovery cases, retention policies)
You can maintain copies of chats by using eDiscovery cases/litigation/inplace hold/retention policies. You can set this up to store the copies hidden in the mailbox. Either for a certain periode of time or indefinitely.
You can configure retention policies to retain files longer and to be stored in the preservation hold library. However, you might search and access the retained chat/files but not within Teams as it were before the “permanent” delete.
Option 3: Thirdparty solution/s?
Most of the thirdparty backup solutions are offering options to backup Exchange Online, SharePoint Online and OneDrive For Business data. Some providers also mention capabilities to restore Office 365 groups but it needs clarification if they have working restore procedures to recover a deleted Teams after the default “soft-delete” period of 30 days. If you consider to leverage a thirdparty solution you should take this into account for your Microsoft Teams evaluation and proof of concept phase.
If a Team get’s
(soft) deleted you can restore it within 30 days by default.
Beyond 30 days,
there no default or extend restore procedure to get the deleted Team to 100 %
recovered as it was before.
might provide an exception to a certain extent and add value based to
extensible restore capabilities which should be thoroughly examined during an
evaluation or proof of concept phase.
First of all, happy new year! I’m looking forward to all the new opportunities, features, services and integrations around communication and collaboration at the modern or digital workplace. The fresh new year will bring us some new capabilities to do more with Microsoft Teams as well as related apps or services.
To me, the most noticeable Microsoft Teams capabilities which we’ll probably see in 2019 are (01/01/2019 might be subject to change):
Shared Line Appearance – Allows multiple calls on a single phone number with delegates who can answer the calls.
Call Park – Park a call “on hold” and grab the call from another endpoint to resume the call by using an unique code, e.g. #150.
Location Based Routing (LBR) – Route PSTN voice calls based on the location, e.g. emergency call outbreaks for roaming users…
Group Call Pickup – This enables a group of users to pickup / grab an incoming call for a colleague.
Yammer Tab in Teams (Preview) – Easily access Yammer via a tab
SharePoint web parts as tabs in Teams – Direct access SharePoint web parts via a tab in Teams
Screen sharing in a private chat session – Without calling you can share you screen
Support for Oracle SBCs in Direct Routing
Safe Links Protection for Microsoft Teams – Protects users from opening bad / malicious links
Create an org-wide team (for up to 2,500 users) in Microsoft Teams
Broadcast Meetings – Town-hall-stlye / large meetings via Teams
Team Templates – Pre-define Teams and re-use this template to provision a team
The above mentioned features and capabilities might be subject to change. This post is just a list to quickly recognize what we could get soon with Microsoft Teams. For more, stay tuned here or directly on the Microsoft 365 Roadmap:
Rolling out and adopting Micrsoft OneDrive for Business (ODFB) is a great opportunity to get rid of your legacy onprem file servers, shares, local device saved data and roaming profiles etc.
ODFB enables you to access your files from a versatile set of endpoints (PC/Mac/common Browsers/iOS/Android) and keep your data safe and in sync. You can also share certain files with others as needed. However, ODFB is one part for storing data. It is primarily for your documents. Working requires also other options for data collaboration, distribution and sharing therefore you might want to consider SharePoint Online as backend for storing files within your company, department or team.
To start and abandon your legacy file repository you can find supportiv guidiance and details for ODFB, e.g.