<p> <logo customer> <customer name> <Project name> <Document name> <Document name></p><p>TABLE OF CONTENT</p><p>Addressee Date <date> 2/10 <Document name></p><p>DOCUMENT HISTORY Document Version Version Revision History Date of this revision: Date of next revision: Revision Date Version Summary of Changes Changes marked 29-07-2016 0.1 Templae O365 Documentation Ivo Maas</p><p>Approvals Name Signature Title Date of Issue Version</p><p>Distribution This document has been distributed to: Name Title Date of Issue Version</p><p>Addressee Date <date> 3/10 <Document name></p><p>GLOSSARY</p><p>Images & Icons The following Icons are used throughout this document to elaborate on decisions or noteworhty factors.</p><p>Glossary of terms, abbreviations and definitions Term, abbreviation, Explination definition</p><p>Addressee Date <date> 4/10 <Document name></p><p>1. INTRODUCTION <project/document background></p><p>Addressee Date <date> 5/10 <Document name></p><p>2. CURRENT ENVIRONMENT 2.1. Current mail/UM Solution <What mail system/um system is in use?> <versions> <size of the environment in servers> <size of the environment in users/mailboxes> <size of the environment in amount of data> <size of the environment in amount of mails sent/received> <mail profiles of users defined (low,medium,high)> <domains> 2.2. Mailflow <vision drawings/depictment & elaboration on the current mail flow> 2.3. Identities <AD> <ADFS> <OKTA> <etc.> 2.4. Authentication <visio drawsings/depictment & elaboration on the current authentication flow for mail/um> 2.5. Licensing & Features <features supported by current system (mail, voice, Social media, calendar, public folders, contacts etc.)> <describe the licenses used and what features they provide. In addition you can use the mail profiles of users defined in 2.1 to elaborate.> 2.6. Security <measures taken in regards to security (anti-virus, spam, firewalls etc)> <these measures should also be depicted in the mailflow/authentication in points 2.2 and 2.3> 2.7. Support <The current support organization></p><p>Addressee Date <date> 6/10 <Document name></p><p>2.8. Clients <Clients used to connect to the mail/um environment and how they interact with the system> 2.9. (Mobile) Devices <Devices used to connect to the environment & their numers & uses). Think of ipads, android phones, laptops etc.> 2.10. Usability & integrations <Services that rely on the current system (smtp relay example)> <Integration with other services> <Ease of connection> 2.11. User requirements <access, device support, mail handeling, rule configuration> 2.12. Reliability <uptime guaranties> <SLA> <mailbox en message protection> <backup> <DR> <failover> 2.13. Managability <administration> <policy enforcement> <user & group management> 2.14. Regulatory <Compliacne> <eDiscovery></p><p>Addressee Date <date> 7/10 <Document name></p><p>3. NEW ENVIRONMENT 3.1. New mail/UM Solution <What mail system/um system is in use?> <versions> <size of the environment in servers> <size of the environment in users/mailboxes> <size of the environment in amount of data> <size of the environment in amount of mails sent/received> <mail profiles of users defined (low,medium,high)> <domains> 3.2. Mailflow <vision drawings/depictment & elaboration on the current mail flow> 3.3. Identities <AD> <ADFS> <OKTA> <etc.> 3.4. Authentication <visio drawsings/depictment & elaboration on the current authentication flow for mail/um> 3.5. Licensing & Features <features supported by current system (mail, voice, Social media, calendar, public folders, contacts etc.)> <describe the licenses used and what features they provide. In addition you can use the mail profiles of users defined in 3.1 to elaborate.> 3.6. Security <measures taken in regards to security (anti-virus, spam, firewalls etc)> <these measures should also be depicted in the mailflow/authentication in points 3.2 and 3.3> 3.7. Support <The current support organization></p><p>Addressee Date <date> 8/10 <Document name></p><p>3.8. Clients <Clients used to connect to the mail/um environment and how they interact with the system> 3.9. (Mobile) Devices <Devices used to connect to the environment & their numers & uses). Think of ipads, android phones, laptops etc.></p><p>3.10. Usability & integrations <Services that rely on the current system (smtp relay example)> <Integration with other services> <Ease of connection> 3.11. User requirements <access, device support, mail handeling, rule configuration> 3.12. Reliability <uptime guaranties> <SLA> <mailbox en message protection> <backup> <DR> <failover> 3.13. Managability <administration> <policy enforcement> <user & group management> 3.14. Regulatory <Compliacne> <eDiscovery></p><p>Addressee Date <date> 9/10 <Document name></p><p>4. MIGRATION STRATEGY 4.1. Migration environment <depictment of the migration environment & ellaboration> 4.2. Migration size <De scribe the amount of mailboxes to migrate, size, etc.> 4.3. Migration method <elaboration on migration methods available and the one(s) chosen> 4.4. Dependancies <describe the dependancies on other services/providers/etc. to make the migration a success> 4.5. Tooling used <describe the toolings used and why></p><p>Addressee Date <date> 10/10</p>