Office 365 Groups and Teams can hold tons of secrets that we don’t want to share outside our organization. To keep sensitive information secure, you can block guest users from groups by setting a directory policy on your most important and confidential groups.
In today’s Ask the Admin, Russell takes a look at Azure AD Password Protection and why Microsoft believes it will improve Active Directory security.
Office 365 apps like Teams, Groups, Planner, and SharePoint support guest user access, so they create guest accounts. Those accounts are pretty bare-boned, but you can liven them up by adding details, including user photos – which you might just copy from LinkedIn.
A free version of Teams is now available and it’s pretty good. Up to 300 users, free storage, and lots of functionality – and a phantom Office 365 tenant (or so it seems). The nice people at Slack might not like what they see, but there’s fierce competition to secure the hearts and minds of those who choose to collaborate using a free platform.
Microsoft Teams now shows team owners when their team is going to expire – that if, if you use the Office 365 Groups expiration policy. But tenant administrators don’t have a report showing them when groups expire, so we wrote one in PowerShell for you to use (and improve).
Office 365 makes it easy to collaborate with external users through Office 365 Groups and Teams, both of which use Azure B2B Collaboration. In fact, collaboration is so easy that users might be carried away and share with all and sundry, including your competitors. Which is why it’s nice to have a policy to control sharing with certain domains that works for applications like Groups, Teams, and Planner.
It is nice to have an Azure Active Directory Expiration Policy for Office 365 Groups, but it’s not so good that the policy functions exclusively based on age. Another problem is that administrators have no way of knowing when groups will expire. So we take out PowerShell, write a script, and hey presto, we have a report. We still need to solve the problem of creating a policy that functions based on activity rather than age, but that’s another day’s work.
Tons of Spring Updates in the Office 365 space to cover this month. As always, it will be the news you need with the two cents you don’t.
Learn a few of the best practices that businesses today are using for the hybrid cloud to make sure you get the most bang for your buck.
Office 365 now supports external access to Teams for guests with any email address, a development that creates some questions in the minds of those who might want to add guests from non-Office 365 domains. In this article, I try and answer some common questions that you might have about guest access.
Six months after allowing users from other Office 365 domains to access Teams as guest users, Microsoft now supports access from any email address. You can now invite people to join teams from Gmail, Yahoo! Mail, Yandex, Outlook.com, or any other email system. The same basic Azure B2B collaboration flow is used to invite guests and redeem the invitations, so it should be a well-worn path for administrators at this stage.
A recent vacation meant that I didn’t spend as much time as usual monitoring changes inside Office 365. As it happened, lots of change occurred. The large stuff (major updates for Teams and Planner) has already been covered in detail, but many other small but important changes are now active inside Office 365. And, as always, it’s the small stuff that can trip you up. Here’s what I learned after a weekend of catching up…
There are five things every business should know about the hybrid cloud before you move to maximize your efforts.