When you create a new mailbox in Exchange Online, that mailbox comes with specific settings, features, and protocols enabled. As an Office 365 administrator, you have the ability to go back and modify these settings later if—for instance—you don't want users to have their default mailbox size limit set at 100 GB, or if you want a specific retention policy applied to that mailbox.
Back in September of last year, I wrote an article about Multi-Factor Authentication for Office 365. Since the cloud refuses to stand still, it looks like it’s time to update that post with some new information.
Topics: Office 365
About a year ago, we published an article on how to manage preservation policies in the new Security and Compliance Center in Office 365 via PowerShell. Over the course of the last year, a great number of new features have been added to the SCC, which is now the central place for data governance in Office 365. With some minor exceptions, all of the functionalities exposed in the SCC are very sensitive and controlling access to them is vital. In this article, we will cover some methods to restrict access to the SCC features. By using PowerShell, of course!
For most the last 25 years or so, most people with “office” jobs have relied on email as their primary communications tool at work. During that time, Microsoft has added many ways for groups of people to collaborate within their email clients. Distribution lists, public folders, shared mailboxes, resource mailboxes, site mailboxes, and now Groups each give end-users different functionalities. How does an organization decide which of these options to use? When are shared mailboxes the best choice?
When it comes to sizing a typical on-premises Exchange Server deployment, Microsoft has really gone out of their way to provide all the information you need. Along with the Mailbox Role Requirements Calculator, I believe Microsoft’s guidance to be one of the most complete in the industry—–leaving little to the imagination and with clear guidance on what you should and should not do.
This post is about a recent migration of legacy public folders hosted on Exchange Server 2007 to modern public folders hosted on Exchange Server 2013.
I have spent most of the last six years of my professional life configuring Exchange hybrid deployments for organizations looking to move their email into Office 365. Speaking from the perspective of someone who has set it up repeatedly, Exchange hybrid is straight forward. You take your on-premises Exchange organization’s and run the Hybrid Connectivity Wizard (HCW) to connect to Office 365. I suppose there is more to it than that, but this blog post is not the place to go into those details.
In this blog post, I want to talk about the hybrid options for Skype for Business. Hybrid for Skype for Business is a much newer offering from Microsoft, and in my opinion (as someone who has not set it up for hundreds of customers) much more complex.
Since the dawn of email, organizations have struggled with the way that users reply to emails. Confusion (or worse) occurs when emails include groups, CC, BCC, internal, and external recipients. Choosing to use "Reply All" may release confidential information to the wrong people or cause mail storms between senders and recipients – sometimes bringing email servers to their knees.
There are a few words Microsoft likes to use in several different situations. “Federated” is a great example of this. Federated can mean several different things in the Microsoft world, and it can sometimes be hard to tell what sort of “federation” you’re talking about.
“Supported” is another word Microsoft uses to mean different things in different situations, and what I’d like to talk about in this blog post.
In the world of hybrid headaches, directory synchronization is the root of all evil. While there's nothing wrong with using directory synchronization (I'm a big fan), most of the issues and questions I encounter when dealing with hybrid issues are a direct result of not understanding directory synchronization and how the process works.
Topics: Azure active directory