Back in July 2018, Microsoft released new functionality to Microsoft Teams that would migrate existing contacts and contact groups that you have configured in your Skype For Business client into Teams. Specifically, the release details were:
Bring your Skype for Business contacts to Teams When your organization moves from Skype for Business to Teams, your contacts will make the move with you. To see them, once you’re in Teams, click Chat on the left, then Contacts at the top.
During a recent migration from Skype for Business on-premises to Teams, though, I encountered a user who had multiple groups and contacts but none appeared in the Teams client. The fix was quick and painless.
As I filtered through the 1700+ sessions leading up to Microsoft Ignite, I quickly knew that unless I was able to clone myself I would have some catching up to do. Rather than try to sort through all of the sessions again later, I made a playlist of sessions that I’d like to go back and watch.
The playlist is a compilation of 70+ videos and 24+ hours of content, mostly in the Azure and Office 365 arena since that is where a lot of my focus is these days. Is there a session that shouldn’t be missed? Feel free to let me know what should be added!
As Microsoft Ignite 2018 nears, I am busy preparing my schedule for the week. Part of that preparation is planning for discussions I would like to have with product group members, MVPs, and other peers. I also have some other things that I either think (hope) will happen, or at least want to hear more about. Without further ado, here are 5 things I’m either hoping for or looking forward to at Ignite this year: Continue reading →
A few weeks back, June 26th specifically, Microsoft announced archival functionality for Teams. Archiving a Team does just what you’d expect by keeping the Team itself, but freezing changes to preserve the current state of the data. There are a couple of things that I found interesting, and good to know before you get started.
While troubleshooting an issue recently, I noticed failures showing up in the Azure Sign-In Activity panel with a sign-in error code 50140. The error code gave the following details:
This error occurred due to ‘Keep me signed in’ interrupt when the user was signing-in. Open a support ticket with Correlation ID, Request ID, and Error code to get more details.
This was happening for a variety of single-sign on enabled applications. Upon testing, the user logged in and was prompted with KMSI as expected. They experienced no trouble either when selecting Yes or No to the prompt. After opening a case with Microsoft, and reaching out to someone on the inside, both confirmed that this was more of an anomaly in the logs and could be safely ignored. It sounds like this will soon either be resolved or changed to an Informational message instead.