<Document name>

<logo customer>

<customer name>

<Project name>

<Document name>

Table of content

Table of content

Document history

Document Version

Revision History

Approvals

Distribution

Glossary

Images & Icons

Glossary of terms, abbreviations and definitions

1.Introduction

2.CUrrent environment

2.1.Current mail/UM Solution

2.2.Mailflow

2.3.Identities

2.4.Authentication

2.5.Licensing & Features

2.6.Security

2.7.Support

2.8.Clients

2.9.(Mobile) Devices

2.10.Usability & integrations

2.11.User requirements

2.12.Reliability

2.13.Managability

2.14.Regulatory

3.New Environment

3.1.New mail/UM Solution

3.2.Mailflow

3.3.Identities

3.4.Authentication

3.5.Licensing & Features

3.6.Security

3.7.Support

3.8.Clients

3.9.(Mobile) Devices

3.10.Usability & integrations

3.11.User requirements

3.12.Reliability

3.13.Managability

3.14.Regulatory

4.Migration strategy

4.1.Migration environment

4.2.Migration size

4.3.Migration method

4.4.Dependancies

4.5.Tooling used

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

Approvals

Name / Signature / Title / Date of Issue / Version

Distribution

This document has been distributed to:

Name / Title / Date of Issue / Version

Glossary

Images & Icons

The following Icons are used throughout this document to elaborate on decisions or noteworhty factors.

Glossary of terms, abbreviations and definitions

Term, abbreviation, definition / Explination

1.Introduction

<project/document background>

2.CUrrent environment

2.1.Current mail/UM Solution

<What mailsystem/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 mailflow>

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>

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>

3.New Environment

3.1.New mail/UM Solution

<What mailsystem/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 mailflow>

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>

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.>

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>

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>

AddresseeDate <date>

1/11