Editor's Note: Originally posted by Paul Cunningham (Microsoft MVP) on his blog, Practical365, this review is extremely comprehensive and discusses the many ways Mailscape 365 can be used in Office 365 cloud and hybrid environments.
Since the dawn of time (if the dawn of time was in 2011), assigning licenses in Office 365 has been a pain. It has never been complicated, but it has also never been a pleasant experience.
In my previous article in this series, we discussed Exchange “Alternative Architecture” options for medium-to-large businesses. We specifically covered common storage design options and which were ideal to design the best solution for a customer that has decided to remain on-premises and chosen to not follow the Preferred Architecture. To reiterate, I’m a big fan of Office 365 and the Preferred Architecture but I understand many customers will not follow either of these two routes. Therefore, if they deviate from either of these options they should at least follow the recommended guidance that can increase the uptime and better the performance of their solution.
Office 365 is Microsoft's premier cloud service, and the clear leader in the "back office" server cloud offering market. If your organization has not moved to Office 365 yet, it's a safe bet that someone within your organization will be making a strong push to get you there soon.
One common request when performing an eDiscovery or using the Search-Mailbox cmdlet has long been the option to search a specific folder only. Possible scenarios for such requests are to delete/purge items from a (sub)folder or copy them to a different mailbox, etc. Similarly, an “exclude folder” functionality can sometimes be useful. With the latest additions to the service, we are now able to scope eDiscovery/Content searches to specific mailbox, SharePoint or OneDrive for Business folders!
In my first article in this series, I discussed Alternative Architecture options for Small Businesses who choose to stay on-premises. My intent was to ensure that if a business chose to remain on-premises but did not wish to implement Microsoft’s Preferred Architecture for Exchange, they would at least deploy in a way that will reduce complexity and increase uptime of the solution. While the first article focused on options for small businesses, this article will begin to discuss common deployment options seen in medium to large environments. We’ll focus on popular storage technologies found in this space; RAID and advanced storage solutions (SAN/NAS/Hyper converged). As the type of architecture found in this space is so varied, we’ll focus more on sound design principles and best practices.
In the past and even today, we are used to “share” documents and files by sending copies as email attachments. This behavior is often the source of end user frustration when message size limitations are enforced. Especially when size limitations for internal and external recipients are different. Users do not understand why they cannot send any file to any recipient of their choice.
For hybrid customers, Azure Active Directory Connect is one of the most important tools you need to keep Azure AD up-to-date. Besides directory synchronization, it provides means for authentication to Office 365 resources using password hash sync, pass-through authentication, or AD FS.
Topics: Azure AD Connect
What is "Microsoft 365"?
First, it's a terrible name. I get confused as I look back though what I have written in this blog post, so I don’t think it’ll be a surprise to find that this name confuses customers.
In recent years, the Exchange Product Team began recommending the "Preferred Architecture" for Exchange On-Premises. Inspired by what Microsoft found successful in their Office 365 datacenters, the Preferred Architecture (PA) was designed with several business requirements in mind: