Last month, Andy Higgins of IMCollaboration and I presented Domino and Office 365 Integration at Collabsphere. During this session, we discussed concepts and technical components of getting these two technologies to play nice.
When considering any coexistence project, it is important to first define what is needed for your environment. This may include directory synchronization to provide single sign on and group membership for messaging and access lists. Most common is the need for mail flow between the two environments. Additionally, calendar scheduling and instant messaging between the two may be necessary. The length of the coexistence and budget will contribute to these decisions, as some may be achieved with native technology and others require a third party utility.
Email, Calendar, and Instant Messaging Integration
Email integration between Domino and Office 365 involves using SMTP. Over the years, Lotus/IBM/HCL have greatly improved the Domino SMTP engine and have tweaked Domino to handle Microsoft specifics, such as Outlook Rich Text and winmail.dat files. Hence, no additional tools are needed to have email move between the two environments. When moving from Domino to Office 365 for email, the Domino server will become a sub domain. Further, if Domino will only receive incoming email from Office 365, you may tighten the security of the Domino server by only allowing connections from this domain. If coexistence continues after the email migration due to Domino applications, ensure doclinks are converted to URLs by setting in the configuration document MIME – Conversion Options – Outbound – Message Content from Notes to Plain Text and HTML.
For an environment where Office 365 and Domino messaging will both be in use it becomes important to provide a method for users to share free/busy time for scheduling. Neither platform offers a native solution for this; hence, a third party tool is needed. The IntraVision company was a vendor at Collabsphere, where they show cased their OnTime product. OnTime easily allows your Notes and Outlook users to interact when scheduling meetings.
Further, instant messaging needs include the need to migrate buddy lists, synchronize buddy lists and collaboration between the two. Microsoft is in the process of deprecating Skype for Business in favor of Teams. Sametime 11 moves back to a Domino centric offering and provides the use of external meeting services. Keep these in mind as you look forward to planning instant messaging migrations and coexistence.
Finally, directory synchronization between Active Directory and Domino is getting easier with Domino 11. In Domino 11 the Domino Directory will be a “down stream” directory that receives changes from AD. New users in AD will become new person documents in Domino. Additionally, a right mouse menu option in the People view of the Administrator client will allow you to easily create Notes IDs for these new users. AD groups will synchronize based on the defined group types, where AD Distribution groups update Domino Mail Only groups and AD Security groups update Domino ACL Only groups. If directory coexistence is in your future, I recommend you upgrade at least your Domino Directory administration server to Domino 11 and use this new feature. Synchronization of other directory items, i.e. Domino mail in databases, requires a third party tool. Integration. Integration
Single sign on authentication can be achieved by using LDAP or SAML. However, keep in mind SAML is not quite completely supported by Domino. Please visit the following page and vote for full SAML support in Domino: https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-395
If you have questions about Domino and Office 365 coexistence specific to your environment, feel free to ask.
And, I cannot leave you without a friendly reminder about the Domino 11 launch on December 4th viewing party hosted by RPR Wyatt in Phoenix, AZ. Hope to see you there!