Office 365 exchange online

Office 365 Exchange Online and Redirected Mailboxes

So a client I am working with was in the process of migrating to Office 365 Exchange Online. They have approximately 350 "mailboxes", and the reason I put mailboxes in quotes is that actually about 150 of those mailboxes are not actual mailboxes, but email addresses for their primary email domain that get redirected to another actual mailbox. What this company does is some outsourcing of resources (people) to other companies. These other companies provide a mailbox for the resources so they can be integrated into the contracting company’s messaging environment. And to avoid the resources from checking two different mailboxes, my client simply setup an email alias for the users and then setup forwarding of that address to the outsourced company mailbox. Simple enough and I’m sure a situation that many other companies have implemented. This situation saves money, licenses and storage costs.

So back to the issue, my client sees the benefit of cloud computing and has an overall goal of removing all servers from their infrastructure. Enter Office 365 and Exchange online for phase one. While Exchange online offers many different licensing levels, including the K plans for Kiosk workers as a lesser month fee, this did not solve the outsourced resource problem, as they would still have to pay for a mailbox that would not be utilized. Being an expert of Exchange on-premises, I knew how I would fix this situation, mailUser. If you are not familiar with this it differs from a mailbox user for an on-premises Exchange implementation in that the mailUser is more of a super contact entry. A way for an Active Directory account to have an email address associated with the company’s primary email domain but any email sent to said email address is it actually redirect to another external email address. This is what my client was looking for. This was easy to do with a standard K or E plan user within Exchange Online, but it required a monthly fee for the Exchange online mailbox. This was counterproductive to the TCO for a move to the cloud.

First, no third party hosting company can claim to match the resources, investment, and level of expertise in these products as Microsoft.

Second, Microsoft’s products are in a constant state of development to improve their capabilities, reliability and security. The improvements made to these products will flow directly into their Office 365 and CRM Online offerings.

Often these improvements come first to the online offering before their traditional client-server applications. As an Office 365 customer you will automatically have access to these improvements included in your subscription as they are released. Updates to these products may be available to third party hosting providers as well but you may be charged for these upgrades or the provider may not elect to deploy them at all.

Click a question below to see more details.

  • Capture credentials
  • Create a new PSSession
  • Import the PSSession

Идентификатор пользователя должен выглядеть как адрес электронной почты, например [email protected] или [email protected]

{0} нет в системе

Another noted benefit of hosted Exchange is the addition of security tools. Microsoft Forefront Online Protection (FOPE) is deployed on the service provider’s end to curtail spam and viruses. This adds value over conventional Exchange Server deployments where security and malware tools must be purchased, installed and maintained separately.

Exchange Online enterprise pricing and control
There are two principal pricing schemes for Exchange Online. One plan carries a monthly fee of $5 per user, while the other plan costs $10 per user. Both plans provide the overall suite of features covered above, but the $10 plan provides advanced archiving, legal hold and compliance features, as well as unlimited archival storage and hosted voicemail. Additional pricing plans and options are available for organizations that want other Office 365 hosted capabilities, like SharePoint Online and Lync Online.

Программа лицензирования Microsoft Open License Program (OLP)

Recommended Email Clients:

и делаем то же самое:

Теперь необходимо сделать так, чтобы служба SMTP запускалась автоматически вместе с системой. В системе в Administrative Tools переходим к списку сервисов (Services) и находим сервис

В настройках сервиса запускаем сервис, если он еще не запущен (Start), а также указываем тип запуска (Startup type) - автоматически (


Настройка SMTP на IIS 6.0 завершена.

Figure 3: Improved reporting

  • New Migration Features With Exchange 2013, we can now create so called batch moves and migration endpoints. Migration endpoints are management objects, that describes the remote server as well as connections that can be associated with one or multiple batch moves. By using the new batch move architecture, we improve the Mailbox Replication Service (MRS) moves by enhancing the management capability. More specifically, we can move multiple mailboxes in large batches, we get email notifications with reporting during the moves, have automatic retry and prioritization of the moves, the primary and personal archive mailboxes can be moved together or separately and finally, we get periodic incremental syncs that update the migration changes. All of this of course occurs form within the Exchange Administrator Center (EAC) no matter if you’re dealing with on-premises moves or online moves.
  • Public Folders Just like for on-premises Exchange organizations, organizations that move to Exchange Online can take advantage of public folder functionality. Organizations with on-premises public folders can even migrate their on-premises public folder data to public folders in Exchange Online. Public folders in Exchange 2013 are based on mailboxes, so we now have the same high availability history for public folders as for “normal” mailboxes as both PF mailboxes also are stored in DAG protected mailbox databases.

Figure 4: Public Folders in Exchange Online

When archive is enabled, the default retention policy is applied to the mailbox. To apply a specific retention policy to a specific mailbox, use
Set-Mailbox -Identity [email protected] -RetentionPolicy policy-name

To set a specific retention policy for all mailboxes, use
Get-Mailbox | Set-mailbox -RetentionPolicy policy-name