In November, Microsoft set a 1TB limit for Exchange Online auto-expanding archive mailboxes. Now they’ve retreated and the latest service description says nothing about a limit. The two changes in the service featured little or no customer communications and a total lack of any supporting material, like administrative controls to help manage archive mailboxes approaching the limit. While a limit has gone for now, it will be back.
Nine new REST-based PowerShell cmdlets are available for Exchange Online. They offer the prospect of better performance and reliability. Here are the code samples we used to test the new cmdlets for a theater session delivered at the Microsoft Ignite 2019 conference. Anyone wanting to explore the new cmdlets can use these examples to get going.
In a surprise development, Microsoft reversed course for Exchange Online auto-expanding archives and imposed a 1TB limit. The promise of a bottomless archive that continually expanded to cope with user data is removed. Although it’s reasonable for Microsoft to restrict the consumption of resources, suddenly implementing a limit is not, especially when you don’t communicate with customers.
The ability to see the PowerShell commands executed by Exchange administrative centers has existed since Exchange 2007. Now something has changed in Exchange Online and the command log is blank. It’s sad because many administrators learned to use PowerShell by examining how Microsoft used it to manage Exchange. Let’s hope that Microsoft fixes this bug soon.
Microsoft has implemented a new synchronization mechanism in Outlook ProPlus to deal more efficiently with shared folders. The new approach increases the limit from 500 to 5,000 folders and is a more elegant and precise solution. Users who manage other peoples’ mailboxes will appreciate the change after they install build 11629.20196 or later.
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…
You can use Exchange Address Book Policies (ABPs) to limit the ability of Teams users to chat with each other. Everything works as expected until you look for some new teams to join only to find that Teams can’t suggest any teams to you. The problem seems to be with filtering the set of teams returned by the Microsoft Graph to take account of the scope applied to the user. At least, that’s what I think is going on.
Outlook for Windows (ProPlus or click to run) now boasts settings to allow users to schedule meetings and appointments to end some minutes earlier than expected. Brian Reid is very excited by the prospect, but we’re not sure if this qualifies as one of Ståle Hansen’s famous lifehacks. In any case, ending meetings early won’t solve the problem of badly-organized or managed meetings or how people behave during meetings, but it might give you a quiet feeling of satisfaction to have a neater calendar.
Microsoft announced a new migration experience from Google G Suite yesterday, which is nice. Under the covers, the venerable Mailbox Migration Service (MRS) does the work to extract mailbox data from Gmail using IMAP4 and moves it to Exchange Online. But after the move is done, there’s still lots of work to do to help users make the cultural change to their new mailbox in the cloud.
It’s hard for a program that’s been around for 22 years to surprise, but Outlook has done it by introducing background moves. The implementation is good and it closes a gap that’s existed in Outlook for a very long time. So long that most Outlook users probably assumed that the program would never mend its ways. But then again, because people don’t move items between folders like they used to, perhaps no one cared.