Synchronizing users’ identities between local and cloud directories is a great way to let users access different resources on both on-premises and cloud environments with just a single set of credentials. To achieve that, you need to use Azure AD Connect to integrate your on-premises Active Directory with Azure AD.
In this article, you will find some guidance on how to use Azure AD Connect to sync on-premises Active Directory with Azure Active Directory.
Azure AD Connect
Azure AD Connect is a tool that connects functionalities of its two predecessors – Windows Azure Active Directory Sync, commonly referred to as DirSync, and Azure AD Sync (AAD Sync). Azure AD Connect will be now the only directory synchronization tool supported by Microsoft as DirSync and AAD Sync are deprecated and supported only until April 13, 2017.
Continue reading ‘How to sync on-premises Active Directory to Azure Active Directory with Azure AD Connect?’
There are many situations in which permissions to another user’s mailbox should be granted on Exchange Server. Sometimes it is for monitoring purposes, sometimes in order to send emails on behalf of someone else. Full access permissions give the highest level of access to a mailbox, and are necessary, for example, during a migration process. If you want to learn how to set full access permissions on Exchange 2007, Exchange 2010, or Exchange 2013, you have come to the right place.
If you want to learn more about how to perform an Exchange server to Office 365 migration using native means, check this article.
Continue reading ‘How to grant full access permissions to all users’ mailboxes using PowerShell’
With the popularity of Office 365 constantly growing, there are few administrators who did not at least consider moving from their on-premises Exchange server to Microsoft’s Cloud. Especially now, when the extended support for Exchange 2007 is inevitably going to end in 2017, Exchange to Office 365 migration is likely to be a common topic. As moving mailboxes is never an easy task, there are quite a few consequences which have to be taken into consideration before jumping into the new environment.
First of all, you have to remember that Office 365 has some storage limits which have to be taken into consideration. All mailboxes types, including public folders and shared mailboxes, can store up to 50 GB of data. If in your organizations there are public folders or mailboxes which exceed this size, you might want to archive some content.
Secondly, moving to Office 365 requires the source and target environment to be thoroughly prepared before the migration proper can be started.
There is a number of native options available for those who wish to move from their on-premises Exchange to the Online version:
- Cutover Migration
- Staged Migration
- Hybrid Deployment*
- Office 365 Import Service
*Does not apply to Exchange 2007 and older versions
Continue reading ‘Available scenarios of Exchange to Office 365 Migration’
Autodiscover is an Exchange service which, after successful configuration, helps admins and users save tons of time. Thanks to Autodiscover, Outlook clients are automatically configured, after as little as entering user’s e-mail address and password upon first login. Its job does not end there, it is required to ensure Outlook-Exchange connectivity later on. Therefore, it is crucial to diagnose problems with the service as quickly as they occur. In this guide I will show 2 quick and easy ways to do that.
Checking Autodiscover connection for a user is as simple as using a single cmdlet:Test-OutlookWebServices for the user you want to diagnose, i.e.
Test-OutlookWebServices -identity: email@example.com –MailboxCredential (Get-Credential)
Continue reading ‘How to quickly verify if Autodiscover is working’
Applies to: Exchange 2016, Exchange 2013, Exchange 2010, Exchange Online
In this article I am going to show you how to use the Search-Mailbox PowerShell cmdlet together with the -DeleteContent switch to delete email (and other item types) from multiple mailboxes on Microsoft Exchange 2016, 2013 and 2010.
I will also talk about using the -SearchQuery parameter to manage items scopes and target specific content.
Continue reading ‘How to delete email from mailboxes on Exchange 2016 / 2013 / 2010 / Online’
Applies to: Exchange 2016, Exchange 2013, Exchange Online. Some information may also apply to Exchange 2010.
The -SearchQuery parameter available in the Search-Mailbox command allows you to filter items stored in Exchange mailboxes using a set of item attributes and properties.
Microsoft doesn’t offer documentation regarding attributes that can be used with the -SearchQuery parameter, so I decided to create my own list.
Continue reading ‘Search-Mailbox (Exchange 2013, 2016, Online): Attributes’
(First published Jan 16, 2014)
Server sided email disclaimers belong to one of the most desired features among server administrators. Although the need for this functionality has been consistently increasing throughout the past years, Microsoft still hasn’t disclosed a robust built-in Exchange Server mechanism that would fully satisfy the needs of IT professionals.
Let’s take a look at the list of things that all successive versions of Exchange Server can do natively in this matter, and compare it with vast capabilities of CodeTwo Exchange Rules Pro, a third party email management tool for Exchange 2007, 2010, 2013 and 2016.
Continue reading ‘Email disclaimers on Microsoft Exchange Server’s side’
Although mailbox data in Office 365 is fairly secure, it does not mean it is protected from deleting. Users, either by accident or on purpose, can remove their emails from Inbox and Deleted Items folder or even purge them from Recoverable Items folder. What’s more, retention policies can exist, which live only for deleting certain emails from users’ mailboxes. Of course, Office 365 gives you a plan B, just in case you would need to recover deleted emails. This plan, however, only works when the time gap between deletion and recovery is not too big.
Continue reading ‘How to recover deleted emails in Office 365?’
CodeTwo Exchange Rules Pro is the ultimate powerhouse tool in the hands of an Exchange administrator. On a very general level it lets you create rules that redefine email flow and modify email content in your organization.
A common example of the program’s application is extended control over server-level email signatures. There are, however, numerous other ways it can be utilized. In this article I will talk about one of them: archiving attachments from outgoing email in SharePoint server libraries. A feature that can prove very useful when it comes to monitoring what your users send to external recipients.
For the purpose of this presentation, I have prepared the following server environment:
Domain controller: DC.example.com
Exchange Server 2013 CU13 (EX2013.example.com)
SharePoint Server 2013 SP1 (SP2013.example.com)
All servers operated by Windows Server 2012 R2
I deployed a domain controller running Exchange 2013 in the internet.com domain, so that I can simulate email going out into the Internet.
Continue reading ‘How to save outgoing email attachments in SharePoint library?’