One feature that stands out with Office365 Exchange is the great native spam protection it offers. My only complaint is that there is no administrative email you can configure that will show you what has been getting caught in the Quarantine. Microsoft offers ‘End user spam notifications” that will send an email to the user showing what has been quarantined for their account, but it also gives them access to release that message. Given that I still have a relatively small number of end users (160), I wanted to be the one deciding whether or not the message was actually spam.
I was recently faced with a very frustrating problem in regards to uploading user photos over 10KB into Office 365. Their online documentation states that “The “native” size of user photos is around 100×100 pixels, with a file size of 10 KB”. First of all, that is an extremely small and grainy photo, and shrinking my original 2 MB photo down to 10 KB left the picture very distorted. Regardless, using the Set-UserPhoto cmdlet, I was only able to upload a 4KB photo at about a 60×60 resolution. Anything over that would give me “The remote server returned an error: (413) Request Entity Too Large…” I opened a ticket with their online support and after weeks of back and forth emails and phone calls, their support technician told me that this was an issue and there was nothing to do about it except wait for Microsoft to release a fix.
I recently took my company of about 140 off of our current POP/SMTP email system (yes, companies still use POP for email) and onto Microsoft’s Office 365 Hosted Exchange. They give you PowerShell access to your Exchange 2013 server so there is a lot you can do to help reduce the time it takes to get your environment ready. Here are some quick and easy PowerShell scripts I wrote to assist with my transition.