A reader wants the benefits of dynamic Office 365 groups without having to pay for Azure AD premium licenses. It’s relatively straightforward to maintain the membership of a group with PowerShell. That is, if your directory is accurately populated and the right results are returned when you look for who the set of group members should be.
Despite the age of the protocols, you can cheerfully connect a wide range of IMAP4 and POP3 clients to Exchange Online. If you do, you might need to consider how to handle calendar appointments, and if you want to use iCAL, you’ll need to make some adjustments with PowerShell.
Exchange Online supports inactive mailboxes as a way to keep mailbox data online after Office 365 accounts are removed. Inactive mailboxes are available as long as a hold exists on them. You can update mailbox properties to exclude all or some org-wide holds. If you exclude holds from a mailbox, you run the risk that Exchange will permanently remove the mailbox. If that’s what you want, all is well, but if it’s not, then you might not be so happy.
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…
Teams App Setup policies allow tenant administrators to modify the set of apps shown in the Teams navigation bar,. You can add your own apps and move apps around and then assign policies to select groups of users individually or using PowerShell. This is part of a set of features designed to make apps more manageable within enterprises. The next step will be Teams app permission policies (not yet available).
Office 365 supervision policies can now make use of artificial intelligence and machine learning to detect offensive language in email and Teams communications. The data model covers a wide range of problematic language, but only in English. You can go ahead and cheerfully continue to swear in French, German, and other languages with no danger of being detected by policy.
A recent report puts the availability of Azure behind Google and Amazon Web Services (AWS). Office 365 tenants depend on Azure in a variety of ways. The recent problems occurred in a variety of places and there’s no common thread connecting the different issues. It seems like Azure has had a run of bad luck, so let’s hope that the bad days have passed and reliability improves.
The CISA report titled “Microsoft Office 365 Security Observations” makes five recommendations to improve security of an Office 365 tenant. The recommendations are valid, but competent administrators won’t take long to implement them. In fact, the worst thing is that consultants brought in to help organizations didn’t seem to have much expertise in securing Office 365.
The Groups section of the Azure Active Directory portal now includes a preview of a feature to configure the Office 365 Groups naming policy without going near PowerShell. Although those proficient with scripts and GUIDs will lament this sad reduction in standards, the normal administrator will welcome the chance to forget some obscure syntax.
The writing team has released update 14 for the Office 365 for IT Pros eBook. Fifteen out of twenty-four chapters are updated, so the new files should be downloaded and used to make sure that you have the latest content. This is the last major update for the 2019 edition as the writing team is now focused on creating the 2020 edition for publication in July.