If you find yourself using the Office 365 (Exchange Online) e-mail quarantine often then you probably know how frustrating and slow it can be to quickly find and release quarantined items. Often times you’ll find yourself waiting for a few minutes only to realise it’s not doing anything. Then you have to refresh the page and re-enter your search criteria. The fact you can’t even wildcard searches is also unforgivable (it’s 2016 Microsoft, why can we not wildcard search the subject and sender fields?!)
This annoyance coupled with my eagerness to play with PowerShell led me to develop a quick and dirty quarantine tool or viewer if you like. The tool is quite basic but it will let you do the following:
- Wildcard search the subject and sender fields
- Configure the number of results to return
- Release a message based on message ID
If you want to have a play with the tool, it’s on my GitHub along with the source code if you feel like suggesting some improvements.
In this article I will show you how to create Exchange Online mailboxes in a hybrid environment such that the maiboxes also show up on the on-premises Exchange server management console.
The most logical way of creating an Exchange Online mailbox (you’d think) is to let AD users DirSync across to 365, assign them licenses and be done with it. However doing it this way doesn’t create a link between Exchange Online and your On-Premises Exchange server which means you can’t do things like manage the user’s mailbox from EMC or migrate the mailbox between on-premises and Exchange Online.
Continue reading Creating Office 365 Mailboxes in a Hybrid Setup
Licensing Office 365 users manually can be a tedious task; especially if you are tasked with licensing hundreds or even thousands (think educational institutes that need to license user’s every semester or academic year).
I created a fairly basic script that will take a .CSV input and license your users according to your Office 365 environment and the licenses you have available.
Continue reading Bulk Licensing Office 365 Users with PowerShell
The short answer is, yes.
The long answer is that it will require a lot of work on your behalf.
The new Office 365 midsize business plan is very similar to the E3 plan (bar some advanced features which most users probably won’t need anyway) without the more expensive price tag attached to it; for UK users this is £9.80 per user per month as compared to £15 per user per month… if you have a lot of users the cost adds up very quickly.
Continue reading Can you Move from an Office 365 Enterprise Plan to a Midsize Business Plan?
The default policy for Office 365 user accounts is to automatically expire their passwords after 90 days.
Some of our users experienced this today and the most annoying thing about it was that they were not warned beforehand about it. They were simply locked out their account until they changed it there and then; unlike the Windows OS counterpart which gives you a comfortable 15 day warning before forcing you to change your password.
Anyway, this article will tell you how to set the password expiry from 90 days to never.
Office 365 already enforces a strong password policy BUT I do not recommend you change this setting if your users often use public terminals or are prone to writing their passwords on sticky notes and keeping them under their keyboards 🙂
Continue reading Setting Office 365 User Passwords to Never Expire
So an employee has left the company and you now need to archive the mailbox due to legal and/or company policies.
This article will give you a quick overview on how you can achieve this goal on an Office 365 mailbox while maintaining the integrity and security of your organisation’s 365 account.
Although not necessary, I recommend (as a pre-requisite) disabling account ‘sign-in’ capabilities and resetting the user account password.
This will prevent the user from logging in to the account and messing around with it whilst you are attempting to archive their mailbox.
Continue reading Archiving a User’s Mailbox on Office 365
For one reason or another, you may want to disable remote PowerShell access for all the users in your organisation.
The main reason for doing so would be to prevent ‘reconnaissance’ type attacks whereby a user will try to gain information about your network/organisation/topology/system etc by simply running (in this case) PowerShell queries against your organisation.
Continue reading Disable Remote PowerShell for Office365 Users