M365 - Exchange Online Center

With the increasing number of services and features in Office 365, keeping up with all the changes can be a challenge. Keeping an eye on all the different ways a user can do harm, either willingly or by mistake, is not an easy task, either. While the on-premises versions of Exchange and SharePoint do offer some form of auditing, many organizations were surprised to find out that things were quite different after their move to the cloud.

Office 365 Groups (that’s Groups with a capital “G”) are a newish feature of Office 365 that allow for collaboration across several different cloud applications. Office 365 Groups are the cloud only evolution of Site mailboxes, a technology introduced with Exchange and SharePoint 2013 that gave users a single place to access data stored on both Exchange and SharePoint.

Security and compliance are big concerns for corporate customers moving to Office 365. As such, Microsoft is putting a lot of resources into ensuring that customers have the tools they need to ensure their data is kept securely and compliantly.

Phishing attacks are ever more common for all email users. These attacks can target organizations or individual users.. Most phishing emails are easy to spot, but even the savviest of us can be caught off guard, and when a user ends up clicking on a dangerous link in an email message, then suddenly a bunch of servers start getting encrypted and your whole weekend is ruined. In an attempt to help reduce this problem, Microsoft is currently rolling out email safety tips as part of Exchange Online Protection in Office 365.

Forwarding might not be one of the most used features when it comes to email, but it’s certainly common enough. I know I’ve had to deal with it in a lot of related cases back in my support days. While most of the issues you might run into are easy enough to solve, there are so many different ways to configure forwarding that oftentimes people get confused. In this article we will review (some of) the forwarding-related options and introduce you to a recent change in handling forwarding in Office 365/Exchange Online.

Office 365 is a collection of online services that allow organizations to use Exchange, Skype for Business, and SharePoint in the cloud. In the nearly five years that Office 365 has been available most of the organizations using Office 365 have used it just like that; for Exchange or Skype for Business or SharePoint in the cloud. Some organizations are using more than one of those services, but for the most part they are still using them separately.

Moving to Office 365 means a pretty big adjustment. Administrators who were used to doing things one way are going to have to make adjustments as their organizations migrate their infrastructure into Office 365. One of the areas where new Office 365 administrators often feel most in the dark about is changes in their environment.

Only a statistician loves statistics and I am no statistician. However, it’s interesting to try to track the growth in Office 365 numbers based on the snippets of information released by Microsoft in their financial results and elsewhere.

Spam is the bane of all messaging administrators, as well as a major pain for all email users. Using email means a consistent battle against spam, malware, and unwanted nonsense flooding your inbox. There are a number of different tools and tactics we, as administrators, can use to reduce the impact of these attacks and recently Microsoft has added another one to the toolboxes of Office 365 customers. In this blog post I'm going to explain what DKIM is, and how you can use it to help make the world a safer place for legitimate email messages.

A little over two years ago, I wrote about an issue I encountered with a KEMP load balancer and how Microsoft performs hybrid mailbox moves. More specifically, the issue evolved around a seemingly different interpretation between KEMP and Microsoft regarding the implementation of the expect 100-continue header. As I noted then, the workaround was to configure the KEMP load balancer to ignore the 100-Continue rules as described in RFC 2616.