Office 365 migration project
7
Office 365 migration project Stone and Christy P.A. This Project consisted of migrating my clients from their current email host to hosted Exchange and Office 365. The office consisted of nine user accounts. The Consumer Fraud Protection Department mandated that the exchange of personal and sensitive information required that an email encryption be implemented. My clients current email hosting solution could not be provisioned to accommodate due to the inability to specify a smarthost. This provided us with an opportunity to transition to hosted Exchange via Office 365. To accomplish this, first I had to create my clients user accounts through the Office Portal.
Transcript of Office 365 migration project
Office 365 migration project
Stone and Christy P.A.This Project consisted of migrating my clients from their current email host to hosted Exchange and Office 365. The office consisted of nine user accounts.
The Consumer Fraud Protection Department mandated that the exchange of personal and sensitive information required that an email encryption be implemented.
My clients current email hosting solution could not be provisioned to accommodate due to the inability to specify a smarthost. This provided us with an opportunity to transition to hosted Exchange via Office 365.
To accomplish this, first I had to create my clients user accounts through the Office Portal.
Once created, I then had to update the DNS records that via their DNS host. This included the MX, CNAME, TXT and SRV records.
After working through these issues with the DNS hosting service below:
I was then able to successfully run the records check and move on to the next phase.
Prior to getting the DNS records modified, the portal access required the username @stoneandchristy.onmicrosoft.com . After the records update, that allowed the users to login through the office portal using the username @stoneandchristy.com .
2
The next phase of my project consisted of exporting the existing user .PST files. After exporting them I then setup their new hosted Exchange account in their 2013 Outlook client.
Once the new account was configured, I then imported the .PST file into the new account, coping subfolders, contacts and calendars.
After the synchronization of those completed, the users had mobile devices to be configured with the new account settings. Some used the native app while others preferred the Outlook app via the App Store.
After the mobile devices where configured, I contacted our Echoworx reseller to begin the process for setting up the email encryption service.
3
The Echoworx encryption service allowed my clients email to be routed through the hosted Echoworx servers and scanned for any personal information, i.e. Social Security numbers, birthdates, etcetera. Upon encryption, the message would be sent to the receiver and depending on whether on not the receivers email server has a valid TLS (Transport Security Layer) certificate the message would be sent through without the receiver knowing the message had been encrypted at all. For the ten to fifteen percent that has email servers without a valid TLS certificate, the message would be retained on the Echoworx server and a message would be sent to the recipient with a hyperlink to view the message.
The routing process consisted of updating the SPF record for the the DNS zone file and set an outbound connector to route by smarthost.
For the SPF record modification, I sent the DNS hosting company the following:
v=spf1 include:nets1.spf.messagelabs.com include:nets2.spf.messagelabs.com -all I then had to modify the outbound connector through the Office 365 ECP portal:
4
After specifying the outbound connector:
cluster8out.us.messagelabs.com
My connector setup was complete.
Mail started routing instantly and there where no interruptions in service.
5
6
