Microsoft’s Compliance Manager is intended to help cloud tenants cope with regulations like ISO 27001 and GDPR. The Compliance Manager has a nice dashboard, but it is passive and offers very weak options in terms of organizing the work needed to achieve compliance. But Office 365 has Planner and Teams, and it is easy to create the necessary collaboration structure to allow people to work on GDPR controls.
A new premium Azure Active Directory feature allows you to force group owners to certify that external members should have continued access. Given that Office 365 Groups and Microsoft Teams now both support guest users, it is wise to check on who can access what from time to time. Whether you will want to pay extra for such a feature is quite another matter!
Microsoft has released a beta version of the Teams PowerShell module. The only problem is that the module is not very good. In fact, the module is very disappointing because it does not contain the cmdlets that an Office 365 administrator might except to automate operations around Teams. Maybe the 1.0 release will be better. We can only hope!
After returning from the Ignite conference, I have pages of notes to pour over. Here are some of the more interesting things i learned about Office 365, including who should be in my “inner loop” and “outer loop”, why Microsoft talks about Microsoft 365 when they really mean Office 365, and some Exchange Online cmdlets I had not heard about before.
Now that Microsoft has shipped external access for Teams, it is obvious that they have some work to do to smoothen access and increase functionality. Although access works as long as guest users have accounts in other Office 365 tenants, areas like switching, auditing what external users do, compliance, and blocking deserve some consideration. Here’s what we know from the last week.
Microsoft launched the long-awaited external access for Teams on Sept 11. The downside is that only Azure AD accounts are supported, but the functionality is sufficient to support interaction between Office 365 tenants. You can access a team in my tenant and I can access a team in yours. What’s not to like about that?
Microsoft has new tools to migrate public folders (the “cockroaches of Exchange”) to Office 365 Groups. Sounds good. The good news is that the tools work, even if they need a lot of manual oversight. ISVs offer tools to do the same job with more automation. The choice is yours!
Office 365 Groups and Microsoft Teams are two of the collaboration offerings available within Office 365. Some get very vexed about the two applications. I don’t because I think the two serve different audiences and exist for different reasons.
The quarterly cumulative updates for Exchange Server quietly appeared with little fuss this week. Meanwhile, in cloud land, Office 365 continues the crusade to eradicate distribution lists with new bulk conversions to Office 365 Groups.
Microsoft has updated Yammer so that new groups use the Office 365 Groups service to manage the identity and membership of the groups. There are far too many “groups” in that last sentence, which kind of illustrates how a surplus of groups might be building up within Office 365.
Office 365 Groups now support the addition of Exchange Online mail contacts as external group members. The new feature solves a problem for many tenants but it does not help you to convert old DLs that contain mail contacts.
Microsoft is very keen that Office 365 tenants should move away from email distribution groups to embrace the world of Office 365 Groups. There is lots to like about Groups, but I have some doubts about the way Microsoft is cajoling people to move.
Microsoft is convinced that Office 365 tenants should move from old-fashioned email distribution lists to embrace the new world of collaboration enabled by Office 365 Groups. A new conversation method allows OWA users to convert DLs that they own. Is it a winner?