Microsoft released its Office app for mobile. It’s available in the respective app stores for Android and iOS. It’s a single app which covers Word, Excel and PowerPoint. So three single apps become one.
A single app is definitely a good idea in case no functional is cut off due to consolidation into one app. I just tested the app a little bit and its very straightforward and easy to use. In case your are already using Outlook, Teams, OneDrive for Business on your mobile or your connected with your Office 365 account the new app signs in directly, shows a start splash screen and a short intro and you are ready to go.
On the home screen you can seen your recent documents and the navigation drop down offers you to go to Word, Excel, PowerPoint, PDF, Media or Notes.
In the Office apps settings you can enable/disable “Download most recent and recommended files”. By default it’s enabled so it downloads files to your mobile so that you can directly start to work on recent documents. Also by default, download via mobile network/data is disable if the above feature is on but of course you can enable it in case you roam a lot.
Nice app to access your files within a single app, no need for a app switch between Excel, Word and PowerPoint anymore. Some nice and new features are convert a picture to (Excel) table, convert images to files and sign PDFs. More features and improvements are already planned and announced.
In this post I give you an architectural overview on thoughts, ideas and options to a more secure communication and collaboration experience with Microsoft Teams.
It’s inevitable to provide a secure, modern and usable (!) solution for your users, your company and keep identities and [information] assets secure. I want to emphasize usable because you can surely set up a highly secure service, however, if you do so, nobody might be able to use it because you locked it too restrictively. So, this will probably cause other headaches, first of all users need to get work done and might workaround that highly secured service [just using anything else which they find online]. No adoption. Hence, the added value of the communication and collaboration solution and the ROI will never be achieved. That’s why you need to figure out a suited balance between security and collaboration.
Microsoft Teams as part of the Microsoft 365 cloud services can leverage these comprehensive security features to enable a secured communication and collaboration. Besides the fact that Microsoft encrypts data in transit as well as at rest.
The following slides contain what you could do to secure your Microsoft Teams communication and collaboration experience by not giving up usability and a modern teamwork experience.
Beyond these basic security considerations in the slides you could, of course , also make further and more granular optimizations, for example …
in the Microsoft Office 365 Admin Center
in the Microsoft Teams Admin Center
in the Microsoft SharePoint Online Admin Center
in the Microsoft One Drive for Business Admin Center
in the Microsoft Exchange Online Admin Center
as well as in other Microsoft Admin Centers
Conclusion, opinion and summary
Microsoft 365 enables you to secure Microsoft Teams and Office 365 with the eligible licenses. There are many aspects around securing your modern teamwork experience. It starts with general identity and information protection and goes ahead with fine tuning Microsoft Office 365, Teams, SharePoint Online, Exchange Online, Yammer etc. There are some bigger and some smaller switches to be aware of and to configure modern teamwork secure. E.g. guest access, external access (federation), message policies, meeting/conferencing policies, app setup policies, app permission policies and many more. At least but not at last you also should think about monitoring and auditing so that you’ll be able to trace things in case it is required.
This post is about the improvements Microsoft made to the AI Builder in Power Automate (previously know as Flow). The subjects for the major enhancement is the data input and output for the AI models. The big benefit is that there is no longer the need that you transform the data at the beginning. Now AI builder does that that for you based on the AI model which you can train for that.
In this post I provide an overview on key capabilities with modern meetings with Microsoft Teams. It enables you and your fellow co-workers for modern meetings [almost] anywhere, anytime and on [almost] any device.
Microsoft Teams offers you the following key capabilities for meetings but are not limited to these:
interactiv application and desktop sharing
dialin phone numbers from 65+ countries around the world
versatile clients and devices (mobiles, rooms, browsers, Windows, Linux)
recording – transcript – for many languages (speech-to-text to transcript)
calendar integration (Outlook, Exchange, Teams)
Do more with Microsoft Teams Meetings
Microsoft Teams enables for modern meetings so that you can easily communicate and collaborate, either in a planned or scheduled meeting. No matter if you are in transit, in a meeting room, at a desk or any other space. The things you need are the right equipment as well as a sufficient connection, i.e. Internet or in case you are in transit at least cell coverage to dialin by phone.
Microsoft and partners offer many certified devices for Microsoft Teams depending on your needs and requirements to get that modern meeting experience for your users. Therefore you can get a glimpse on the “Microsoft Teams enabled devices” page to explore and discover what kind of devices are available and what devices are suited for which meeting space or scenario.
Basically, there you can find
Headsets | user devices
Speakerphones | lightweight and compact user/room equipment
Desk phones | IP phones for users, lobby or other user cases
Room systems | for collaboration in meeting rooms and spaces
Conference phones | for conference rooms
Cameras | for users, rooms and other spaces
Conclusion, opinion and summary
Modern meetings with Microsoft Teams are easy and offer all the above key capabilities which are important to users today. Users get enabled to do more with Teams meetings and make meetings more productive and more fun, too, because client and device capabilities are available and easy to use and access with no frills and unhandy controls or preparation tasks for a Teams meeting. You can just meet, collaborate and focus on what you need to do.
In this post I highlight a study publication by Forrester regarding Microsoft 365 Cloud Voice. Forrester is a market research and analysis company focused on the information technology sector. Microsoft mandated Forrester to carry out the study on Microsoft 365 Cloud Voice.
What’s the study for?
The so called TEI (short for “Total Econonomic Impact”) study examines Microsoft 365 Cloud Voice in regards of
What does the study say?
To sum it up a little bit the study provides the following key aspects:
employees save time due to telephony integration in Microsoft Teams
integration enhances business outcomes
Microsoft 365 Cloud Voice enables companies to replace legacy telephony systems (PBX/s)
costs for telephony are reduced
better security and compliance because of its integration in the Microsoft security and compliance capability stack
higher availability as (legacy) PBX
better performance as (legacy) PBX
better scalability as (legacy) PBX
higher employee/user satisfaction especially for younger employees
reduced total cost of ownership (TCO)
Well, for details, I’d recommend to read the study by yourself [see links at the bottom].
Conclusion, summary and opinion
In my view the study can be seen as supporting document for you in case your are about to decide on what’s next for your company’s telephony due to ending support or just because you want to embrace modern workplace at your company. The study gives you some numbers, facts and figures for further consideration, evaluation and decision making.
Microsoft rolled out read receipts in Teams. It shows you if your messages were read or not. By default it’s enabled. You get a popup that read receipts is available and how it looks like. In this post I provide an overview.
In the Teams client settings you can disable or enable it depending on what’s configured in your Office 365 tenant.
Teams Admin Center
If required, a Teams administrator can configure read receipts by modifying Teams messaging policies in the Teams Admin Center as depicted below.
By default, read receipts are on and the message policy configuration is set to“User Preference” which means that users can disable it within their Teams Client settings.
Turned on for everyone: It’s enabled for all users and a user cannot turn it off.
Turned off for everyone: It’s disabled for all users and a user cannot turn it on.
Limitations [January 2020]
The “Manage messaging policies in Teams” documentation says
it is for 1:1 chat or chats with up to 20 people
it is not caputered in eDiscovery reports
Conclusion, opinion and summary
It’s another neat feature to easily recognize if your chat message was read or not. Thus you can decide how to react, e.g. send a priority notification or make a call.
In this post I give you an architectural overview on how you can connect analog devices, e.g. fax machines, analog phones, door bells, intercoms etc. to Microsoft Teams.
First of all, I’d recommend to please get rid of your analog devices. Let me guess you are probably reading this because you have some of these poor and legacy analogs which you cannot get rid of for some reasons?
If this is the case: Well, ok, let’s go ahead to keep your existing investments in analog devices and get it to work.
If not, i.e. you can get rid of them: Skip this post and read something more interesting. 😉
The goal is to add analog devices to a Microsoft Teams voice/telephony deployment.
Use Cases – Analog Telephony with Teams user and PSTN
The uses cases are defined as follows:
call from an analog device to a Teams user
call from a Teams userto an analog device
call from an analog device to a PSTN (external) phone (number) [e.g. mobile phone]
call from a PSTN (external) phone to an analog device
In this architectural sketch you can see a high level Microsoft Teams Direct Routing deployment including an analog device which is connected via an anlog [device] gateway.
[left] PSTN sip trunk [from your PSTN provider of choice],
[center] a (certified) session border controller (SBC),
[center] a analog [device] gateway
sip trunk between analog gateway and SBC
analog link (FXS, RJ11) between analog gateway and analog device
[center-right] analog device [connect to analog gateway]
[right] a Microsoft Phone System sip trunk
[right] a Microsoft Teams User
What are the requirements for this? To keep it short, you need:
Teams Direct Routing (TDR) [for details, please see Plan Direct Routing]
Analog [Device] Gateway
Note: In case you have Microsoft Teams and utilize calling plans for telephony already but need these analog devices added you can add Teams Direct Routing to what you’ve got already.
Conclusion, opinion and summary
To sum this up, to connect analog devices to your Microsoft Teams deployment you need Teams Direct Routing (TDR). Then you can attach an analog device to an analog (device) gateway which is linked to a certified SBC for Direct Routing which handles the voice routing (from/to PSTN/Microsoft Phone System/analog gateway).