The time you decide to move to MS Office 365, you should be prepared to deal with few certain surprises that come with it. In this article, we will discuss some of the noted factors that we personally encountered during this transition. Though the move to Office 365 will also prove fruitful, yet there can be some surprising factors that may put you in a puzzling situation. So, to avoid falling in that situation, read on all the points we cover in this article.
I. Migrating Is A Complex Process
If you use an Active Directory on-premise environment and you try to start migration process to Office 365, then be informed that the process will be complex for sure. The SP2 Exchange Server 2010 has a wizard which lessens the step counts from around 50 down – 6; however, the process is still very hectic and needs a strong planning from you.
II. You should begin with the spam filtering
Spam filtering can be a big issue to you during this process if you are not aware of it in advance. The process of fine-tuning spam filters can be time consuming for you, but it is an essential step because it will keep spam away from you. This suite utilizes MS Forefront Online Protection for Exchange which is a great spam filtering tool but requires ample of time to get configured.
III. Addresses of Outbound Emails May Change
While subscribing to MS Office 365, each user account uses an email address that comes as default and this email address lasts in onmicrosoft.com. Though it is quite possible for any user to use his or her own domain, by accepting email of your domain name is insufficient. Here, all the outbound messages will keep on using .onmicrosoft.com domain until some changes related to configuration are being made, which would not be intuitive.
IV. Chances for you to say bye to third-party utilities
A number of companies utilizes third party utilities for handling Exchange Server. So, if you too use any of these utilities and they should be installed right on the Exchange Server, then there will be difficult for you to use on Office 365. For using it, you should get on premise Exchange Server. Moreover, Microsoft is not giving permission to users to install software over Office 365 servers.
V. DNS Issues Can Be Arisen
Users who include domain to their Office 365 account would get a DNS entries list that has to be made for domain to work properly. Though a majority of these entries are quite straightforward, yet Microsoft Lync needs few SRV records to be made.
It should not be an issue for users who use DNS servers of Microsoft, yet it will surely be a problem for people using Non-Microsoft DNS Servers. For instance, if you use ISP to handle your DNS entries, then it would not be able to handle SRV records creation due to its utilization of Linux DNS server. Though it is not meant that these DNS entries would not be effective with Linux server, however, your DNS is being handled by someone else, then it will be troublesome to get required DNS records made.
VI. You would require to utilize multiple management tools
As in Office 365, Control Panel in Exchange is being used as a main management tool for Exchange Server. Similarly, accounts of various users are being made via proprietary interface instead of the Computers console and Active Directory users. Hence, you would require relying on multiple management tools in this process.
VII. Resetting permissions of file server
If you plan to move your entire domain of Active Directory, make sure to get a compelling plan for the data of file server before decommissioning the domain controllers. Here, you can either shift all your data to the NAS appliance; however it is not the only and perfect situation for all. Though just focus that if you think of moving everything except file servers, then somehow you would not be able to utilize your accounts in Active Directory to manage file access.
VIII. Get Ready To Be Filled With Email Messages & Phone Calls
One of the most surprising aspects of this process is that; you would be attacked with so many email messages and phone calls from Microsoft. Though it is quite helpful to users in many ways, yet if you are not needing any assistance, then it will be irritating for you.
IX. No Instant Connection With Mobile Devices Of Users
It is a certain issue of this process as during this transition, you have to keep your Windows phone connected to the mailbox for many days which ultimately leads you to stay disconnected with the mobile device. This issue mainly affects to those who starts the process from the beginning rather choosing to work through co-existed scenario as well as migrating each thing to the servers.
In fresh start of the transition, you would be required to make the PST file on the system and then, move each of your calendar entries, contacts and emails from Outlook to PST. After completing it, you can disjoin your system from on-premise domain. Now, switch Outlook to the new mailbox of Office 365. After that, copy all data in the PST file to the mailbox. It will not let your contacts, as well as other important content, disappear from your mobile device.
Certainly, it will not be an issue for companies working through a real process of migration. However small companies that decide to abandon on premise domain would certainly need to consider it.
X. A Control Loss May Happen
Lastly, migrating to Office 365 is clearly meant to give up your control at some extent. For instance, there will be no control on the process of patch management, administrative tasks, and software upgrades which you perhaps use to perform on premise.
So, by having a knowledge about these concerns and aspects to move to Office 365, you can make a confident move to this suite and can enhance your productivity positively.