As Office 365 Groups and Microsoft Teams continues to explode in popularity, the ability to explore and control resources in large scale is becoming more apparent. While there are some basic controls available, those specifically included in the Teams PowerShell Beta module leave a lot to be desired. The Teams module currently only allows you to get information about Teams that you are actually in, thus very limited in the benefits to an administrator.
One of the tasks I have come across is the need to get a list of Teams, along with the members and owners of each. 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.
Microsoft Teams continues to get new functionality and I saw a nice addition just the other day. The ability to quickly create a survey in a channel conversation without leaving the app or even adding Forms as a new tab makes collaboration with your team more seamless.
Along with an Office 365 subscription, you get Microsoft’s mail filtering solution Exchange Online Protection (EOP). You can also subscribe to EOP if you are running on on-premises mail solution.
One nice feature of EOP is that it can be configured to detect and block outbound spam. IF When a user account gets compromised (or maybe you have legitimate spammers) Microsoft can block the ability for the account to send any more outbound mail until you have addressed the account and unblocked it. This is great until you have an outbreak of compromised accounts, likely due to phishing victims, and need to remove multiple blocked addresses. So how can we do this?