Posts by
Nathan is a five time former Microsoft MVP and he specializes in Exchange, Microsoft 365, Active Directory, and cloud identity and security.
One situation I see often with customers is the desire to control and monitor file downloads from the cloud. For most organizations in most industries, it’s important to control your organization's data, and that data is often contained in files. The proprietary nature of information in files makes them very valuable to many organizations, and thusly important to control.
If you've ever participated in an Exchange Online migration at almost any level, it's likely you've run into the issue of cross-forest delegation. You know that Exchange allows you to delegate rights from one mailbox to another, allowing users to access other mailboxes. When you do an Exchange hybrid migration, there are some special considerations you have to take to keep these delegated rights working.
I expect we all know there are limits to what you can and cannot do with your Exchange Online mailbox. We all know there is a limit to how many emails you can send and receive, how much storage you can use, how much data you can move into or out of Exchange Online, and how big each individual email can be. However, I find that few Exchange Online administrators know exactly what those limits are, how they work, why they are there, or what you can do about them.
I imagine that about a week after the first customer was on-boarded into Office 365 they decided that they needed to do a tenant-to-tenant migration. While that is probably not how it went, I suspect I am not too far-off reality with that one.
There's a lot of content out there about backups for Office 365. I personally have written and spoken a lot about backups for Office 365. If you ask 10 experts, you will probably get 10 different opinions about how, or why, or what you should or should not backup in Office 365. Depending on the day (and, let’s be honest, depending on who I am working for) I may give you different answers.
The great thing about Office 365 is that it is a constantly updated service. For your subscription, your organization is constantly getting new features and functionality that can greatly improve the overall Office 365 experience. Of course, the downside of that is that IT pros working in Office 365 need to keep up to date on these changes..
So, the cloud, am I right? While it's always nice to get away from having to worry about failed hard drives, or backups, or patches, or a million other things, the real upside to using cloud services is that the good folks at Microsoft are able to put so much more into developing new features. Even for services like Exchange that seem mature, there are always new and unexpected ways for them to evolve as part of a huge infrastructure like Office 365 and Azure.
As we come to the end of 2018, or the beginning of 2019 depending on when you’re reading this, it seems like a good time to look at how Exchange Online has changed over the last year.
Having grown up with personal computers in the 70s and 80s my introduction to computer science was a simple two-line program.
Intune was born as Microsoft’s Cloud based Mobile Device Management platform. Since then, it has grown into a management platform for both mobile devices and P.C.s. Intune can now manage iPhone, Android, Windows Phone, and some versions of Windows. It’s clear that Microsoft intends to grow Intune into a complete cloud-based device management platform.