Exchange online preservation policy summary
I love the cloud, yet sometimes it is not easy to keep up with the ever-changing topology. With the quickness and agility of O365 and the amazing new tools and processes, it’s an exciting time but one you must keep up with on all the changes. This article is written to help clear up some
EXO Manageability Survey
The Exchange online engineering team would like your feedback on the user interface within O365: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR49eFzv9DqVGqZMZy6mK_45UQVUzS1JGSU9YSU9OMTQxT1VNT0U2Wk5JSy4u
Exchange Hybrid Duplicate Mailboxes
Some customers have seen where they can end up with a duplicate mailbox within their hybrid environment. This can cause problems when a user, either on premises or in the cloud, has two mailboxes, one on premises and another one in Exchange Online (EXO). The good news is, there is now a work around. A
To stay hybrid or not to stay hybrid…
That is the question and the answer is: It depends, but most like yes. You need to ensure that you have no on premises dependencies. I’ve had this conversation with more than 5 customers in the past 2 weeks, so thought I’d present the discussion of the options and thought process around removing the Exchange servers from
Dynamic Distribution Groups, Distribution Groups, and Exchange hybrid
I recently ran into a customer that uses: Distribution Groups (DG), leverage Dynamic Distribution Groups (DDG), have started their move to Exchange Online (EXO), while nesting several DDG's inside of DG's. There are known work arounds that you should implement if you are in an Exchange hybrid configuration working with DDG's. Since each realm bifurcates the
cmdlet: Remove-InboxRule
Q: Is there a way to remove an Inbox rule for a mailbox? A: Yes. You can use the Remove-InboxRule cmdlet to remove an Inbox rule from a mailbox. Inbox rules process messages in an Inbox based on conditions specified and take actions. Removing an Inbox Rule can assist in troubleshooting end user’s mailboxes. Remove-InboxRule -Mailbox
cmdlet: Enable-InboxRule
Q: Is there a way to enable an Inbox rule for a mailbox? A: Yes. You can use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules process messages in an Inbox based on conditions specified and take actions. The enable/disable InboxRule cmdelts, assist in troubleshooting end user’s mailboxes. Enable-InboxRule "Move To Junk Mail" -Mailbox
cmdlet: Disable-InboxRule
Q: Is there a way to disable an Inbox rule for a mailbox? A: Yes. You can use the Disable-InboxRule cmdlet to enable an Inbox rule. Inbox rules process messages in an Inbox based on conditions specified and take actions. The enable/disable InboxRule cmdelts, assist in troubleshooting end user’s mailboxes. Disable-InboxRule -Identity "MoveAnnouncements" -Mailbox "Joe@Contoso.com" This example
cmdlet: Set-InboxRule
Q: Is there a way to change or set an Inbox rule on an end user’s mailbox? A: Yes. The Set-InboxRule cmdlet allows you to modify, enable, disable, or even create a rule with this cmdlet. Other than the Get-InboxRule cmdlet, one could argue, the Set-InboxRule is the only other cmdlet you need to know
Support for Exchange 2013+ File Share Witness server in Azure
The Exchange product group has announced support for putting your Exchange 2013 File Share Witness (FSW) server in Azure. http://blogs.technet.com/b/exchange/archive/2015/01/09/using-an-azure-vm-as-a-dag-witness-server.aspx I think this is the next big advancement with the marriage of Exchange and the cloud. Yes you can migrate to O365 and leverage all of the integration with: Exchange, Lync, SharePoint, OneDrive, Teams, and/or StaffHub. While some organizations do have the