All about Microsoft 365
One of the differences between on-premises Exchange and Exchange Online is the way user mailbox objects are provisioned, or de-provisioned. In the on-premises world, this is of course dependent on the underlying AD, but as long as you have the necessary permissions you can provision a new user, along with …
In a previous article, we covered the scenario of bulk-disable a specific Office 365 service/plan for a group of users via the Azure AD PowerShell module. The script is fairly simple – it gets the list of users, iterates over each of them and adjust the licenses based on the …
Continue readingBulk enable specific services via the Azure AD PowerShell module
The new year greeted us with an interesting glitch, or intentional change, with the way Exchange Online PowerShell displays some properties. As first reported in this TechNet forums thread, suddenly we were seeing different values for properties such as the Retention policy, all of them being prefixed by the tenant …
Continue readingTemporary glitch in the way Exchange Online object identities were returned
Short and quick – it seems that at least some of the Billing notification emails that Microsoft is sending to Office 365 customers now come from a new email address, namely maccount@microsoft.com. And when I say some, I do mean some – out of three billing notifications I’ve received today, only …
Continue readingChange in Microsoft’s billing notification email address
This seems like a relatively new addition to the service, but it is now possible to block users from attaching files when composing messages in OWA. To set those restrictions, you will need to use the OWA mailbox policy cmdlets, and toggle the value of the ClassicAttachmentsEnabled parameter. Here’s an example: …
Continue readingPreventing users from attaching files to messages via OWA