IT Decision Maker

Blog archive

Our Office 365 Experience: Part 1, The Decision

My company, Concentrated Technology, recently made the leap from Google Apps to Office 365. We mainly work with Microsoft products and we figured "what the heck." In addition, we were really dissatisfied with Google Docs. The inability to create a true folder hierarchy, the difficulty of sharing sets of documents with external contractors...it was just a bit much. We all use phones that are Exchange Server-compatible, so we wanted to get some of the advantages of Exchange. While Google emulates Exchange pretty well, it doesn't have quite the same calendar sharing and other features that make Exchange great.

Deciding on an Office 365 plan was the toughest decision. The various "P" and "E" plans all offer different features. We initially leaned toward the P1 plan, but after reviewing its limitations, we worried that it might not be enough for us. Keep in mind that you can't ever migrate from a "P" plan to the larger "E" plans, or vice-versa, so if the biggest "P" plan might not suit you forever, then you need to up the ante and go "E."

The fine print was also a bit troubling. The "P" plans, for example, have a hardcoded e-mail limit of 500 recipients per day. Per day. If you've got a dozen users, that's actually not very many outgoing recipients -- just about 40 recipients per person, per day, which is something we felt we could easily exceed. The "E" plans have a much larger limit. This is actually the most troubling thing about Office 365; I understand why Microsoft does it (to help prevent O365 from becoming a spam source), but there has to be a better way to achieve the goal than an across-the-board cap.

1/19 UPDATE: I was contacted by a Microsoft spokesperson today who said this limit has been lifted; the number of recipients is no longer capped at 500.

A final caveat: Because two company's two owners are journalists, we'd both been involved in the O365 beta, as well as in a "P" plan trial. That meant the accounts we'd created for those purposes couldn't be used for our new, permanent account. So instead of getting "concentratedtech.onmicrosoft.com" as our account base name, we had to pick something else. Of course, once we migrated, nobody would see that base name because we'd use our own domain name, but it's something to be aware of: If you do a trial, either use a totally fake name, or use the name you plan to proceed with and stick with it.

Up next: The Migration

In case you missed it:

Posted by Don Jones on 01/18/2012 at 1:14 PM


Featured

  • Spaceflight Training in the Middle of a Pandemic

    Surprisingly, the worldwide COVID-19 lockdown has hardly slowed down the space training process for Brien. In fact, it has accelerated it.

  • Surface and ARM: Why Microsoft Shouldn't Follow Apple's Lead and Dump Intel

    Microsoft's current Surface flagship, the Surface Pro X, already runs on ARM. But as the ill-fated Surface RT showed, going all-in on ARM never did Microsoft many favors.

  • IT Security Isn't Supposed To Be Easy

    Joey explains why it's worth it to endure a little inconvenience for the long-term benefits of a password manager and multifactor authentication.

  • Microsoft Makes It Easier To Self-Provision PCs via Windows Autopilot When VPNs Are Used

    Microsoft announced this week that the Windows Autopilot service used with Microsoft Intune now supports enrolling devices, even in cases where virtual private networks (VPNs) might get in the way.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.