When you are navigating or making changes in the Exchange Online portal, PowerShell is being executed in the background. Using the Command Logger, you can see exactly what that these background PowerShell command looks like! This tool is a great way to learn PowerShell and can give you a head start in your own scripting.
Exchange 2010 offered ways to view the Exchange shell to see what was happening in the background when changes were made. This feature disappeared in Exchange 2013, but reappeared in Exchange 2013 SP1. The Command Logger is now also present in both Exchange Online and Exchange Online Protection.
This is a new series of articles for this blog that were inspired by Mark Russinovich’s Case of the Unexplained series. Each article will tell the story of an Exchange Online scenario that initially made no sense. I’ll then progress through the troubleshooting steps and eventually end up with the root cause. I have a couple of hopes here.
Welcome to the second episode in our Support Hot Topics for Exchange Online Protection series. I’m joined in this episode by my co-worker, Jason, and we discuss Exchange Online Protection strategies, including two transport rules, that can help reduce the threat of zero-day malware.
Rather than start this article with an appetizer, I’m going to switch things up and dive right into the meat and potatoes. Very soon, if not already, you will see two new entries to your Spam Filter in Exchange Online Protection, Allow Lists & Block Lists. As suggested by the name, this is a new way to manage allow and block lists within EOP. These new entries certainly don’t replace using Transport Rules to manage allow and block lists, but instead offer a simpler alternative.
Obtaining reports in the past was a manual task which had to be performed every time you wanted to pull data. Many of you (most of you?) have asked us to allow for automated reporting in Office 365. Did you catch how I used the words, “in the past,” in the first sentence?
Well, I’m happy to say that automated reporting in Office 365 has arrived and is now available in your tenant. Reports can be scheduled for delivery either on a weekly or monthly basis.
I have recently seen a lot of zero-day malware attacks and interestingly, these attacks aren’t even trying to be covert. In these cases, the malware is attached to an email in the form of an executable file and the recipient is asked to run the attachment. Being in the technology works, people like you and me don’t fall for this, but a lot of less technical users do and execute the attachment.
In this article we’ll explore proactive actions that can help prevent zero-day malware from landing in in your employee’s mailboxes.
Welcome to the first episode in a new series called Support Hot Topics for Exchange Online Protection. This series will consist of short videos which will each cover a trending topic relating to Exchange Online Protection. These videos are designed to give you a quick blast of information on a specific topic when you need to learn fast.
There was a lot of Exchange Online / EOP and Office 365 news in April and I wanted to pull them all together in one place, here! The stories range from product updates all the way to announcing new services. I have placed the articles that directly relate to Exchange Online towards the top of the list.
Need to get a list of all messages that triggered a particular transport rule, or do you want to see all rules that have been triggered by a particular sender? This information can be easily found using the Get-MailDetailTransportRuleReport cmdlet. Looking past the name being much too long, this cmdlet can provide very insightful information about your transport rules.
What better way to show off this cmdlet than with examples. Here we go.
In case you missed it, we have something new coming to Exchange Online. Last week on Office Mechanics, Shobhit Sahay, technical product manager for the Office 365 team, introduced a new service coming to Exchange Online Protection (EOP), Advanced Threat Protection.
Advance Threat Protection (ATP) adds another layer of security and protection on top of EOP, targeting specific types of advanced threats.
Update (April 7, 2015): More content and examples have been added to this article since the original posting.
PowerShell can be used to quickly search for rules matching specific criteria. This can be incredibly valuable for a tenant that contains a lot of rules. While possible to search for transport rules in the EOP portal, PowerShell offers a more comprehensive (and cooler) way to accomplish this. There are also some rule properties that can only be searched for with PowerShell.
I typically avoid the Internet like the plague on April fools day, but this morning I peaked and came across MS-DOS Mobile and just couldn't help but share. This April fools day app brings DOS directly to your Windows phone! Let's take a trip down memory lane and see what we can do with this app.
This is a quick public service announcement before the weekend starts. Exchange Online Protection has been allocated a new IP range. Starting in 30 days, EOP will add 188.8.131.52/16 to the IP pool that is used to deliver mail that passes through custom connectors (ex. EOP outbound connector which routes inbound mail to your on-premises environment).
I recently worked on a very interesting case that I wanted to share. This organization had set EOP to deliver all spam messages to end users junk mail folder.
This worked great for most users, but a small number experienced EOP delivering spam messages directly to their inbox, as if they weren’t being scanned at all. Very peculiar indeed. Let’s go through the troubleshooting process to figure out what’s happening here.
When troubleshooting mail flow it is often important to determine where a message is handed off from a partner to your Office 365 tenant, or from your Office 365 tenant to a partner. This is easy to see in a message header, just look for the receiving host with the domain mail.protection.outlook.com, as this will indicate Office 365 servers.
But what if your partner is also an Office 365 tenant, then how can we tell when a message left their tenant and entered yours, or vice versa? If troubleshooting a mail delay, this is crucial information as this will let us know which tenant is experiencing the delay.
I have recently seen a large number of cases where an organization’s own domain was spoofed to send that company phishing messages. This isn’t all that uncommon, but what was concerning for me was the method used in these cases to do the spoofing. In these cases, only the 5322.From header was spoofed, which cannot be detected by an SPF check.
I've recently seen an increase in cases that involve incorrectly published SPF records that have resulted in sent mail failing the SPF check. Ensuring your SPF record is up to date is great proactive work that can help prevent issues with SPF checks. In this article I'm going to go over how to properly set your SPF record if you are using Exchange Online or Exchange Online Protection.
There is also a common mistake that organizations sometimes make in their SPF record when they are smart hosting mail out through EOP which I will also highlight.