Now that October 1 has arrived, Microsoft has started the process to permanently remove basic authentication from 7 email connection protocols. So what happens next? Well, for many organizations, not much. They’re the ones that have already transitioned to modern authentication. For others, some unpleasant surprises might lie ahead as people discover that stuff just doesn’t work anymore.
Microsoft Teams is getting a new calendar app to replace the cheap-and-cheerful meetings apps used up to now. Although the calendar app boasts new views and actions, it’s not the same or as powerful as the Outlook calendar. That being said, for many people, the new Teams calendar will be quite sufficient.
By the end of June, Office 365 tenants around the world will enjoy the chance to use the new announcement post type in Teams. I’m not altogether sure that the new post type will make our lives more productive, but it might brighten some of the boring announcements organizations are prone to make,
Microsoft has refreshed the Files channel tab to expose more functionality for Teams users when working with SharePoint Online document libraries.Office 365 commercial tenants should see the new UI in June 2019. The new Files channel tab is almost at feature parity with the functionality available through the SharePoint browser UI, but it still lacks the ability to expose and edit document properties.
Teams allows users to send email to channels via special email addresses. Those addresses aren’t very user-friendly, but you can add them as mail contacts so that channel addresses show up in the Exchange GAL. It’s easy to do and makes it much easier for people to email Teams channels. That is, until someone removes the channel email address…
If you’ve integrated Planner into Teams by creating channel tabs for plans, users are now notified when they are assigned new tasks.The notifications turn up in the Teams activity feed. Why? Well, the Planner bot sends messages to people about new tasks, so its chats as treated like new messages in a personal chat.
Two Office 365 Message Center notifications bring news about an increase in the number of participants for a Teams group chat to 100 and improvements in shareable links for files. Moving the limit from 50 to 100 for a group chat makes these conversations more flexible. Adding permissions to the sharing links used by Teams gives users more control over how they share information with others.
Teams deep links are probably not something you chat about a lot, but they can be used to start off a personal chat. In this post, we discuss how to insert a deep link in an Outlook or OWA signature so that recipients can contact you to follow up a topic started in email. It’s a quirky detail about Teams that might be interesting for you.
You can use Exchange Address Book Policies (ABPs) to limit the ability of Teams users to chat with each other. Everything works as expected until you look for some new teams to join only to find that Teams can’t suggest any teams to you. The problem seems to be with filtering the set of teams returned by the Microsoft Graph to take account of the scope applied to the user. At least, that’s what I think is going on.
Office 365 notification MC177587 tells us that Teams will soon start to move underused teams to the More section of the teams gallery, letting users concentrate on the set of teams that they really use. Background agents do the work of detecting teams that haven’t been accessed in 45 days or so and users get the chance to reverse the process. But it’s a good idea to let users know what’s coming, just in case they panic when they can’t find a moved team.
Office 365 notification MC177013 gives the news that team members can now nominate other people to join a private team. Teams routes the requests to team owners, who approve or deny access. It’s a small but useful update.
The Teams Admin Center now boasts the ability to delete teams and (if you don’t want to get rid of them altogether) archive teams. And unarchive teams back into use. All is good, even if Microsoft is making slow progress at building out Teams management functionality. Some of the slowness is due to dependencies, some because of other factors.
Office 365 Message Center update MC176548 says that Teams has started to roll out “Praise” a way of sending another user a graphical reminder of how much you appreciate their work. Undoubtedly, praising people in Teams will make the world a happier place.
Every Office 365 group (and team) has a SharePoint site. But how to find the URLs of all the sites used by teams in a tenant. One PowerShell answer came from Syskit, but it’s an old technique and we can do better now by fetching a list of teams in the tenant and then retrieving the URL for each team-enabled group.
Teams supports federated chat with other users in Office 365 tenants using a feature called external access. It’s similar to the way that Skype for Business federated chat works, except that you can’t use emojis. Generally things work very well, which is nice when you want to reach out and communicate with someone externally.
At the Enterprise Connect conference, Microsoft announced that Teams is now used by 500,000 organizations. That’s a jump of 80,000 since the last data given in January. They also said that 150 organizations have more than 10,000 users and that Teams is used by 91 of the Fortune 100. All in all, some impressive numbers.
Microsoft announced that the era of favorites and following is over for Teams. The new way is to show or hide teams and configure notifications for channels. Apparently, people found the old terminology confusing. Hopefully the new world of Show/Hide and Channel notifications will be more reassuring.
New data about the number of Slack and Workplace usage gives the chance to compare how Microsoft is doing with Teams. And the answer is that things seem to be going well, largely because Teams is growing off the huge Office 365 base. With 155 million users (the last figure) and 3 million more added monthly, Teams has a lot more to go after in the Office 365 installed base.
Microsoft Teams suffered its first major worldwide outage on 18 February 2019. Users reported a failure to connect because Teams couldn’t authenticate them. The Post-Incident report for TM173756 revealed an issue with the Azure Key Vault. What’s more interesting is that the issue affected users in multiple Office 365 datacenter regions, which is not good.
In one of those interesting (but possibly worthless) facts discovered about Office 365, we find that audit records are captured for Teams compliance records written into Exchange Online group mailboxes. The Search-UnifiedAuditLog cmdlet reveals details that we can interpret using some techniques explained in Chapter 21 of the Office 365 for IT Pros eBook.
Teams users can now set their own status message to inform co-workers about what they’re up to for the next few hours, days, or on an ongoing basis. It’s a small but useful feature that seems to have crept into Teams without much publicity!
A new report commissioned by Microsoft explains how Exchange Online and the Security and Compliance Center meet the electronic records requirements of regulatory bodies like the SEC and FINRA. Within the report, there’s some news about changes to the way that Office 365 handles Teams compliance records stored in Exchange Online. And after all that, we consider how some backup vendors treat Teams compliance records as equivalent to the data stored in the Teams Azure services.
According to Microsoft’s FY19 Q2 results released on January 30, Teams is now used by 420,000 organizations. That’s a strong growth rate over the 329,000 number given at Ignite 2018. And with Office 365 still growing, there’s plenty of room for Teams to expand.
The Shifts app is now available to Office 365 tenants worldwide. Hosted as a Teams app, the idea is that managers can build out and publish schedules for hourly-paid frontline workers, who can then view their hours and request changes.
Microsoft’s CMO says that the largest customer deployment of Teams (Accenture) has reached 170,000 users. Numbers like this underline the success of Office 365’s fastest growing application.
A survey found that Teams is now the second most popular chat application in large businesses and has put Slack into third position. But anyone who has tracked the numbers isn’t surprised because Teams has been growing strongly for some time.
Some recent questions in the Microsoft Technical Community show confusion about the email addresses used by Office 365 Groups and Teams. Here’s our attempt to clarify.
A reader asked if it is possible to add an administrator account to every Office 365 Group. This feature doesn’t exists OOTB, but it’s an easy task to script with PowerShell.
The latest version of the Teams desktop and browser clients support the creation of dynamic teams based on dynamic Office 365 Groups. The functionality is welcome, as long as you can pay for it as every member who comes within the scope of a query used for a dynamic team needs an Azure AD P1 license.
The new version of the Teams PowerShell module (0.9.5) supports a Get-Team that’s actually useful because it can return a full list of teams in the tenant. But there’s still some work to do…
Microsoft will retire the Windows S client for Teams on November 29, 2018. The decision to double-down on the Electron-based client is probably due to the fact that not many people use Windows S.
Do you need to remove some offensive or otherwise doubtful material from Teams? If the original author won’t do the right thing, the team owner or an Office 365 administrator might have to step in to do the right thing.
When you impose a block on certain domains, you’d like to think that applications like Teams will respect that block. As it turns out, if you have some lingering guests in your Azure Active Directory, the B2B collaboration policy might not be as effective as you’d hope.
Tony spoke about “Can Teams Replace Email” at the Modern Workplace Conference in Paris on October 17. Here’s a sketch note about what he said and a copy of the slides.
The Teams T-Bot is no more and has been replaced by a snazzy new help “experience.” No doubt this is good news for those who consult help on a regular basis, but it won’t help Office 365 tenant admins much.
The prospect of having to pay for many Azure AD Premium P1 licenses just because you use an org-wide team is horrible to contemplate. But don’t worry. You don’t have to because the Teams developers look after membership updates for you.
Slack is the most obvious competitor for Microsoft Teams. The question is how many users does each platform have? Here is our best guess.
A simple question asked where Teams stores its Wiki content. A search found that the Wiki is stored in a SharePoint document library, while some further investigation discovered some interesting facts about the Teams wiki.
The news has emerged that Microsoft won’t provision new Office 365 tenants with Skype for Business Online unless they have more than 500 users. Any smaller and the tenant gets no choice but Teams.
Microsoft has documented how organizations using the free version of Teams can upgrade to the full enterprise version (and Office 365). It all seems pretty easy, which is good. Paying those Office 365 licenses mightn’t be as nice.