If you’re reading this, the odds are good that at some point in your life you’ve seen a Disney movie of some sort. Many of these movies feature some sort of magic device, such as a magic mirror or a pool of water, that let the characters see things they otherwise couldn’t. Think of the wicked queen in Snow White chanting “Mirror, mirror, on the wall…” and you’ll get the idea. Microsoft offers something very similar in the form of the service health dashboard (SHD) in Office 365.
Topics: Office 365
In Part 1 of this series, we covered the basics of the Collaboration choices available in Office 365. Before you say it, I know I didn’t include SharePoint Online in Part 1, and I won’t cover it in Part 2 either. Although Microsoft lists it as a collaboration tool, I don’t really agree. I see SharePoint Online as a method or landscape to store data that has rich features for document management, such as versioning, views, check in/out, etc. For me, collaboration requires more than document management. I know many of you reading this will disagree with me, and that is okay. If it works for you, then use it!
More than likely, you are an email admin, with deep experience in Exchange. Maybe you have recently migrated to Exchange Online, and are thinking “Hey, I know how to collaborate in Exchange, so what’s the big fuss about.” Let review where we have been and where Office 365 is headed.
Reddit, a popular online discussion site, has a running joke: people are often asked whether they would rather fight a horse-sized duck or 100 duck-sized horses. This question has surprising relevance to Office 365, because while Microsoft customers often worry about the threat of a widespread large outage (the horse-sized duck), they’re actually getting beat up by a larger number of smaller, less damaging but still annoying outages (the herd of duck-sized horses). There are a couple of deeper issues here that warrant a closer look to understand what the real risk is, and what you can do about it.
A few months back, we did a short two-article introduction to Advanced Security Management (ASM), a stripped-down version of the Cloud App Security suite, tailored to the needs of Office 365 administrators. As it is now a year since the product was officially launched, I thought it’s a good idea to take it for another spin and compare it to its big brother, in terms of Office 365 related functionalities that is.
Traditionally, restricting where and from which device users could access their Mailbox in Office 365 required substantial configuration within Active Directory Federation Services (ADFS), or more recently, relied heavily on registration of compatible devices within Intune.
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?